arm August 2013

arm@lists.fedoraproject.org

48 participants
116 discussions

Fedora ARM 12 on IGEPv2 (Beagle Board clone)
by Matthew Wilson 01 Jan '16

01 Jan '16

Hi all, I would like to introduce myself to the group. I have recently received an IGEPv2 board [1], which is based on the Beagle Board, but with wifi, bluetooth, ethernet, and more RAM. I'm still at the "wow, it's tiny and it runs Linux" stage. I should get a bit more time over the next month and Christmas to play around properly with it. I'm new to embedded development, but neither new to Linux nor ARM (writing my first ARM assembly some 15 years ago). However, for the past 6 years I've not even built a Linux kernel, preferring to use the default kernel in Fedora for simplicity :) Firstly, a thank you to those involved in Fedora ARM for getting it to this stage. If I get the time, I'd really like to contribute some (probably small) effort to help get Fedora ARM working well on the IGEPv2 and Beagle Board. As I progress, I'd like to know what I can do to help. In the meantime, I have some questions. Apologies in advance if these seem simple. 1) There are various different kernels from different sources. I'm used to there being a small set of "right" kernels (that is, Fedora's idea of "right") for x86. I fully appreciate that different ARM-based boards are quite different in capabilities (like different instruction set variants). a) Is there likely to be some standardised vanilla Fedora ARM kernel source? (Or is that simply the source RPM available for Fedora?) Then patches /could/ be offered for the more common systems (e.g. Beagle Board & clones, SheevaPlug). b) Would it then make sense to offer these as pre-built RPMs for common systems? c) Is there any guidance on which version is good to use as a base? I've seen quite different kernel versions being used (from 2.6.27 to 2.6.31). 2) I understand a little bit about the different calling conventions, FP differences (e.g. soft FPU versus VFP), and instruction set differences (v5 versus v7). a) Can the kernel can be safely built with a different instruction set targeted? (I know there are different optimisation options passed to GCC. Apologies if this seems a bit newbie-ish.) b) For FP-heavy programs (e.g. ogg encoding), is it possible to build the packages with VFP/NEON but still get them to work in a soft FPU system? I'd imagine any call to an external library would have to somehow be defined to use a different calling standard. 3) There seem to be some missing dependencies in the packages in the current Fedora ARM repository. For example, emacs is requiring libotf, which doesn't seem to be there in the repository. And likewise with the xorg-x11-font* packages needing ttmkdir. I'm confused as to how the RPM could have been successfully built without it. What am I missing? 4) I see there has been some discussion over unaligned data access. (Oh, I remember that from the ARM2 days.) It seems as if the Cortex-A8 cores allow unaligned data access when set up to do so [2]. Does this, in any way, help with the compatibility of packages targetting Cortex-A8? 5) I've managed to get various source packages missing from the Fedora ARM repositories to compile successfully (natively). I guess there is a reason why there are not in the repos right now -- is that reason down to time and priorities, or is there some blocking bugs with many of these packages? I look forward to being able to contribute something back into Fedora! Kind regards, Matthew [1] http://www.igep-platform.com/index.php?option=com_content&view=article&id=4… [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344j/Beihgi…

11 15

Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support
by Hans de Goede 26 Dec '13

26 Dec '13

Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r… sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), or at least no battery backup for it, resulting in the date + time being wrong. -If the date is of by more then a couple of months, "yum update" won't work because certificate validation fails for the https connection yum tries to make. So if yum fails to get its repodata first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows up in the output umount its partitions 3) Write the img file to the card, ie as root do: xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 sync 4) The card is not yet ready for use! Since the A10 u-boot is board specific, the image comes without any uboot install, follow the next steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get automatically mounted, if not mount it manually, 6) As root (or through sudo) run: <uboot-part-mount>/select-board.sh, ie: sudo /run/media/hans/uboot/select-board.sh If you've dialog installed the select-board.sh script will prompt for your board. If you don't have dialog installed, it will print the list of supported boards. Lookup your board and re-run the script with the shortname for your board as argument, ie: sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: umount /run/media/hans/uboot umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically reboot once, this is part of the process to resize the root partition to fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: 11a) Configure networking, note: * If you've an A10 board with wired ethernet and you want to use dhcp you don't need to do anything. * If you've an A20 board, your ethernet will have a random mac-address, so if you want to configure a static ip-address and want it to stick across reboots, go to the ethernet-tab, select the mac-address field and delete its contents, so that the static ip address you're configuring does not get tied to the random mac-address. 11b) Setup the time zone 11c) Set a root password 11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, pal-nc-svideo. Note the -svideo variants should only be used on boards with an svideo connector, for composite out use the regular variants, ie: disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the disp.screen0_output_mode value and set it to the desired mode, ie: disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the disp.screen0_output_mode value otherwise it will be ignored. interlaced progressive and refreshrate settings specified are ignored, each resolution has hardcoded values for these. Example usage: disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. Also we don't use an initrd, so removing the console=ttyS0,115200 from the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, this combining is done by the build-image.sh script The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script.

