Automatic AArch64 bootstrap daily update for August 6, 2013
by Brendan Conoboy
Number of candidate source rpms: 13606
Number of source rpms built in stage 4: 11834
Number of packages built in stage4 with aarch64 components: 4991
Currently building packages
MegaMek-0.30.11-11.fc19.src.rpm
ascii-design-1.0.2-1.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
evolution-3.8.3-2.fc19.src.rpm
fedfs-utils-0.9.2-2.fc19.src.rpm
gnome-tweak-tool-3.8.1-1.fc19.src.rpm
gtkhtml3-4.6.6-1.fc19.src.rpm
icu-50.1.2-7.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libint2-2.0.3-2.644hg.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
midori-0.5.4-1.fc19.src.rpm
nodejs-gaze-0.3.4-2.fc19.src.rpm
novnc-0.4-7.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
openscad-2013.06-1.fc19.src.rpm
openstack-quantum-2013.1.2-2.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
php-5.5.1-1.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qelectrotech-0.30-0.8.beta.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
selinux-policy-3.12.1-69.fc19.src.rpm
squid-3.2.13-1.fc19.src.rpm
sssd-1.10.1-1.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
telepathy-glib-0.20.4-1.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
texstudio-2.6.2-1.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
zorba-2.9.1-1.fc19.src.rpm
Packages building since previous report (which might be stuck or crashed)
MegaMek-0.30.11-11.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
evolution-3.8.3-2.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libint2-2.0.3-2.644hg.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
openscad-2013.06-1.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qelectrotech-0.30-0.8.beta.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
zorba-2.9.1-1.fc19.src.rpm
Total current build failure count: 745 failed
Build failures from unsatisfied dependencies: 169 failed-dep-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list.
Build failures after dependency resolution: 576 failed-build-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list.
Naive Top 25 dependency issues
225 nodejs-devel
223 ghc-Cabal-devel
144 kdelibs4-devel >= 4.10.5
127 kdelibs4-devel
74 libkdegames-devel >= 4.10.5
73 kdelibs4-devel >= 4.10.4
40 mono-devel
39 mingw32-gcc
38 libkdegames-devel >= 4.10.4
37 erlang-rebar
36 R-devel >= 3.0.0
20 prelink
20 octave-devel
20 mingw32-gcc-c++
20 ldc
19 valgrind-devel
19 kdelibs-devel
16 nautilus-devel
15 gtkglext-devel
15 gdal-devel
13 netcdf-devel
13 kdebase-workspace-devel
12 qtwebkit-devel
12 fcitx-devel
12 PyQt4-devel
Previously broken builds that are now fixed:
gpm-1.20.6-31.fc19
libpinyin-0.9.92-1.fc19
libpinyin-0.9.93-1.fc19
Newly attempted builds that failed:
adcli-0.7.2-1.fc19
firewalld-0.3.2-1.fc19
firewalld-0.3.4-1.fc19
gnome-session-3.8.4-1.fc19
libndp-0.1-3.20130723git873037a.fc19
nodejs-difflet-0.2.3-4.fc19
nodejs-estraverse-1.2.0-1.fc19
nodejs-eventemitter2-0.4.12-2.fc19
nodejs-fresh-0.1.0-4.fc19
nodejs-gaze-0.3.4-2.fc19
nodejs-jwt-simple-0.1.0-4.fc19
openstack-nova-2013.1.2-4.fc19
perl-XML-Bare-0.53-1.fc19
userspace-rcu-0.7.7-1.fc19
webkitgtk-2.0.2-1.fc19
webkitgtk-2.0.2-2.fc19
webkitgtk-2.0.4-1.fc19
10 years, 8 months
Debugging/disassembly in F19
by Florian Weimer
I'm looking at /usr/bin/newgrp in F19. Specifically, I've set a
breakpoint on xmalloc and stepped until the call to malloc in this function:
Dump of assembler code for function xmalloc:
0xb6f07ffc <+0>: push {r4, r5, r6, lr}
0xb6f08000 <+4>: sub sp, sp, #8
=> 0xb6f08004 <+8>: bl 0xb6f05698
0xb6f08008 <+12>: ldr r4, [pc, #104] ; 0xb6f08078 <xmalloc+124>
0xb6f0800c <+16>: add r4, pc, r4
0xb6f08010 <+20>: cmp r0, #0
0xb6f08014 <+24>: beq 0xb6f08020 <xmalloc+36>
0xb6f08018 <+28>: add sp, sp, #8
0xb6f0801c <+32>: pop {r4, r5, r6, pc}
0xb6f08020 <+36>: ldr r3, [pc, #84] ; 0xb6f0807c <xmalloc+128>
0xb6f08024 <+40>: mov r2, #5
0xb6f08028 <+44>: ldr r1, [pc, #80] ; 0xb6f08080 <xmalloc+132>
0xb6f0802c <+48>: ldr r3, [r4, r3]
0xb6f08030 <+52>: add r1, pc, r1
0xb6f08034 <+56>: ldr r5, [r3]
0xb6f08038 <+60>: bl 0xb6f055cc
0xb6f0803c <+64>: ldr r3, [pc, #64] ; 0xb6f08084 <xmalloc+136>
0xb6f08040 <+68>: ldr r3, [r4, r3]
0xb6f08044 <+72>: ldr r4, [r3]
0xb6f08048 <+76>: mov r6, r0
0xb6f0804c <+80>: bl 0xb6f05740
0xb6f08050 <+84>: ldr r0, [r0]
0xb6f08054 <+88>: bl 0xb6f056b0
0xb6f08058 <+92>: mov r3, r4
0xb6f0805c <+96>: mov r2, r6
0xb6f08060 <+100>: mov r1, #1
0xb6f08064 <+104>: str r0, [sp]
0xb6f08068 <+108>: mov r0, r5
0xb6f0806c <+112>: bl 0xb6f057b8
0xb6f08070 <+116>: mov r0, #13
0xb6f08074 <+120>: bl 0xb6f056e0
0xb6f08078 <+124>: andeq r10, r0, r0, ror lr
0xb6f0807c <+128>: andeq r0, r0, r8, asr r1
0xb6f08080 <+132>: andeq r1, r0, r8, ror #24
0xb6f08084 <+136>: andeq r0, r0, r4, asr r1
As you can see, there is zero symbolic information. I understand that
presenting symbol offsets obtained indirectly from constant pools might
be difficult, but even the simple direct calls aren't annotated.
On x86_64, the same function looks like this in GDB.
Dump of assembler code for function xmalloc:
0x00007fac621c9890 <+0>: push %rbp
0x00007fac621c9891 <+1>: push %rbx
0x00007fac621c9892 <+2>: sub $0x8,%rsp
=> 0x00007fac621c9896 <+6>: callq 0x7fac621c7470 <malloc@plt>
0x00007fac621c989b <+11>: test %rax,%rax
0x00007fac621c989e <+14>: je 0x7fac621c98a7 <xmalloc+23>
0x00007fac621c98a0 <+16>: add $0x8,%rsp
0x00007fac621c98a4 <+20>: pop %rbx
0x00007fac621c98a5 <+21>: pop %rbp
0x00007fac621c98a6 <+22>: retq
0x00007fac621c98a7 <+23>: callq 0x7fac621c71f0 <__errno_location@plt>
0x00007fac621c98ac <+28>: mov (%rax),%edi
0x00007fac621c98ae <+30>: callq 0x7fac621c7600 <strerror@plt>
0x00007fac621c98b3 <+35>: mov %rax,%rbp
0x00007fac621c98b6 <+38>: lea 0x203e0b(%rip),%rax #
0x7fac623cd6c8 <Prog>
0x00007fac621c98bd <+45>: lea 0x1cac(%rip),%rsi #
0x7fac621cb570
0x00007fac621c98c4 <+52>: mov $0x5,%edx
0x00007fac621c98c9 <+57>: xor %edi,%edi
0x00007fac621c98cb <+59>: mov (%rax),%rbx
0x00007fac621c98ce <+62>: callq 0x7fac621c72a0 <dcgettext@plt>
0x00007fac621c98d3 <+67>: mov %rax,%rdx
0x00007fac621c98d6 <+70>: mov 0x20371b(%rip),%rax #
0x7fac623ccff8
0x00007fac621c98dd <+77>: mov %rbp,%r8
0x00007fac621c98e0 <+80>: mov %rbx,%rcx
0x00007fac621c98e3 <+83>: mov $0x1,%esi
0x00007fac621c98e8 <+88>: mov (%rax),%rdi
0x00007fac621c98eb <+91>: xor %eax,%eax
0x00007fac621c98ed <+93>: callq 0x7fac621c75c0 <__fprintf_chk@plt>
0x00007fac621c98f2 <+98>: mov $0xd,%edi
0x00007fac621c98f7 <+103>: callq 0x7fac621c75a0 <exit@plt>
End of assembler dump.
--
Florian Weimer / Red Hat Product Security Team
10 years, 8 months
Can an armv5tel CPU with vfp flag boot an armv7l userspace?
by Alex Villacís Lasso
I have read that Fedora 18 will be the last Fedora distribution that will support the armv5tel userspace. I am a bit worried because I have built a project using the distribution on an armv5tel CPU with custom-built kernels. From reading
https://fedoraproject.org/wiki/Architectures/ARM/Secret_Decoder_Ring I understand that the main difference between armv5tel and armv7hl is that armv5tel forces passing floats on the stack and armv7hl uses the FPU. I was thinking about the possibility that
a CPU model that might have a FPU and currently runs an armv5tel userspace might be updated to run armv7hl instead. The end goal is to make the armv5tel system run the Fedora 19 armv7hl userspace with the custom-built kernel.
1) In /proc/cpuinfo, I have seen the "vfp" flag. Does this stand for "vector floating point", a FPU? Could there be other kinds of FPU that might be reported as different flags?
2) If an ARM chipset that is officially armv5tel can be guaranteed to have a FPU (vfp or otherwise), can it boot an armv7hl userspace with the same custom-built armv5tel kernel it used before? Do I have to watch out for specific kernel compile options
before attempting this?
10 years, 8 months
Automatic AArch64 bootstrap daily update for August 5, 2013
by Brendan Conoboy
Number of candidate source rpms: 13606
Number of source rpms built in stage 4: 11816
Number of packages built in stage4 with aarch64 components: 4981
Currently building packages
MegaMek-0.30.11-11.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
ekiga-4.0.1-1.fc19.src.rpm
empathy-3.8.3-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
evolution-3.8.3-2.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libint2-2.0.3-2.644hg.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
openscad-2013.06-1.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qelectrotech-0.30-0.8.beta.fc19.src.rpm
qpid-cpp-0.22-1.1.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
syncevolution-1.3.99.3-1.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
zorba-2.9.1-1.fc19.src.rpm
Packages building since previous report (which might be stuck or crashed)
MegaMek-0.30.11-11.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libint2-2.0.3-2.644hg.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
openscad-2013.06-1.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qelectrotech-0.30-0.8.beta.fc19.src.rpm
qpid-cpp-0.22-1.1.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
zorba-2.9.1-1.fc19.src.rpm
Total current build failure count: 731 failed
Build failures from unsatisfied dependencies: 161 failed-dep-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list.
Build failures after dependency resolution: 570 failed-build-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list.
Naive Top 10 dependency issues
396 ghc-Cabal-devel
232 nodejs-devel
207 kdelibs4-devel
154 kdelibs4-devel >= 4.10.5
134 kdelibs4-devel >= 4.10.4
76 libkdegames-devel >= 4.10.5
74 libkdegames-devel >= 4.10.4
71 erlang-rebar
61 mono-devel
33 mingw32-gcc
Previously broken builds that are now fixed:
Newly attempted builds that failed:
control-center-3.8.3-1.fc19
control-center-3.8.3-2.fc19
gnome-initial-setup-0.12-1.fc19
10 years, 8 months
Yum update problems
by Mickey
Fedora-18-arm
After update This problem shows up, I did update and I still have
problems with update for the following four packages, What gives ?
root@localhost jim]# yum update
Loaded plugins: langpacks, presto, refresh-packagekit
fedora/18/armhfp/metalink | 2.8 kB 00:00
updates/18/armhfp/metalink | 2.9 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package glibc-common.armv7hl 0:2.16-24.fc18 will be updated
---> Package glibc-common.armv7hl 0:2.16-33.fc18 will be an update
---> Package gnome-keyring.armv7hl 0:3.6.2-2.fc18 will be updated
---> Package gnome-keyring.armv7hl 0:3.6.3-1.fc18 will be an update
---> Package iputils.armv7hl 0:20121125-2.fc18 will be updated
---> Package iputils.armv7hl 0:20121221-2.fc18 will be an update
---> Package systemd.armv7hl 0:195-15.fc18 will be updated
---> Package systemd.armv7hl 0:201-2.fc18.7 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
glibc-common armv7hl 2.16-33.fc18 updates 11 M
gnome-keyring armv7hl 3.6.3-1.fc18 updates 811 k
iputils armv7hl 20121221-2.fc18 updates 152 k
systemd armv7hl 201-2.fc18.7 updates 2.3 M
Transaction Summary
================================================================================
Upgrade 4 Packages
Total download size: 14 M
Is this ok [y/N]: y
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 14 M
(1/4): iputils-20121221-2.fc18.armv7hl.rpm | 152 kB 00:02
(2/4): gnome-keyring-3.6.3-1.fc18.armv7hl.rpm | 811 kB 00:03
(3/4): glibc-common-2.16-33.fc18.armv7hl.rpm | 11 MB 00:10
(4/4): systemd-201-2.fc18.7.armv7hl.rpm | 2.3 MB 00:23
--------------------------------------------------------------------------------
Total 590 kB/s | 14 MB 00:24
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Updating :
glibc-common-2.16-33.fc18.armv7hl 1/8
Error unpacking rpm package glibc-common-2.16-33.fc18.armv7hl
error: unpacking of archive failed on file /usr/libexec/pt_chown: cpio:
cap_set_file
error: glibc-common-2.16-33.fc18.armv7hl: install failed
Updating :
systemd-201-2.fc18.7.armv7hl 2/8
Error unpacking rpm package systemd-201-2.fc18.7.armv7hl
warning: /etc/dbus-1/system.d/org.freedesktop.login1.conf created as
/etc/dbus-1/system.d/org.freedesktop.login1.conf.rpmnew
warning: /etc/systemd/journald.conf created as
/etc/systemd/journald.conf.rpmnew
warning: /etc/systemd/logind.conf created as /etc/systemd/logind.conf.rpmnew
warning: /etc/systemd/system.conf created as /etc/systemd/system.conf.rpmnew
warning: /etc/systemd/user.conf created as /etc/systemd/user.conf.rpmnew
error: unpacking of archive failed on file /usr/bin/systemd-detect-virt:
cpio: cap_set_file
Updating :
iputils-20121221-2.fc18.armv7hl 3/8
Error unpacking rpm package iputils-20121221-2.fc18.armv7hl
error: systemd-201-2.fc18.7.armv7hl: install failed
error: unpacking of archive failed on file /usr/bin/ping: cpio: cap_set_file
Updating :
gnome-keyring-3.6.3-1.fc18.armv7hl 4/8
Error unpacking rpm package gnome-keyring-3.6.3-1.fc18.armv7hl
error: iputils-20121221-2.fc18.armv7hl: install failed
error: unpacking of archive failed on file
/usr/bin/gnome-keyring-daemon: cpio: cap_set_file
Verifying :
iputils-20121221-2.fc18.armv7hl 1/8
Verifying :
glibc-common-2.16-33.fc18.armv7hl 2/8
glibc-common-2.16-24.fc18.armv7hl was supposed to be removed but is not!
Verifying :
glibc-common-2.16-24.fc18.armv7hl 3/8
Verifying :
systemd-201-2.fc18.7.armv7hl 4/8
systemd-195-15.fc18.armv7hl was supposed to be removed but is not!
Verifying :
systemd-195-15.fc18.armv7hl 5/8
iputils-20121125-2.fc18.armv7hl was supposed to be removed but is not!
Verifying :
iputils-20121125-2.fc18.armv7hl 6/8
gnome-keyring-3.6.2-2.fc18.armv7hl was supposed to be removed but is not!
Verifying :
gnome-keyring-3.6.2-2.fc18.armv7hl 7/8
Verifying :
gnome-keyring-3.6.3-1.fc18.armv7hl 8/8
Failed:
glibc-common.armv7hl 0:2.16-24.fc18 glibc-common.armv7hl
0:2.16-33.fc18
gnome-keyring.armv7hl 0:3.6.2-2.fc18 gnome-keyring.armv7hl
0:3.6.3-1.fc18
iputils.armv7hl 0:20121125-2.fc18 iputils.armv7hl 0:20121221-2.fc18
systemd.armv7hl 0:195-15.fc18 systemd.armv7hl 0:201-2.fc18.7
10 years, 8 months
Plans for fpc on arm ?
by Hans de Goede
Hi,
I just got a mail that the hedgewar rebuild (as part of the Fedora-20 mass rebuild),
failed because there is no fpc for arm. So I was wondering if anyone is working on
this and what the plans for fpc on arm are?
Regards,
Hans
10 years, 8 months
KUSER_HELPERS kernel config
by Josh Boyer
Hi All,
ARM introduced a new kernel config option called KUSER_HELPERS. It
seems it allows one to turn something that has always been built-in
off. I've left it on with today's rawhide kernel build, but please
review and change if necessary.
josh
10 years, 8 months
