Re: ct-ng 1.8.2 how to select gcc 4.5.x ?

[Samson Luk <samsonluk at gmail dot com>]

Yann, All,

> This is a known issue. glibc does not build with 'fortify'.
> Please try setting:
>  C-library  --->
>  (-U_FORTIFY_SOURCE)  extra target CFLAGS

I suppose this also apply to eglibc?

I also found symlinks with "double slash" in path like below in the
target tree, are they normal, why is that using "double slash"?

/opt/x-tools/arm-none-linux-gnueabi/arm-none-linux-gnueabi$ ls -la
total 20
drwxr-xr-x 5 root root 4096 2010-10-07 23:26 .
drwxr-xr-x 7 root root 4096 2010-10-07 23:26 ..
drwxr-xr-x 2 root root 4096 2010-10-07 23:26 bin
drwxr-xr-x 2 root root 4096 2010-10-07 20:38 debug-root
lrwxrwxrwx 1 root root   23 2010-10-07 20:38 include -> .//sys-root/usr/include
lrwxrwxrwx 1 root root   15 2010-10-07 20:38 lib -> .//sys-root/lib
drwxr-xr-x 4 root root 4096 2010-10-07 20:38 sys-root

Beside, why is that required to generate two levels of
"arm-none-linux-gnueabi", can I eliminate one level or there are
special purposes for setup like this?

When a 'ct-ng build' aborted and configuration adjusted / problem
fixed, is it safe to simple 'ct-ng build' again or should I resume
from the exact failed step?  Is there easy way to figure out which is
the current step or have to dig through the build log?

Thank you for your patient to all these newbie questions...  I really
learn a lot from this tool because it actually let you see the real
process in action with logs to examine how things get done step by
step and what configuration being used, etc.

Regards,
Samson

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