5 5

Building a kernel for the Chromebook...
by Darryl L. Pierce 03 Sep '13

03 Sep '13

Is it advisable to build my own kernel for the Chromebook? I glanced through the IRC chat from last week and saw a note about kernels. -- Darryl L. Pierce <mcpierce(a)gmail.com> http://mcpierce.multiply.com/ "What do you care what people think, Mr. Feynman?"

4 14

Beagle Bone with FC19
by Steve Underwood 01 Sep '13

01 Sep '13

Hi, There is a Fedora 19 image for the Beaglebone Black at http://parasense.fedorapeople.org, but I'm not sure how to use it. When copied to an SD card it boots into the MATE desktop OK, as the user "guest". However, root seems to have a password, which I can't find documented, so I can't much further than just doodling with things. Regards, Steve

3 5

Fedora 19 does not boot on Pandaboard ES (Rev. B3)!
by Franz Ilano 01 Sep '13

01 Sep '13

Hi, today I received my Pandaboard ES (Rev. B3) and I tried to use Fedora-Minimal-VFAT-armhfp-19-1-sda.raw.xz to boot it and I received on the serial console: U-Boot SPL 2013.04 (Jun 17 2013 - 12:42:04) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 4000000 Is there already a solution for this problem? Searching for the problem gave me some solutions/hints: https://groups.google.com/forum/#!topic/pandaboard/OWvyla72e00 http://www.eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ https://groups.google.com/forum/#!topic/pandaboard/n5h8wKJ84Ok Before trying myself I wonder if someone already has a ready-to-use solution for it? (Because it is my only ARM-system compiling might get complicated for me...) Best regards, Franz P.S.: Will this problem also happen in Fedora 20 or are the developers aware of this problem? (Or is Rev B3 a not-supported-out-of-the-box system?)

3 4

Re: [fedora-arm] [linux-sunxi] Re: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support
by Hans de Goede 31 Aug '13

31 Aug '13

Hi, On 08/30/2013 07:24 PM, elias.vds(a)gmail.com wrote: > Op vrijdag 19 juli 2013 00:12:35 UTC+2 schreef Hans de Goede: >> The following has been ported / is supported: >> >> -sound: analog in/out >> Fedora 19 ARM should also work on the following devices: >> >> * A13-OLinuXino (Olimex) >> > > Hi, thanks very much for the release! > > I've already tested the Fedora 18 remix on my A13-OLinuXino (even with WIFI working!), but I can't get the audio to work: > ALSA reports that no soundcards could be detected. > > However using the Debian image of Olimex, I was able to get audio through my headphones and the mic worked also. I looked up the driver, and it appeared to be "sun5i-CODEC". On the rootfs of the Fedora image, I looked into "/lib/modules/<sun5i-kernel>/kernel/sound/soc/", but I only could see a "sun4i" directory, even without a "sun4i-CODEC" counterpart. > I read somewhere else that code of "/sound/soc/sun5i" was merged with "/sound/soc/sun4i", but I tried to modprobe each driver in "/sound/soc/sun4i" without success. > > Do I have to recompile the whole kernel, or just compile the "sun5i-CODEC" module, or do I have to do something different to get audio working? > Thank you very much! You're not seeing the sun4i-codec module (which works for sun5i too) because it is build into the kernel. You should see some audio devices under /dev/snd and /sys/class/sound While checking things work with Fedora 19 ARM remix for Allwinner SOCs release 1 I did notice that there is an error in the fex file for the A13-OLinuXino, causing only audio-out to be present, I've just pushed an updated fex file here: https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a13/a13-… If you save this file, convert it to a script.bin file using the fex2bin utility from here: https://github.com/linux-sunxi/sunxi-tools And then overwrite script.bin in the uboot partition of your sdcard with the new one you should also get a capture device. Regards, Hans

1 0

Daily Koji Compare Stats
by jon.chiappetta＠senecacollege.ca 31 Aug '13

31 Aug '13

