From: Paolo Bonzini <bonzini@gnu.org>
To: Andreas Schwab <schwab@suse.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
cygwin@cygwin.com
Subject: Re: [PATCH] Build system cleanups 1/4
Date: Thu, 27 Mar 2008 10:56:00 -0000 [thread overview]
Message-ID: <47EB7928.5050407@gnu.org> (raw)
In-Reply-To: <jeej9wihzp.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Paolo Bonzini <bonzini@gnu.org> writes:
>
>> This one removes the PICFLAG variables, which are never set, as well as
>> the makefile fragments that used to set PICFLAG *at the time of Cygnus
>> configure*.
>>
>> Committed to gcc and (shortly) to src.
>
> AFAICS this is used by libiberty when --enable-shared.
Also, considering that libstdc++ compiles its own cp-demangle.c, and has
always done so since it started using the libiberty demangler (r78553):
cp-demangle.c:
rm -f $@
$(LN_S) $(toplevel_srcdir)/libiberty/cp-demangle.c $@
cp-demangle.lo: cp-demangle.c
$(LTCOMPILE) -DIN_GLIBCPP_V3 -Wno-error -c $<
cp-demangle.o: cp-demangle.c
$(C_COMPILE) -DIN_GLIBCPP_V3 -Wno-error -c $<
I wonder why we still compile libiberty for the target at all. Neither
it nor libobjc needs it, which would leave only all-target-fastjar
(which is a bogus target anyway) and all-target-winsup.
Cygwin people, does winsup actually need a target libiberty? If so,
were you aware that the target libiberty is not compiled as PIC?
Paolo
next prev parent reply other threads:[~2008-03-27 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 10:31 Paolo Bonzini
2008-03-27 10:48 ` Andreas Schwab
2008-03-27 10:55 ` Paolo Bonzini
2008-03-27 11:09 ` Andreas Schwab
2008-03-27 10:56 ` Paolo Bonzini [this message]
2008-03-27 11:21 ` Andreas Schwab
2008-03-27 13:45 ` Paolo Bonzini
2008-03-27 15:46 ` Christopher Faylor
2008-03-27 15:49 ` Christopher Faylor
2008-03-27 19:27 ` Paolo Bonzini
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=47EB7928.5050407@gnu.org \
--to=bonzini@gnu.org \
--cc=cygwin@cygwin.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).