From: Andrew Pinski <pinskia@gmail.com>
To: Pavel Chupin <pavel.v.chupin@gmail.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
Igor Zamyatin <izamyatin@gmail.com>
Subject: Re: [PATCH, libstdc++] Fix missing gthr-default.h issue on libstdc++ configure
Date: Fri, 05 Oct 2012 23:47:00 -0000 [thread overview]
Message-ID: <CA+=Sn1mAxvO5s==TR2AW-NXyc=BwD7wC-pmXPs=0X1tuF9a4=w@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1mBVm2j7O8PqK+ZaynWF-zi5QNSsf-v52R6VbP68GrQaA@mail.gmail.com>
On Fri, Oct 5, 2012 at 12:13 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> On Fri, Oct 5, 2012 at 7:32 AM, Pavel Chupin <pavel.v.chupin@gmail.com> wrote:
>> I can't configure libstdc++ separately. To reproduce:
>>
>> mkdir BUILD
>> cd BUILD
>> ../libstdc++-v3/configure
>>
>> Error:
>> make: *** No rule to make target
>> `/users/pvchupin/android/toolchain/gcc/gcc-4.8/BUILD/../libgcc/gthr-default.h',
>> needed by `bits/gthr-default.h'. Stop.
>>
>> See fix attached.
>>
>> Ok for trunk and 4.7?
>
> Why do you want to compile libstdc++ separately from GCC? I think you
> need to explain why you want to do that. In fact libstdc++ depends on
> libgcc internals is not a bug but rather a feature.
One more thing is that for cases where target==host!=build, you can
just use the libraries which are produced by the cross compiler and
use "make all-host" and "make install-host" for the programs.
This should simplify how Yocto builds the "native" GCC and not
worrying about building libstdc++ separately.
Thanks,
Andrew Pinski
>
> Thanks,
> Andrew Pinski
>
>
>
>>
>> 2012-10-05 Pavel Chupin <pavel.v.chupin@intel.com>
>>
>> Fix missing gthr-default.h issue on separate libstdc++ configure
>> * libstdc++-v3/acinclude.m4: Define glibcxx_thread_h.
>> * libstdc++-v3/include/Makefile.am: Use glibcxx_thread_h.
>> * libstdc++-v3/Makefile.in: Regenerate.
>> * libstdc++-v3/configure: Regenerate.
>> * libstdc++-v3/doc/Makefile.in: Regenerate.
>> * libstdc++-v3/include/Makefile.in: Regenerate.
>> * libstdc++-v3/libsupc++/Makefile.in: Regenerate.
>> * libstdc++-v3/po/Makefile.in: Regenerate.
>> * libstdc++-v3/python/Makefile.in: Regenerate.
>> * libstdc++-v3/src/Makefile.in: Regenerate.
>> * libstdc++-v3/src/c++11/Makefile.in: Regenerate.
>> * libstdc++-v3/src/c++98/Makefile.in: Regenerate.
>> * libstdc++-v3/testsuite/Makefile.in: Regenerate.
>>
>> --
>> Pavel Chupin
>> Intel Corporation
next prev parent reply other threads:[~2012-10-05 23:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 14:32 Pavel Chupin
2012-10-05 19:13 ` Andrew Pinski
2012-10-05 23:47 ` Andrew Pinski [this message]
2012-10-08 13:44 ` Pavel Chupin
2012-10-08 14:05 ` Paolo Carlini
2012-10-08 14:26 ` Pavel Chupin
2012-10-08 14:51 ` Paolo Carlini
2012-10-09 0:50 ` Benjamin De Kosnik
2012-10-09 9:59 ` Pavel Chupin
2012-10-09 17:47 ` Benjamin Kosnik
2012-10-10 12:06 ` Kirill Yukhin
2012-10-11 13:16 ` Olivier Hainque
2012-10-11 14:51 David Edelsohn
2012-10-11 15:03 ` Pavel Chupin
2012-10-11 15:12 ` Rainer Orth
2012-10-11 18:24 ` Pavel Chupin
2012-10-12 11:31 ` Kirill Yukhin
2012-10-12 12:51 ` David Edelsohn
2012-10-12 14:21 ` Pavel Chupin
2012-10-12 15:01 ` Paolo Carlini
2012-10-13 19:42 ` David Edelsohn
2012-10-15 13:21 ` Kirill Yukhin
2012-10-15 14:01 ` Olivier Hainque
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='CA+=Sn1mAxvO5s==TR2AW-NXyc=BwD7wC-pmXPs=0X1tuF9a4=w@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=izamyatin@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=pavel.v.chupin@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).