Sat Aug 31 08:05:01 EDT 2013 f19-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 2189 | 0 | 3 | 0 | 75 | 3 | http://scotland.proximity.on.ca/jon/kc.f19-updates.diff.html f19-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 438 | 0 | 0 | 2 | 14 | 0 | http://scotland.proximity.on.ca/jon/kc.f19-updates-testing.diff.html f18-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 4092 | 0 | 25 | 0 | 151 | 43 | http://scotland.proximity.on.ca/jon/kc.f18-updates.diff.html f18-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 1790 | 0 | 2 | 3 | 81 | 2 | http://scotland.proximity.on.ca/jon/kc.f18-updates-testing.diff.html f17-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 4192 | 0 | 104 | 1 | 154 | 151 | http://scotland.proximity.on.ca/jon/kc.f17-updates.diff.html f17-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 147 | 0 | 2 | 0 | 35 | 2 | http://scotland.proximity.on.ca/jon/kc.f17-updates-testing.diff.html ARM Build Status Wiki: https://fedoraproject.org/wiki/Architectures/ARM https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide Sat Aug 31 08:11:34 EDT 2013

1 0

Automatic AArch64 bootstrap daily update for August 31, 2013
by Brendan Conoboy 31 Aug '13

31 Aug '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12018 Number of packages built in stage4 with aarch64 components: 5123 Currently building packages ascii-design-1.0.2-1.fc19.src.rpm chrony-1.29-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm dcap-2.47.8-1.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm edje-1.7.8-1.fc19.src.rpm glibc-2.17-11.fc19.src.rpm glibc-2.17-14.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libcxgb4-1.3.1-1.fc19.src.rpm libguac-0.7.0-5.fc19.src.rpm libreswan-3.5-2.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm lpg-2.0.17-10.fc19.src.rpm mariadb-5.5.32-8.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mate-themes-extras-1.7.2-2.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm neap-0.7-1.fc19.src.rpm nordugrid-arc-3.0.3-2.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm pdns-3.3-4.fc19.src.rpm php-pecl-http-2.0.0-0.18.beta5.fc19.src.rpm php-pecl-propro-1.0.0-1.fc19.src.rpm php-symfony2-Yaml-2.2.5-1.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-django-1.5.2-1.fc19.src.rpm python-django-south-0.8.2-1.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qbittorrent-3.0.9-1.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qmmp-0.7.1-2.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Packages building since previous report (which might be stuck or crashed) ascii-design-1.0.2-1.fc19.src.rpm chrony-1.29-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm dcap-2.47.8-1.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm glibc-2.17-11.fc19.src.rpm glibc-2.17-14.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libcxgb4-1.3.1-1.fc19.src.rpm libguac-0.7.0-5.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm lpg-2.0.17-10.fc19.src.rpm mariadb-5.5.32-8.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mate-themes-extras-1.7.2-2.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nordugrid-arc-3.0.3-2.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qbittorrent-3.0.9-1.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Total current build failure count: 811 failed Build failures from unsatisfied dependencies: 340 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 471 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 452 ghc-Cabal-devel 252 kdelibs4-devel 212 nodejs-devel 154 kdelibs4-devel >= 4.10.5 146 kdelibs4-devel >= 4.10.4 82 erlang-rebar 79 mono-devel 76 libkdegames-devel >= 4.10.5 76 libkdegames-devel >= 4.10.4 74 R-devel >= 3.0.0 64 mingw32-gcc 38 octave-devel 36 valgrind-devel 33 kdelibs-devel 32 openmpi-devel 30 nautilus-devel 29 gdal-devel 28 mingw32-gcc-c++ 28 ldc 28 gtkglext-devel 28 PyQt4-devel 27 prelink 26 qt-webkit-devel 25 netcdf-devel 24 qtwebkit-devel Previously broken builds that are now fixed: Newly attempted builds that failed: a2jmidid-8-4.fc19 apt-0.5.15lorg3.95-8.git522.1.fc19 eeze-1.7.8-2.fc19 gfal2-plugin-xrootd-0.2.2-2.fc19 ibmasm-3.0-21.fc19 keepalived-1.2.7-5.fc19 lcg-util-1.15.0-0.fc19 nodejs-traverse-0.6.3-5.fc19 nordugrid-arc-3.0.1-1.fc19 opusfile-0.4-1.fc19 pacemaker-1.1.9-3.fc19 perl-POE-Test-Loops-1.352-1.fc19 root-5.34.07-1.fc19 rubygem-aws-sdk-1.15.0-1.fc19 spacechart-0.9.5-11.fc19 sugar-measure-49-1.fc19 urdfdom-headers-0.2.3-1.fc19

