This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

crosstool-NG: binutils config fails each time


  i'm currently chatting with ct-ng developer yann morin about this,
but i figured i might post here and see if anyone's noticed this and
has some ideas.

  i'm trying to use the svn HEAD of ct-ng to build some sample
toolchains and, to that end, i'm just trying to duplicate the
allegedly successful builds that yann advertises and that are defined
by the config files under the samples/ directory (see web page
here: http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool).

  in every case, regardless of architecture, the configuration of
binutils fails early on.  i've attached the binutils config log
generated by ct-ng, and here's what looks like the relevant portions:

...
PATH: /opt/x-tools/x86_64-unknown-linux-uclibc/bin
PATH: /home/rpjday/ctng/dev/targets/x86_64-unknown-linux-uclibc/build/gcc-core-shared/bin
PATH: /home/rpjday/ctng/dev/targets/x86_64-unknown-linux-uclibc/build/gcc-core-static/bin
...

  so, near the top, the search path clearly includes that first entry,
which is where the symlinks to the native build tools are.  not much
further down, we see:

...
configure:1501: checking build system type
configure:1519: result: i686-pc-linux-gnu
configure:1554: checking host system type
configure:1568: result: i686-pc-linux-gnu
configure:1576: checking target system type
configure:1590: result: x86_64-unknown-linux-uclibc
configure:1633: checking for a BSD-compatible install
configure:1688: result: /usr/bin/install -c
configure:1699: checking whether ln works
configure:1721: result: yes
configure:1725: checking whether ln -s works
configure:1729: result: yes
configure:2782: checking for i686-pc-linux-gnu-gcc
configure:2798: found /opt/x-tools/x86_64-unknown-linux-uclibc/bin/i686-pc-linux-gnu-gcc
configure:2808: result: i686-pc-linux-gnu-gcc
...

  good, good ... the configuration process successfully locates the
executable called "i686-pc-linux-gnu-gcc" in the correct directory.
but immediately thereafter, we see:

...
configure:3090: checking for C compiler version
configure:3093: i686-pc-linux-gnu-gcc --version </dev/null >&5
i686-pc-linux-gnu-gcc: No such file or directory
configure:3096: $? = 1
configure:3098: i686-pc-linux-gnu-gcc -v </dev/null >&5
i686-pc-linux-gnu-gcc: No such file or directory
configure:3101: $? = 1
configure:3103: i686-pc-linux-gnu-gcc -V </dev/null >&5
i686-pc-linux-gnu-gcc: No such file or directory
configure:3106: $? = 1
configure:3129: checking for C compiler default output file name
configure:3132: i686-pc-linux-gnu-gcc  -pipe   conftest.c  >&5
i686-pc-linux-gnu-gcc: No such file or directory
...

  huh?  the config process *just* claimed that it could find the
executable by that name; now, suddenly, it can't, which causes the
whole process to subsequently abort.

  this is the result no matter which architecture i choose, so i'm
convinced it's not a problem with ct-ng, but more with binutils or my
development setup.

  yann tells me he can create those toolchains under ubuntu, but i'm
working with a fully-updated version of fedora 8, so there *must* be
some fundamental difference here.  why would the binutils process
clearly be able to locate that executable, then suddenly not be able
to find it again (at least under fedora 8)?

  thoughts?  advice?

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

Attachment: config.log
Description: Text document

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]