console-image trying to build X?

console-image trying to build X?

[Peter Chubb]

Hi,
	I'm using the tip-of-tree as of this morning openembedded
recipes to build a console image for the Beagleboard.  After a while,
I see:
...
NOTE: collecting binary locales from locale tree
NOTE: Multiple libraries (libnss_nis.so.2, libnss_nisplus.so.2, libnss_hesiod.so.2) found, but LEAD_SONAME 'libc.so' doesn't match any of them
NOTE: Couldn't find shared library provider for libgcc_s.so.1
NOTE: Tasks Summary: Attempted 554 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/peterc/src/OpenEmbedded/openembedded/recipes/xorg-proto/xproto-native_7.0.15.bb' failed

Why are the recipes even trying to build X for a console-image?  (to
me, console means no X or graphics) And how can I work out how to fix
the error? 

--
Dr Peter Chubb                              peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
           Kernel Engineering Group (KEG): Where Systems Brew.

Re: console-image trying to build X?

[Lucian Ion]

Hi Peter,

I had the same problem after updating today.

I've removed the files 'xproto_7.0.15.bb' 'xproto-native_7.0.15.bb' 'xproto-sdk_7.0.15.bb' from
~/stuff/openembedded/recipes/xorg-proto

Then bitbake console-mage completed succesfully.

MACHINE = "qemuarm"
I've moved files to a ex3 file system

qemu-img create -fraw hda.img 160M
mkfs.ext3 hda.img
sudo losetup /dev/loop0 hda.img
sudo mount /dev/loop0 /mnt/jffs2
cd /mnt/jffs2/
sudo tar -xf ~/stuff/tmp/deploy/glibc/images/qemuarm/Angstrom-console-image-glibc-ipk-2009.X-test-20090528-qemuarm.rootfs.tar
cd ~/.qemu
sudo umount /mnt/jffs2
sudo losetup -d /dev/loop0

start:
qemu-system-arm  -M versatilepb -show-cursor -m 64 -kernel zImage-2.6.25+2.6.26-rc4-r6-qemuarm.bin -drive file=hda.img -append "root=/dev/sda"

The boot freeze. The last message:

Thu May 28 12:53:00 UTC 2009
hwclock: can't open '/dev/misc/rtc': No such file or directory

Anyone managed to start this image on qemu?
Do I need to use the buid qemu or the one from ubuntu distro will do?

Regards,
Lucian Ion
Software Engineer
Microsol Ltd.

________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Peter Chubb [peter.chubb@nicta.com.au]
Sent: 28 May 2009 03:57
To: openembedded-devel@lists.openembedded.org
Subject: [oe] console-image trying to build X?

Hi,
        I'm using the tip-of-tree as of this morning openembedded
recipes to build a console image for the Beagleboard.  After a while,
I see:
...
NOTE: collecting binary locales from locale tree
NOTE: Multiple libraries (libnss_nis.so.2, libnss_nisplus.so.2, libnss_hesiod.so.2) found, but LEAD_SONAME 'libc.so' doesn't match any of them
NOTE: Couldn't find shared library provider for libgcc_s.so.1
NOTE: Tasks Summary: Attempted 554 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/peterc/src/OpenEmbedded/openembedded/recipes/xorg-proto/xproto-native_7.0.15.bb' failed

Why are the recipes even trying to build X for a console-image?  (to
me, console means no X or graphics) And how can I work out how to fix
the error?

--
Dr Peter Chubb                              peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
           Kernel Engineering Group (KEG): Where Systems Brew.

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

________________________________________________________________________
This email has been scanned for all viruses.
________________________________________________________________________

_______________________________________________________________________

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify the originator of the message. 
This footer also confirms that this email message has been scanned for the presence of computer viruses.

Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Microsol.

If you have received this mail in error you are requested to e-mail us (info@microsol.ie) or by telephoning Microsol on +353 14153700.

Please Visit our website at
http://www.microsol.com

_______________________________________________________________________

This email has been scanned for all viruses.
_______________________________________________________________________

Re: console-image trying to build X?

[Mike Westerhof (mwester)]

Peter Chubb wrote:
> Hi,
> 	I'm using the tip-of-tree as of this morning openembedded
> recipes to build a console image for the Beagleboard.  After a while,
> I see:
> ...
> NOTE: collecting binary locales from locale tree
> NOTE: Multiple libraries (libnss_nis.so.2, libnss_nisplus.so.2, libnss_hesiod.so.2) found, but LEAD_SONAME 'libc.so' doesn't match any of them
> NOTE: Couldn't find shared library provider for libgcc_s.so.1
> NOTE: Tasks Summary: Attempted 554 tasks of which 0 didn't need to be rerun and 1 failed.
> ERROR: '/home/peterc/src/OpenEmbedded/openembedded/recipes/xorg-proto/xproto-native_7.0.15.bb' failed

xproto-native is missing the dependency on util-macros-native.

I lack the familiarity with the X recipes to know where this dependency
should be added; perhaps someone who knows this better can just add that.

In the meantime, just "bitbake util-macros-native", and restart your
original build; this time xorg-proto will build correctly.

> Why are the recipes even trying to build X for a console-image?  (to
> me, console means no X or graphics) And how can I work out how to fix
> the error? 

This has been a topic of discussion from time-to-time.  In all
likelihood, X is being pulled in to satisfy dbus or bluez (I don't
recall which off the top of my head).  You probably will not end up with
the full X packages on your resulting image; OE just need to build that
in order to satisfy some very specific build-time dependencies.

As a side note, I have been meaning for some time to create a "no-X"
version of the particular package that causes this, to suit my own
needs; once that gets done there might be an easy way to do a build that
won't have this dependency.

Regards,
Mike (mwester)

Re: console-image trying to build X?

