[oe] cannot compute suffix of object files

[Khem Raj]

On Wed, Jan 21, 2009 at 9:47 AM, Claudiu Mdc <claudiu_fw85 at yahoo.it> wrote:
> Hi,
>
> I am building bootstrap-image with OpenEmbedded, but it fails on
> glibc-2.5 configure task with this error:
>
> | checking whether ln -s works... yes
> | checking for i686-angstrom-linux-gcc...
> i686-angstrom-linux-gcc-4.3.1 -mcpu=pentiumpro
> | checking for suffix of object files... configure: error:
>  cannot compute suffix of object files: cannot compile
> | See `config.log' for more details.
>
>
> config.log:
>
> configure:2776: checking for suffix of object files
> configure:2797: i686-angstrom-linux-gcc-4.3.1 -mcpu=pentiumpro -c
> -I/home/claudiu/oe/oetmp/staging/i686-angstrom-linux/include,
> -I/home/claudiu/oe/myToolchain/cross/include  -fexpensive-optimizations
> -fomit-frame-pointer -frename-registers -Os  conftest.c >&5
> /home/claudiu/oe/oetmp/work/i686-angstrom-linux/glibc-2.5-r10/
> glibc-2.5/configure:
> line 2798: i686-angstrom-linux-gcc-4.3.1: command not found
> configure:2800: $? = 127
> configure: failed program was:
> | /* confdefs.h.  */
> |
> | #define PACKAGE_NAME "GNU C Library"
> | #define PACKAGE_TARNAME "c-library"
> | #define PACKAGE_VERSION "(see version.h)"
> | #define PACKAGE_STRING "GNU C Library (see version.h)"
> | #define PACKAGE_BUGREPORT "glibc"
> | #define USE_REGPARMS 1
> | /* end confdefs.h.  */
> |
> | int
> | main ()
> | {
> |
> |   ;
> |   return 0;
> | }
> configure:2814: error:
> cannot compute suffix of object files: cannot compile
>
>
>
> I don't understand why in config.log it says:
> i686-angstrom-linux-gcc-4.3.1: command not found
>
>
> I've built a custom toolchain and it is in PATH:
> ~/oe$ i686-angstrom-linux<TAB><TAB> gives this output:
>
> i686-angstrom-linux-addr2line
> i686-angstrom-linux-gcc
> i686-angstrom-linux-objdump
> i686-angstrom-linux-ar
> i686-angstrom-linux-gcc-4.3.1
> i686-angstrom-linux-ranlib
> i686-angstrom-linux-as
> i686-angstrom-linux-gccbug
> i686-angstrom-linux-readelf
> i686-angstrom-linux-c++
> i686-angstrom-linux-gcov
> i686-angstrom-linux-size
> i686-angstrom-linux-c++filt
> i686-angstrom-linux-ld
> i686-angstrom-linux-strings
> i686-angstrom-linux-cpp
> i686-angstrom-linux-nm
> i686-angstrom-linux-strip
> i686-angstrom-linux-g++
> i686-angstrom-linux-objcopy
>

Are you certain that same path that you are using is available to bitbake ?