1 0

Automatic AArch64 bootstrap daily update for August 30, 2013
by Brendan Conoboy 30 Aug '13

30 Aug '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12013 Number of packages built in stage4 with aarch64 components: 5119 Currently building packages a2jmidid-8-4.fc19.src.rpm ascii-design-1.0.2-1.fc19.src.rpm chrony-1.29-1.fc19.src.rpm claws-mail-3.9.1-2.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm dcap-2.47.8-1.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm emacs-24.3-11.fc19.src.rpm gcompris-12.11-3.fc19.src.rpm glibc-2.17-11.fc19.src.rpm glibc-2.17-14.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libcxgb4-1.3.1-1.fc19.src.rpm libguac-0.7.0-5.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm lpg-2.0.17-10.fc19.src.rpm mariadb-5.5.32-8.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mate-themes-extras-1.7.2-2.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nordugrid-arc-3.0.3-2.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm pacemaker-1.1.9-3.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qbittorrent-3.0.9-1.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Packages building since previous report (which might be stuck or crashed) ascii-design-1.0.2-1.fc19.src.rpm chrony-1.29-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm dcap-2.47.8-1.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm glibc-2.17-11.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libcxgb4-1.3.1-1.fc19.src.rpm libguac-0.7.0-5.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm lpg-2.0.17-10.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mate-themes-extras-1.7.2-2.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 pacemaker-1.1.9-3.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Total current build failure count: 794 failed Build failures from unsatisfied dependencies: 331 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 463 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 446 ghc-Cabal-devel 235 kdelibs4-devel 206 nodejs-devel 154 kdelibs4-devel >= 4.10.5 133 kdelibs4-devel >= 4.10.4 81 erlang-rebar 76 libkdegames-devel >= 4.10.5 73 libkdegames-devel >= 4.10.4 63 mingw32-gcc 61 mono-devel 44 R-devel >= 3.0.0 31 valgrind-devel 31 kdelibs-devel 28 mingw32-gcc-c++ 27 ldc 26 openmpi-devel 24 prelink 24 gtkglext-devel 23 qt-webkit-devel 23 nautilus-devel 23 gdal-devel 22 octave-devel 22 fcitx-devel 21 qtwebkit-devel 21 kdebase-workspace-devel Previously broken builds that are now fixed: grubby-8.24-1.fc19 grubby-8.26-2.fc19 grubby-8.28-1.x1.fc19 libtommath-0.41-14.fc18 perl-POE-Filter-IRCD-2.44-1.fc19 Newly attempted builds that failed: compat-libffi-3.0.10-3.fc19 djview4-4.9-2.fc19 eet-1.7.8-2.fc19 evas-1.7.8-1.fc19 giis-4.6.2-4.fc19 i8kutils-1.33-5.fc19 jglobus-2.0.6-2.fc19 pp3-1.3.3-7.fc18 replacer-1.5.2-1.fc19 rubygem-rr-1.1.2-2.fc19 rubygem-test-unit-rr-1.0.3-1.fc19 ski-1.3.2-14.fc19 sugar-castle-23-4.fc19 sugar-kuku-4-8.fc19

5 5

Daily Koji Compare Stats
by jon.chiappetta＠senecacollege.ca 30 Aug '13

30 Aug '13

Fri Aug 30 08:05:02 EDT 2013 f19-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 2171 | 0 | 3 | 0 | 76 | 3 | http://scotland.proximity.on.ca/jon/kc.f19-updates.diff.html f19-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 422 | 0 | 0 | 10 | 13 | 0 | http://scotland.proximity.on.ca/jon/kc.f19-updates-testing.diff.html f18-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 4090 | 0 | 24 | 0 | 150 | 42 | http://scotland.proximity.on.ca/jon/kc.f18-updates.diff.html f18-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 1780 | 0 | 6 | 4 | 81 | 6 | http://scotland.proximity.on.ca/jon/kc.f18-updates-testing.diff.html f17-updates : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 4192 | 0 | 104 | 1 | 154 | 151 | http://scotland.proximity.on.ca/jon/kc.f17-updates.diff.html f17-updates-testing : arm vs PA Same | Newer | Older | Local | Remote | Missing | ------------------------------------------------------------------------------------------ 147 | 0 | 2 | 0 | 35 | 2 | http://scotland.proximity.on.ca/jon/kc.f17-updates-testing.diff.html ARM Build Status Wiki: https://fedoraproject.org/wiki/Architectures/ARM https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide Fri Aug 30 08:12:04 EDT 2013

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm August 2013