xtrans_1.2.3 build failure using bitbake

GoogleGroups
1

Hi,

So I'm trying to build my own beagleboard-demo-image from source using
bitbake, however the build system crashes as soon as it hits the
xtrans package. I tried to build the latter on its own using:

$ bitbake -b ../openembedded/recipes/xorg-lib/xtrans_1.2.3.bb

However, I'm getting these messages:

[ilyes@blackrock build]$ bitbake -b
../openembedded/recipes/xorg-lib/xtrans_1.2.3.bb
__builtin__:74: DeprecationWarning: the sets module is deprecated
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 5 of 17 (ID: 5,
/home/ilyes/openembedded/openembedded/recipes/xorg-lib/xtrans_1.2.3.bb,
do_configure)
ERROR: function do_configure failed
ERROR: log data follows
(/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/temp/log.do_configure.1467)

automake (GNU automake) 1.10.2
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <tromey@redhat.com>
       and Alexandre Duret-Lutz <adl@gnu.org>.
AUTOV is 1.10
NOTE: Executing autoreconf --verbose --install --force

--exclude=autopoint -I
/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3/
-I/home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal-1.10
-I /home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I

/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3/
-I /home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal-1.10
-I /home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal
--force

autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running:

/home/ilyes/openembedded/build/tmp/staging/i686-linux/usr/bin/autoconf
--include=/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3/
--include=/home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal-1.10
--include=/home/ilyes/openembedded/build/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/share/aclocal
--force --warnings=cross

autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --foreign --add-missing --copy

--force-missing --warnings=cross

automake: unknown warning category `cross'
autoreconf: running: gnu-configize
autoreconf: Leaving directory `.'
NOTE: Running

/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3/configure
             --build=i686-linux
--host=arm-angstrom-linux-gnueabi
--target=arm-angstrom-linux-gnueabi --prefix=/usr
                  --exec_prefix=/usr --bindir=/usr/bin
           --sbindir=/usr/sbin
--libexecdir=/usr/libexec --datadir=/usr/share
          --sysconfdir=/etc --sharedstatedir=/usr/com
           --localstatedir=/var --libdir=/usr/lib
             --includedir=/usr/include
--oldincludedir=/usr/include
--infodir=/usr/share/info --mandir=/usr/share/man
              --enable-malloc0returnsnull ...

configure: WARNING: unrecognized options: --enable-malloc0returnsnull
configure: loading site script

/home/ilyes/openembedded/openembedded/site/endian-little

configure: loading site script

/home/ilyes/openembedded/openembedded/site/common-linux

configure: loading site script

/home/ilyes/openembedded/openembedded/site/common-glibc

configure: loading site script

/home/ilyes/openembedded/openembedded/site/arm-common

configure: loading site script

/home/ilyes/openembedded/openembedded/site/arm-linux

configure: loading site script

/home/ilyes/openembedded/openembedded/site/common

configure: loading site script

/home/ilyes/openembedded/openembedded/site/common

checking for a BSD-compatible install...

/home/ilyes/openembedded/build/tmp/staging/i686-linux/usr/bin/install
-c

checking whether build environment is sane... yes
checking for a thread-safe mkdir -p...

/home/ilyes/openembedded/build/tmp/staging/i686-linux/usr/bin/mkdir -p

checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-angstrom-linux-gnueabi-strip... arm-none-linux-gnueabi-strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking if xorg-macros used to generate configure is at least

1.2... yes, 1.2.1

checking for style of include used by make... GNU
checking for arm-angstrom-linux-gnueabi-gcc...

arm-none-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp

checking for C compiler default output file name...
configure: error: in

`/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3':

configure: error: C compiler cannot create executables
See `config.log' for more details.
FATAL: oe_runconf failed

NOTE: Task failed:
/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/temp/log.do_configure.1467
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/home/ilyes/openembedded/openembedded/recipes/xorg-lib/xtrans_1.2.3.bb
do_configure failed
ERROR: Task 5 (/home/ilyes/openembedded/openembedded/recipes/xorg-lib/xtrans_1.2.3.bb,
do_configure) failed
NOTE: Tasks Summary: Attempted 4 tasks of which 4 didn't need to be
rerun and 1 failed.
ERROR: '/home/ilyes/openembedded/openembedded/recipes/xorg-lib/xtrans_1.2.3.bb'
failed

Any ideas?

Regards,
Ilyes Gouta.

2

Op 26 jul 2009 om 15:00 heeft Ilyes Gouta <ilyes.gouta@gmail.com> het volgende geschreven:\

Hi,

So I'm trying to build my own beagleboard-demo-image from source using
bitbake, however the build system crashes as soon as it hits the
xtrans package. I tried to build the latter on its own using:

$ bitbake -b ../openembedded/recipes/xorg-lib/xtrans_1.2.3.bb

don't use bitbake -b foo.bb, but bitbake foo to build single recipes.

3

Hi Koen,

I think that the key messages in that log are:

configure: error: in
`/home/ilyes/openembedded/build/tmp/work/armv7a-angstrom-linux-gnueabi/xtrans-1_1.2.3-r0/xtrans-1.2.3':

configure: error: C compiler cannot create executables
See `config.log' for more details.

