This is the mail archive of the
crossgcc@sourceware.org
mailing list for the crossgcc project.
See the CrossGCC FAQ for lots
more information.
Re: [PATCH] sample config for arm-unkown-linux-gnueabi, gcc-4.4.0, glibc-2.9
Hello, Yann! Hello All!
> CT_SYSROOT_DIR_PREFIX is *not* an absolute path!
> Carefully read the help entry, please!
>
Sorry, I missed this...
> > CT_CC_EXTRA_CONFIG="CFLAGS=-ggdb3"
> >
> >
> Why is that needed? This will build the _cross-gcc_ with debugging
symbols,
> thus making the cross-gcc bigger and slower! Unless I'm mistaken...
>
> And unless you are debugging gcc, it is a bad idea, IMHO...
We needed debug info in gcc, because there was an error in February
snapshot,
so crosstool failed at building glibc (it was workarounded then by changing
the default optimization level -- there was -O option by default in glibc
Makefile with which it failed, but worked with -O2).
The issue has been fixed in the current snapshot, and glibc now builds
fine with -O.
> > #
> > # Additional supported languages:
> > #
> > CT_CC_LANG_CXX=y
> > # CT_CC_LANG_FORTRAN is not set
> > # CT_CC_LANG_JAVA is not set
> >
> >
> Other gcc versions were able to build the Fortran and Java frontends.
> Did you disable them because they did not work, or simply because you
> did not need them?
We didn't build other languages because we don't need them so we've
disabled them just to save time.
> So, how did you manage to use the 4.3.3 patchset with 4.4-20090320?
We thought we were using this patchset, but actually it isn't applied at
all,
because we put it on directory 4.4.0 and missed that ct-ng searches it in
4.4-20090320. We believed that the patches were successfully applied
since ct-ng said "Applying patches for gcc" in log files and created
"gcc*.patched" file. So it seems actually to be working for this target
without
any patches.
---
Dmitry.
--
For unsubscribe information see http://sourceware.org/lists.html#faq