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] |
On Thu, Oct 7, 2010 at 10:38 PM, Samson Luk <samsonluk@gmail.com> wrote: > 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? Yes. > 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 This is ok. try changing your directory to: // or /home/$USERNAME// It would be the same as: cd ././ (which would be the current directory) The double slash is coming from ${CT_SYSROOT_DIR_PREFIX} being empty. Which I think is only needed for cross-canadian toolchains. > 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? I personally find it easier and more reliable to 'ct-ng clean' and then run 'ct-ng build' instead of trying to resume at the step that the build failed. But, you can enable CT_DEBUG_CT and CT_DEBUG_CT_SAVE_STEPS, and you should be able to restart at a step that failed. You have to restart your build with 'ct-ng clean; ct-ng build' before you can use the saved steps. If libc breaks again, and you somehow fix your issue, you can try: ct-ng RESTART=libc > 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 There is lots of great documentation in crosstool-ng/docs. A lot of what I know about crosstool-ng comes from these documents, and reading the scripts. It also helps to know a little about autoconf, automake, libtool (http://sourceware.org/autobook), gnu make, and bash scripting. Good Luck, -Bryan -- 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] |