From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: GCC 4.3 fails to build glibc(-intermediate)
Date: Wed, 04 Jun 2008 16:22:06 -0700 [thread overview]
Message-ID: <4847239E.90404@gmail.com> (raw)
In-Reply-To: <g25tes$bdb$1@ger.gmane.org>
Koen Kooi wrote:
> Matthijs van de Water wrote:
>> Did anyone working with GCC 4.3 have any problems with the C++
>> compiler in the SDK?
>>
>> With the current setup, my include path search order is such that for
>> instance the<cstdlib> header is trying to #include_next<stdlib.h>,
>> which fails because the normal include paths precede the C++ include
>> paths.
>> If I change the #include_next to #include the headers work fine, but
>> that is obviously no solution. It looks like this is broken for all
>> sysroot builds, because the compiler will put the sysroot include
>> before the C++ ones and get rid of any duplicates.
>>
>> Did anyone see this before?
>
> I did see that before as well.
I was seeing this too while compiling libusb. However when I did not use --with-gxx-headers option
and did not move the headers manually to STAGING_DIR this worked even with c_global scope.
>
>> Any suggestions? I think I can solve this
>> by changing back to --enable-cheaders=c_std instead of c_global (which
>> was the default previously and which is why pre-4.3 toolchains work
>> fine for me), but I'm not sure of the implications of that.
>
> Maybe we try something like this:
>
> --- packages/gcc/gcc-4.3.0.inc 7dac0d4ea94fbc3071cf13542d7afc9c97598920
> +++ packages/gcc/gcc-4.3.0.inc d4ceae7672f475a16184235ac603437f86c3079e
> @@ -68,5 +68,5 @@ JAVA = ""
> FORTRAN = ""
> JAVA = ""
>
> -EXTRA_OECONF_BASE = " --enable-libssp --disable-bootstrap
> --disable-libgomp --disable-libmudflap"
> +EXTRA_OECONF_BASE = " --enable-cheaders=c_std --enable-libssp
> --disable-bootstrap --disable-libgomp --disable-libmudflap"
>
> ============================================================
> --- packages/gcc/gcc-cross_4.3.0.bb
> 1ed2f60e65e1b09e4a5637ab29c85ad02338061f
> +++ packages/gcc/gcc-cross_4.3.0.bb
> cc76abacb299b51bb7da2b6bc0a6f7bec093ebeb
> @@ -7,6 +7,12 @@ SRC_URI_append_fail-fast = " file://zeck
>
> SRC_URI_append_fail-fast = " file://zecke-no-host-includes.patch;patch=1 "
>
> -EXTRA_OECONF += "--disable-libunwind-exceptions
> --with-mpfr=${STAGING_DIR_NATIVE}${layout_exec_prefix}"
> +EXTRA_OECONF += " --enable-cheaders=c_std
> --disable-libunwind-exceptions
> --with-mpfr=${STAGING_DIR_NATIVE}${layout_exec_prefix}"
Adding this option worked for me and I could build console-image.
>
>
> regards,
>
> Koen
>
>
>>
>> Regards,
>>
>> Matthijs
>>
>> --enable-cheaders=OPTION
>>
>> This allows the user to define the approach taken for C header
>> compatibility with C++. Options are c, c_std, and c_global. These
>> correspond to the source directory's include/c, include/c_std, and
>> include/c_global, and may also include include/c_compatibility. The
>> default is c_global.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2008-06-04 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70c9a9110805220710x6663f582lc5d6b75744960d08@mail.gmail.com>
2008-05-22 14:11 ` GCC 4.3 fails to build glibc(-intermediate) Enric Balletbò i Serra
2008-05-22 15:44 ` Khem Raj
2008-05-22 18:24 ` Rolf Leggewie
2008-05-23 0:02 ` Khem Raj
2008-05-23 6:17 ` Rolf Leggewie
2008-05-23 6:36 ` Rolf Leggewie
2008-05-28 7:01 ` Khem Raj
2008-05-28 7:36 ` Koen Kooi
2008-05-28 9:52 ` Matthijs van de Water
2008-05-28 11:22 ` Rolf Leggewie
2008-06-03 7:16 ` Matthijs van de Water
2008-06-04 11:14 ` Koen Kooi
2008-06-04 23:22 ` Khem Raj [this message]
2008-05-07 14:33 Matthijs van de Water
2008-05-07 16:21 ` Khem Raj
2008-05-07 17:02 ` Matthijs van de Water
2008-05-07 18:31 ` Leon Woestenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4847239E.90404@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox