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] |
Hi, On Tue, Oct 19, 2010 at 4:19 AM, Bryan Hundven <bryanhundven@gmail.com> wrote: > Arnaud, > > I think the gxx-include-dir param is a workaround. > no, it's just a plain bug. > I believe that something else is falling off the rails early during > the ct-ng build that cause (e)glibc to need the > ${CT_SYSROOT_DIR}/include symlink or it installs the headers to the > wrong spot, that ultimately screws up the final cc's g++ include > search path. > I still fails to see where this "${CT_SYSROOT_DIR}/include" come from. > I have been working on trying to figure this one out. When we can > figure this out, we should remove the --with-gxx-include-dir! > it should never have been added. > I also saw strange behavior when both > CC_EXTRA_CONFIG=--with-long-double-128 and > CC_GCC_LDBL_128=m were set. > given that the implementation is yet again buggy, I'm not surprised... case "${CT_CC_GCC_LDBL_128}" in Y) extra_config+=("--with-long-double-128");; M) ;; "") extra_config+=("--without-long-double-128");; esac case sentivity boys, case sensitivity... - Arnaud > Lets let Tony finish his build, test, and report cycle. > > In the mean time, lets keep working on the c++ include path issue in > the respective thread ;-) > > -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] |