This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)

From: DJ Delorie <dj at redhat dot com>
To: Corinna Vinschen <vinschen at redhat dot com>
Cc: uweigand at de dot ibm dot com, newlib at sourceware dot org, gcc-patches at gcc dot gnu dot org, yselkowitz at users dot sourceforge dot net, ken dot werner at de dot ibm dot com
Date: Thu, 5 May 2011 11:29:40 -0400
Subject: Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
References: <20110504111745.GD26180@calimero.vinschen.de> <201105050909.p4599SUA010092@d06av02.portsmouth.uk.ibm.com> <20110505092334.GA16123@calimero.vinschen.de>

> I don't know how to avoid this problem in configure, other than by adding
> AC_LIBOBJ([psignal]).

Right, the correct solution is - libiberty shouldn't provide psignal
if newlib does.  Making it match newlib is the wrong solution.

Follow-Ups:
- Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
  - From: Ulrich Weigand
- Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
  - From: Corinna Vinschen

References:
- Re: [PATCH] Export psignal on all platforms
  - From: Corinna Vinschen
- newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
  - From: Ulrich Weigand
- Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
  - From: Corinna Vinschen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]