Can you post the stuff at the start of the build log so we know what
layers/branches/versions are being built?

Philip

On 01/17/2013 02:33 PM, David Lambert wrote:
> I am not sure whether this is a Beaglebone or Angstrom issue, so I am
> posting it to both:
> 
> Over the past couple of weeks I have noticed that the build system
> appears to be unstable. Various errors relating to systemd and udev have
> appeared. Some workarounds have been suggested and seem to work for a
> while, but after ./oebb.sh update similar problems occur. Is this a
> known issue with Angstrom/Beaglebone? If so, is there a fix in the
> works? If not, could someone please guide me as to what I may be doing
> wrong.
> 
> Regards,
> 
> Dave.
> 
> 
> My work-flow is as follows:
> 
> cd ~/
> rm -rf ~/beaglebone
> mkdir -p ~/beaglebone
> cd ~/beaglebone
> git clone git://github.com/Angstrom-distribution/setup-scripts.git
> cd setup-scripts
> MACHINE=beaglebone ./oebb.sh config beaglebone
> MACHINE=beaglebone ./oebb.sh update
> . ~/.oe/environment-angstromv2012.05
> bitbake systemd-image
> 
> 
> <--snip-->
> 
> NOTE: Resolving any missing task queue dependencies
> NOTE: preferred version 189 of systemd not available (for item udev)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item systemd)
> NOTE: versions of systemd available: git v189
> NOTE: preferred version 189 of systemd not available (for item udev)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item
> udev-systemd)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item udev-utils)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item systemd-dev)
> NOTE: versions of systemd available: git v189
> NOTE: preferred version 189 of systemd not available (for item systemd)
> NOTE: versions of systemd available: git v189
> NOTE: Preparing runqueue
> ERROR: Multiple .bb files are due to be built which each provide systemd
> (/home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_v189.bb
> /home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_git.bb).
> 
>  This usually means one provides something the other doesn't and should.
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Running task 1553 of 3282 (ID: 1119,
> /home/dlambert/beaglebone/setup-scripts/sources/meta-ti/recipes-kernel/linux/linux-ti33x-psp_3.2.bb,
> do_package_write_ipk)
> 
> <--snip-->
> 
> | checking pkg-config is at least version 0.9.0... yes
> | checking for UDEV... no
> | configure: error: Package requirements ( libudev >= 172 ) were not met:
> |
> | No package 'libudev' found
> |
> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
> | installed software in a non-standard prefix.
> |
> | Alternatively, you may set the environment variables UDEV_CFLAGS
> | and UDEV_LIBS to avoid the need to call pkg-config.
> | See the pkg-config man page for more details.
> | ERROR: oe_runconf failed
> NOTE: package systemd-git-r28: task do_configure: Failed
> ERROR: Task 165
> (/home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_git.bb,
> do_configure) failed with exit code '1'
> Waiting for 1 running tasks to finish:
> 0:
> linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01
> do_package_write_ipk (pid 22350)
> 
> 
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to