X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <47EB7928.5050407@gnu.org> Date: Thu, 27 Mar 2008 11:38:32 +0100 From: Paolo Bonzini User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Andreas Schwab , GCC Patches , cygwin@cygwin.com Subject: Re: [PATCH] Build system cleanups 1/4 References: <47EB7269.3090309@gnu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Andreas Schwab wrote: > Paolo Bonzini 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 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/