[oe] minimo: task do_configure failed

Mark Butsch mbutsch at syntech-fuelmaster.com
Fri May 15 16:28:48 UTC 2009


Hello,

I asked this question back in March but never saw a response.

I am trying to build minimo (angstrom distro) and it is failing in do_configure.

OE Build Configuration:
BB_VERSION        = "1.8.13"
METADATA_BRANCH   = "stable/2009"
METADATA_REVISION = "481398457bcc88395b07c4c724c4def42be36fd2"
TARGET_ARCH       = "i686"
TARGET_OS         = "linux"
MACHINE           = "4g-i686"
DISTRO            = "angstrom"
DISTRO_VERSION    = "2009.X-test-20090515"

I am building on an x86 64 bit OS for a x86 32 bit target.

The log file is:

-----------
NOTE: make -f client.mk CONFIGURE_ARGS= --build=x86_64-linux --host=x86_64-linux --target=i686-angstrom-linux  configure
cd /home/ad/mbutsch/4G/tmp/angstrom/work/i686-angstrom-linux/minimo-1_0.02+cvs20070626-r1/mozilla
./configure --build=x86_64-linux --host=x86_64-linux --target=i686-angstrom-linux
Adding configure options from /home/ad/mbutsch/4G/tmp/angstrom/work/i686-angstrom-linux/minimo-1_0.02+cvs20070626-r1/mozconfig:
  --enable-application=minimo
  --enable-default-toolkit=gtk2
  --disable-freetype2
  --enable-xft
  --disable-postscript
  --disable-xprint
  --disable-gnomevfs
  --disable-gnomeui
  --disable-jsd
  --disable-plugins
  --disable-view-source
  --disable-accessibility
  --disable-xpinstall
  --enable-single-profile
  --disable-jsloader
  --disable-printing
  --enable-native-uconv
  --enable-plaintext-editor-only
  --disable-xpcom-obsolete
  --disable-pref-extensions
  --disable-extensions
  --enable-image-decoders=png,gif,jpeg
  --disable-mathml
  --disable-installer
  --disable-updater
  --disable-tests
  --enable-optimize=-Os
  --disable-logging
  --enable-strip
  --enable-elf-dynstr-gc
  --disable-shared
  --enable-static
  --disable-profilesharing
  --disable-profilelocking
loading site script /home/oe/openembedded/site/endian-little
loading site script /home/oe/openembedded/site/common-linux
loading site script /home/oe/openembedded/site/common-glibc
loading site script /home/oe/openembedded/site/ix86-common
loading site script /home/oe/openembedded/site/common
loading site script /home/oe/openembedded/site/common
creating cache ./config.cache
checking host system type... x86_64-pc-linux-gnu
checking target system type... i686-angstrom-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking for gawk... gawk
checking for nsinstall... no
cross compiling from x86_64-pc-linux-gnu to i686-angstrom-linux-gnu
checking for host c compiler... checking for gcc... (cached) gcc
gcc
checking for host c++ compiler... checking for c++... (cached) g++
g++
checking for ranlib... no
checking for ar... no
checking whether the host c compiler (gcc -isystem/home/ad/mbutsch/4G/tmp/angstrom/staging/i686-angstrom-linux/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -march=i486 -L/home/ad/mbutsch/4G/tmp/angstrom/staging/i686-angstrom-linux/usr/lib -Wl,-rpath-link,/home/ad/mbutsch/4G/tmp/angstrom/staging/i686-angstrom-linux/usr/lib -Wl,-O1 -Wl,--hash-style=gnu) works... configure: error: installation or configuration problem: host compiler gcc cannot create executables.
*** Fix above errors and then restart with               "make -f client.mk build"
make: *** [configure] Error 1
FATAL: oe_runmake failed
-----------


In looking at the log.do_configure file, the invocation for the configure is:



NOTE: make -f client.mk CONFIGURE_ARGS= --build=x86_64-linux --host=x86_64-linux  --target=i686-linux  configure



It looks strange to me that the 'build' and 'host' are the same. The recipe for minimo_cvs has the line:



EXTRA_OECONF += "--build=${BUILD_SYS} --host=${BUILD_SYS} --target=${TARGET_SYS} "



And uses EXTRA_OECONF when invoking oe_runmake. It seems to me that '--host' should specify ${HOST_SYS} and if I make that edit, it does successfully build.





For my education, what are 'build', 'host' and 'target' referring to in this case?



-     'target' should be the target that is being built for

-     'build' should be the machine that is doing the building

-     'host' not sure?


Mark



More information about the Openembedded-devel mailing list