I tried to invoke the compiler "armv7a-none-linux-gnueabi" from the
command line and check its output (if it really generates an a.out)
and that was OK. I dont' understant the cryptic message: "C compiler
cannot create executables". What could it be?

Regards,
Ilyes Gouta.

4

Hi,

I'm still getting those errors when doing bitbake xtrans-1.2.3. In my
local.conf under my build directory, I have:

TARGET_PREFIX = "arm-none-linux-gnueabi-"

and actually, omitting the the CC, CXX, CPP redefinitions.

#export CC="${CCACHE}arm-linux-gcc-3.4.4 ${HOST_CC_ARCH}"
#export CXX="${CCACHE}arm-linux-g++ ${HOST_CC_ARCH}"
#export CPP="arm-linux-gcc-3.4.4 -E"
#export LD="arm-linux-ld"
#export AR="arm-linux-ar"
#export AS="arm-linux-as"
#export RANLIB="arm-linux-ranlib"
#export STRIP="arm-linux-strip"

Is it OK? What happens if the build system needs to build a native
package while having at the same time CC redefined to
arm-none-linux-gnueabi-gcc?

Here is my cross-compiler version string:

[ilyes@blackrock build]$ arm-none-linux-gnueabi-gcc -v
Using built-in specs.
Target: arm-none-linux-gnueabi
Configured with: /scratch/paul/lite/linux/src/gcc-4.2/configure
--build=i686-pc-linux-gnu --host=i686-pc-linux-gnu
--target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap
--disable-libssp --disable-libgomp --disable-libstdcxx-pch
--with-gnu-as --with-gnu-ld --enable-languages=c,c++ --enable-shared
--enable-symvers=gnu --enable-__cxa_atexit
--with-pkgversion=CodeSourcery Sourcery G++ Lite 2007q3-51
--with-bugurl=https://support.codesourcery.com/GNUToolchain/
--disable-nls --prefix=/opt/codesourcery
--with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc
--with-build-sysroot=/scratch/paul/lite/linux/install/arm-none-linux-gnueabi/libc
--enable-poison-system-directories
--with-build-time-tools=/scratch/paul/lite/linux/install/arm-none-linux-gnueabi/bin
--with-build-time-tools=/scratch/paul/lite/linux/install/arm-none-linux-gnueabi/bin
Thread model: posix
gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)

Regards,
Ilyes Gouta.

5

Hi,

I'm still getting those errors when doing bitbake xtrans-1.2.3. In my
local.conf under my build directory, I have:

Take all these out. They will just cause more problems.

Has anyone built the demo image recently?

Philip

6

Philip,

Do you know about an image that would just compile fine from source code?

Regards,
Ilyes Gouta.

7

Philip,

Do you know about an image that would just compile fine from source code?

I use console-image, try that first. I'm not sure what a lighter
weight X capable image is.

Philip

8

I have, and it builds fine for both stable/2009 and .dev. Unless of course you go out and put nonsensical things in local.conf, like a TARGET_PREFIX that doesn't match, in which case: PEBKAC

regards,

Koen

9

Koen,

Can I have your local.conf?

-Ilyes

10

I use the one from http://www.angstrom-distribution.org/building-angstrom without changes.

11

Hi,

Is it *really* at all possible to build an image, let's say
console-image, using an already installed cross-compiling toolchain,
such as code sourcery's 2007q3 release, or it is inevitable that
bitbake will build the toolchain from scratch?

I followed the documentation (which seems a bit outdated), hacked some
.conf settings with some success, however despite all my efforts, it
seems like bitbake would always go through the gcc-cross-initial and
gcc-cross rules.

The main issue I'm facing is that sourcery's 2007q3 has the ARM
compiler having the form arm-none-linux-gnueabi where as bitbake looks
for armv7-angstrom-linux-gnueabi. I had also to remove the
--target=${TARGET_SYS} from the oe_configure macro to get code
sourcery's 2007q3 successfully building some packages.

Is there just a template local.conf file that shows how to use an
alternate toolchain for building the source code?

Thanks for the nice tools!

Regards,
Ilyes Gouta.

12

Hi,

Is it *really* at all possible to build an image, let's say
console-image, using an already installed cross-compiling toolchain,
such as code sourcery's 2007q3 release, or it is inevitable that
bitbake will build the toolchain from scratch?

I followed the documentation (which seems a bit outdated), hacked some
.conf settings with some success, however despite all my efforts, it
seems like bitbake would always go through the gcc-cross-initial and
gcc-cross rules.

The main issue I'm facing is that sourcery's 2007q3 has the ARM
compiler having the form arm-none-linux-gnueabi where as bitbake looks
for armv7-angstrom-linux-gnueabi. I had also to remove the
--target=${TARGET_SYS} from the oe_configure macro to get code
sourcery's 2007q3 successfully building some packages.

Is there just a template local.conf file that shows how to use an
alternate toolchain for building the source code?

Try using this article:

Philip

13

Thanks Philip!

Regards,
Ilyes Gouta.