Re: Fw: CT_DoExecLog error during GCC build

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Milan, All,

On Tuesday 03 August 2010 13:12:35 milan radulovic wrote:
> I would like to use crosstool-ng as cross compiler for MIPS architecture
> R4K, and I need to build cross compiler without Thread local storage
> support or threads support.
> So far, I tried to build cross compiler but I didn't make any success
> since I am getting the following error message:
> INFO ]? Installing final compiler
> [EXTRA]??? Configuring final compiler
> [EXTRA]??? Building final compiler
> [ERROR]???checking for suffix of object files... configure: error: cannot compute suffix of object files: cannot compile
> [ERROR]??? make[2]: *** 
> [configure-target-libstdc++-v3] Error 1
> [ERROR]???
>  make[1]: *** [all] Error 2
> [ERROR]??? Build failed in step 'Installing final compiler'
> [ERROR]??? Error happened in '/opt/crosstool-ng/lib/ct-ng-hg_default@2039_c5a2e4ee7fb8/scripts/functions' in function 'CT_DoExecLog' (line unknown, sorry)
> [ERROR]?called from '/opt/crosstool-ng/lib/ct-ng-hg_default@2039_c5a2e4ee7fb8/scripts/build/cc/gcc.sh' at line # 414 in function 'do_cc'
> [ERROR] called from '/opt/crosstool-ng/lib/ct-ng-hg_default@2039_c5a2e4ee7fb8/scripts/crosstool-NG.sh' at line # 583 in function 'main'
> [ERROR]??? Look at '/root/x-tools/mips-unknown-linux-uclibc/build.log' for more info on this error.
> [ERROR]? (elapsed: 36:36.24)
> [36:37] / make: *** 
> [build] Error 2

That's not quite enough to track the issue. The full build.log file is
required.

Anyway, you can start to look at the config.log file in the gcc build
directory. It can be either failing in the top-level ./configure, or in
one of the sub-directories. Look at the buildlog file, and see where
it is failing exactly. Search starting there:
  targets/mips-unknown-linux-uclibc/build/build-cc/

> Threading implementation to use: none

Hmmm... No-thread is not something that I do test very often.

I just tried to build the mips-unknown-linux-uclibc sample, with
your changes, and it builds fine here.

> Please, find attached the printout during building.

The complete build.log file is needed to see what is really going on.
In there you can see exactly what part of gcc is failing, and why it
is failing.

Put the complete build.log file on some website, and send the URL so
we can have a look. If it is smaller than 500KiB, you may attach it,
but putting it on a website is better, eg. pastebin.com

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



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