Hi Gerardo,
sorry, I was so busy these days I just forgot to reply and I somehow just
remembered now, ...
Usually it is these days related to -std=c99 or so, ... had to fight with
coreutils as well, see r40001:
-# does not build otherwise
-var_append GCC_WRAPPER_INSERT ' ' '-std=gnu99'
+# the configure adds -std=gnu99 to CC; otherwise we get missing pthread symbols
+var_remove_regex makeopt ' ' 'CC=.*'
So maybe removing explicit CC form the make opts works for your case, too in
case configure does tricky stuff and requires certain flags added in the
Makefile, ...
You can debug via:
cd src.*
./debug.sh
cd ...whatever...
GCC_WRAPPER_DEBUG=1
...whatever...
typed from memory, untested, may contain subtile typos, ..
PS: if I do not respond in some 24h or so just keep pining me, chances it just
scrolled by during my daily workload, though I hope the rest of the year is not
as busy as the first month of 2012, ...
Hope this helps,
René
On 16.02.2012, at 22:55, Gerardo Di Iorio wrote:
> hi,
> i now try to build nodejs,
> but i have an problem with gcc option.
> If i manual build nodejs work fine, if build in t2 enviroment fail.
> How to can 'debug' the the gcc option ????
>
> Regards
> Gerardo Di Iorio
--
René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
http://exactcode.com | http://t2-project.org | http://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
