F10 build errors - clashing initscripts and alsa-utils ?
by Development discussions related to Fedora
Hi there,
Noticed a recent build failure with a fedora package of mine: rakarrack,
that had an attempted arm build:
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=11262
1. This is a real time gui audio dsp application, so I guess someone
would need working X and alsa sound and jack-audio-connection-kit, and
fairly decent CPU speed to make use of this package even if it did
compile. Is it worth looking at this at this stage ?
2. The error from root.log seems to be because of:
=====
DEBUG backend.py:561: /usr/bin/yum --installroot
/var/lib/mock/dist-f10-build-3424-1358/root/ resolvedep 'alsa-utils'
'libjpeg-devel' 'libXpm-devel' 'jack-audio-connection-kit-devel'
'desktop-file-utils' 'fltk-devel' 'libpng-devel' 'alsa-lib-devel'
DEBUG util.py:280: Executing command: /usr/bin/yum --installroot
/var/lib/mock/dist-f10-build-3424-1358/root/ resolvedep 'alsa-utils'
'libjpeg-devel' 'libXpm-devel' 'jack-audio-connection-kit-devel'
'desktop-file-utils' 'fltk-devel' 'libpng-devel' 'alsa-lib-devel'
DEBUG util.py:256: 0:alsa-utils-1.0.15-1.fc8.armv5tel
DEBUG util.py:256: 0:libjpeg-devel-6b-43.fc10.armv5tel
DEBUG util.py:256: 0:libXpm-devel-3.5.7-4.fc10.armv5tel
DEBUG util.py:256:
0:jack-audio-connection-kit-devel-0.109.2-3.fc10.armv5tel
DEBUG util.py:256: 0:desktop-file-utils-0.15-3.fc10.armv5tel
DEBUG util.py:256: 0:fltk-devel-1.1.9-1.fc10.armv5tel
DEBUG util.py:256: 2:libpng-devel-1.2.31-2.fc10.armv5tel
DEBUG util.py:256: 0:alsa-lib-devel-1.0.18-6.rc3.fc10.armv5tel
DEBUG util.py:319: Child returncode was: 0
DEBUG backend.py:561: /usr/bin/yum --installroot
/var/lib/mock/dist-f10-build-3424-1358/root/ install 'alsa-utils'
'libjpeg-devel' 'libXpm-devel' 'jack-audio-connection-kit-devel'
'desktop-file-utils' 'fltk-devel' 'libpng-devel' 'alsa-lib-devel'
DEBUG util.py:280: Executing command: /usr/bin/yum --installroot
/var/lib/mock/dist-f10-build-3424-1358/root/ install 'alsa-utils'
'libjpeg-devel' 'libXpm-devel' 'jack-audio-connection-kit-devel'
'desktop-file-utils' 'fltk-devel' 'libpng-devel' 'alsa-lib-devel'
DEBUG util.py:256: initscripts-8.86-1.armv5tel from installed has
depsolving problems
DEBUG util.py:256: --> initscripts conflicts with alsa-utils
DEBUG util.py:256: Error: initscripts conflicts with alsa-utils
DEBUG util.py:319: Child returncode was: 1
DEBUG backend.py:549: umount -n
/var/lib/mock/dist-f10-build-3424-1358/root/proc
=====
I haven't actually gone any further to confirm that, but it seems like
an issue with one of the dependent packages ?
Is initscripts customized for arm builds, or should such a build problem
show up in x86 etc Fedora builds as well ?
Cheers, David Timms.
15 years
- 1
- 0
Minimal Install to get runlevel3 login prompt
by Carl Sherratt
Hi,
I am booting via u-boot on an ARM based dev kit over tftp (kernel) and
nfs (fedora-arm) using the minimal rootfs and some additional rpms I
needed for my application.
I can reach RunLevel 1 and can manually get sshd up and running from there.
However, when setting run level to 3 the initialisation stalls after
starting the SSHD service via a uart serial console connection.
This is probably because of missing rpms but which I am not sure? Does
anyone know the minimal install to reach runlevel 3, what should my
chkconfig --list look like?
-bash-3.2# chkconfig --list
messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
netplugd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rsyslog 0:off 1:off 2:on 3:off 4:on 5:on 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off
-bash-3.2#
Should the minimal root filesystem from :-
http://fedoraproject.org/wiki/Architectures/ARM be enough to reach
runlevel 3?
Should I have more services to be able to switch on for runlevel 3?
For now I am continuing at runlevel 1 and manually starting my sshd
service but will at some point need to resolve my issues regarding
runlevel 3 so
that we have proper user-management etc.
If you can help please respond
Many Thanks
Carl Sherratt.
15 years
- 1
- 0
successful bootstrap of gcc-java
by Robert Nelson
Hello,
After a couple weeks of trying this build on 128Mb hardware, my new
256Mb beagleboard finished this in less then 24 hours. (with no source
changes to gcc-4.3.2-7.fa4.src.rpm ) Since i wasn't sure it would
actually complete, i didn't run the test suite, so i'll try to rerun
it with that enabled this week.
Note: i'm not sure how useful this actually will be with out the
eclipse-ecj, java-jvm, or a java-jdk..
http://rcn-ee.homeip.net:81/dl/fedora/f10.0/
Built with: rpmbuild -ba --nodeps --target armv5tel -v --with
java_bootstrap gcc43.spec
(nodeps for the /usr/share/java/eclipse-ecj.jar dependicy)
bootstrap log
http://rcn-ee.homeip.net:81/dl/fedora/f10.0/gcc-java-bootstrap.log
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
15 years
- 2
- 4