mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Preparation of Release 2.17 - Final Test


From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] Preparation of Release 2.17 - Final Test
Date: Mon, 6 Dec 2010 09:43:18 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

Gregory Smith <address@hidden> schrieb:
> I didn't try a full build, but I do have a failure building boost with
> 1477:97d8ffa87fa1. This is Fedora 14, 64-bit. Log attached.

The critical part seems to be:

----------------------------------------------------------------------
gcc.compile.c++ 
bin.v2/libs/wave/build/gcc-mingw-4.5.1/debug/link-static/target-os-windows/threadapi-win32/threading-multi/instantiate_cpp_grammar.o
/tmp/ccKZuiyd.s: Assembler messages:
/tmp/ccKZuiyd.s:215377: Error: junk at end of line, first unrecognized 
character is `:'

    "i686-pc-mingw32-g++"  -ftemplate-depth-128 -O0 -fno-inline -Wall -g 
-mthreads  -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_USE_LIB=1  -I"." -c -o 
"bin.v2/libs/wave/build/gcc-mingw-4.5.1/debug/link-static/target-os-windows/threadapi-win32/threading-multi/instantiate_cpp_grammar.o"
 "libs/wave/src/instantiate_cpp_grammar.cpp"

...failed gcc.compile.c++ 
bin.v2/libs/wave/build/gcc-mingw-4.5.1/debug/link-static/target-os-windows/threadapi-win32/threading-multi/instantiate_cpp_grammar.o...
gcc.compile.c++ 
bin.v2/libs/wave/build/gcc-mingw-4.5.1/debug/link-static/target-os-windows/threadapi-win32/threading-multi/instantiate_cpp_literalgrs.o
/tmp/ccg0ixOW.s: Assembler messages:
/tmp/ccg0ixOW.s:196981: Error: junk at end of line, first unrecognized 
character is `:'
/tmp/ccg0ixOW.s:379891: Error: junk at end of line, first unrecognized 
character is `<'
/tmp/ccg0ixOW.s:380593: Error: junk at end of line, first unrecognized 
character is `:'
----------------------------------------------------------------------

Does anyone have an idea about those?

> This is with JOBS=4. Trying again without JOBS=4, but that could take a while.

Yes, please do that.

Although this might not solve the issue, it'll provide less confusing
log messages.


Greets,
Volker

-- 
Volker Grabsch
---<<(())>>---



reply via email to

[Prev in Thread] Current Thread [Next in Thread]