[Phil Blundell]

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

On Thu, 2009-05-28 at 10:38 -0500, Mike Westerhof (mwester) wrote:
> This has been a topic of discussion from time-to-time.  In all
> likelihood, X is being pulled in to satisfy dbus or bluez (I don't
> recall which off the top of my head).  You probably will not end up with
> the full X packages on your resulting image; OE just need to build that
> in order to satisfy some very specific build-time dependencies.
> 
> As a side note, I have been meaning for some time to create a "no-X"
> version of the particular package that causes this, to suit my own
> needs; once that gets done there might be an easy way to do a build that
> won't have this dependency.

It's probably bluez4, which currently has a massive dependency stack
including GStreamer and countless other things.

The right way to fix this, I think, is to split the current monolithic
bluez4 package back into bluez-libs and bluez-apps (i.e. how it used to
be packaged in bluez3 days).  It's only the apps part that has the
monstrous dependencies: the libs are more-or-less self-contained, so
this way people who only want to link with the libs can avoid building
all the app prerequisities.

I did check in a bluez-libs_4.40 recipe last week sometime, which builds
just the library half of the package, but I didn't yet get time to
finish the apps part of the equation.  I've attached a work-in-progress
draft of an apps recipe in case anybody else is enthused enough to
finish it off.

In the slightly longer term it might even be worth going further than
that and splitting up bluez-apps into yet smaller recipes.  Taking
GStreamer as an example again, this is only required by one part of the
apps package (the bluez-gstreamer plugin) and I suspect this particular
plugin is of somewhat fringe interest: there are certainly plenty of
useful things you can do without it.

p.


[-- Attachment #2: bluez-apps_4.40.bb --]
[-- Type: text/plain, Size: 2066 bytes --]

DESCRIPTION = "Linux Bluetooth Stack Userland V4"
SECTION = "net"
PRIORITY = "optional"
DEPENDS = "gst-plugins-base alsa-lib libusb-compat dbus-glib bluez-libs"
HOMEPAGE = "http://www.bluez.org"
LICENSE = "GPL"

DEFAULT_PREFERENCE = "-1"

FILESPATHPKG .= ":bluez4"

SRC_URI = "http://www.kernel.org/pub/linux/bluetooth/bluez-${PV}.tar.gz \
          file://fix-dfutool-usb-declaration-mismatch.patch;patch=1 \
  file://sbc-thumb.patch;patch=1 \
  file://bluetooth.conf \
  file://separate-libs.patch;patch=1;pnum=0 \
"

S = "${WORKDIR}/bluez-${PV}"

inherit autotools_stage
AUTOTOOLS_STAGE_PKGCONFIG = "1"

EXTRA_OECONF = " \
  --enable-alsa \
  --enable-usb \
  --enable-netlink \
  --enable-tools \
  --enable-bccmd \
  --enable-hid2hci \
  --enable-dfutool \
  --enable-hidd \
  --enable-pandd \
  --enable-dund \
  --disable-cups \
  --enable-test \
  --enable-manpages \
  --enable-configfiles \
  --enable-initscripts \
  --disable-pcmciarules \
"

do_configure_prepend() {
        sed 's/ include / /;s/ lib / /' <Makefile.am >Makefile.am.new
        mv Makefile.am.new Makefile.am
}

do_install_append() {
        install -m 0644 ${S}/audio/audio.conf ${D}/${sysconfdir}/bluetooth/
        install -m 0644 ${S}/network/network.conf ${D}/${sysconfdir}/bluetooth/
        install -m 0644 ${S}/input/input.conf ${D}/${sysconfdir}/bluetooth/
        # at_console doesn't really work with the current state of OE, so punch some more holes so people can actually use BT
        install -m 0644 ${WORKDIR}/bluetooth.conf ${D}/${sysconfdir}/dbus-1/system.d/
}

PACKAGES =+ "gst-plugin-bluez libasound-module-bluez"

FILES_gst-plugin-bluez = "${libdir}/gstreamer-0.10/lib*.so"
FILES_libasound-module-bluez = "${libdir}/alsa-lib/lib*.so"
FILES_${PN} += "${libdir}/bluetooth/plugins/*.so"
FILES_${PN}-dev += "\
  ${libdir}/bluetooth/plugins/*.la \
  ${libdir}/alsa-lib/*.la \
  ${libdir}/gstreamer-0.10/*.la \
"

FILES_${PN}-dbg += "\
  ${libdir}/bluetooth/plugins/.debug \
  ${libdir}/*/.debug \
"

[-- Attachment #3: separate-libs.patch --]
[-- Type: text/x-patch, Size: 672 bytes --]

--- acinclude.m4.old	2009-05-22 16:38:04.000000000 +0100
+++ acinclude.m4	2009-05-22 16:38:24.000000000 +0100
@@ -324,9 +324,6 @@
 		AC_DEFINE(HAVE_LIBUSB, 1, [Define to 1 if you have USB library.])
 	fi
 
-	AC_SUBST([BLUEZ_CFLAGS], ['-I$(top_builddir)/include'])
-	AC_SUBST([BLUEZ_LIBS], ['$(top_builddir)/lib/libbluetooth.la'])
-
 	AC_SUBST([GDBUS_CFLAGS], ['-I$(top_srcdir)/gdbus'])
 	AC_SUBST([GDBUS_LIBS], ['$(top_builddir)/gdbus/libgdbus.la'])
 
--- configure.ac.old	2009-05-22 16:38:30.000000000 +0100
+++ configure.ac	2009-05-22 16:38:35.000000000 +0100
@@ -7,6 +7,7 @@
 AM_MAINTAINER_MODE
 
 AC_INIT_BLUEZ
+AM_PATH_BLUEZ
 
 COMPILER_FLAGS