This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [PATCH] Build system cleanups 1/4
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com, GCC Patches <gcc-patches at gcc dot gnu dot org>, Andreas Schwab <schwab at suse dot de>
- Date: Thu, 27 Mar 2008 11:18:32 -0400
- Subject: Re: [PATCH] Build system cleanups 1/4
- References: <47EB7269.3090309@gnu.org> <jeej9wihzp.fsf@sykes.suse.de> <47EB7928.5050407@gnu.org> <je1w5wigpv.fsf@sykes.suse.de> <47EB8026.7070506@gnu.org>
On Thu, Mar 27, 2008 at 12:08:22PM +0100, Paolo Bonzini wrote:
> Andreas Schwab wrote:
>> Paolo Bonzini <bonzini@gnu.org> writes:
>>> If so, were you aware that the target libiberty is not compiled as
>>> PIC?
>> This is not true.
>
> Here is the patch I'll test. I'll commit this as build system maintainer;
> of course any other patch to convert libiberty to libtool will have to be
> approved by the libiberty maintainers.
>
> Paolo
>2008-03-27 Paolo Bonzini <bonzini@gnu.org>
>
> * configure.ac (frags): Don't set, use frag instead.
> (PICFLAG): Set here and substitute.
> * Makefile.in: Substitute from autoconf.
> * configure: Regenerate.
FWIW, Cygwin's reliance on libiberty, so:
2008-03-27 Christopher Faylor <me+cygwin@cgf.cx>
* Makefile.in (all-target-winsup): Remove libiberty dependency.
Index: Makefile.in
===================================================================
RCS file: /cvs/uberbaum/Makefile.in,v
retrieving revision 1.279
diff -d -u -r1.279 Makefile.in
--- Makefile.in 27 Mar 2008 14:16:53 -0000 1.279
+++ Makefile.in 27 Mar 2008 15:16:59 -0000
@@ -53474,7 +53474,6 @@
all-target-libstdc++-v3: maybe-all-target-libiberty
configure-target-libstdc++-v3: maybe-configure-target-libgomp
all-target-libgloss: maybe-all-target-newlib
-all-target-winsup: maybe-all-target-libiberty
all-target-winsup: maybe-all-target-libtermcap
--
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/