This is the mail archive of the
mailing list for the Cygwin project.
Re: [PATCH] Build system cleanups 1/4
- From: Paolo Bonzini <bonzini at gnu dot org>
- To: Andreas Schwab <schwab at suse dot de>, GCC Patches <gcc-patches at gcc dot gnu dot org>, cygwin at cygwin dot com
- Date: Thu, 27 Mar 2008 11:38:32 +0100
- Subject: Re: [PATCH] Build system cleanups 1/4
- References: <47EB7269.firstname.lastname@example.org> <email@example.com>
Andreas Schwab wrote:
Paolo Bonzini <firstname.lastname@example.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
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):
rm -f $@
$(LN_S) $(toplevel_srcdir)/libiberty/cp-demangle.c $@
$(LTCOMPILE) -DIN_GLIBCPP_V3 -Wno-error -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?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html