Re: Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition)

2011-06-22 Thread Hans-Peter Nilsson
Date: Mon, 20 Jun 2011 16:58:41 + (UTC) From: Joseph S. Myers jos...@codesourcery.com On Mon, 20 Jun 2011, Hans-Peter Nilsson wrote: It seems none in approval capacity have any objection to (figuratively) s/target-libiberty//g in toplevel/configure.ac on all branches. Is an

Re: Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition)

2011-06-22 Thread DJ Delorie
Ok for trunk? Ok with me. I'll let the branch maintainers decide if they want it for their branches.

Re: Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition)

2011-06-22 Thread Hans-Peter Nilsson
Date: Wed, 22 Jun 2011 20:16:48 +0200 From: Hans-Peter Nilsson h...@axis.com PR47836 PR23656 PR47733 PR49247 * configure.ac (target_libraries): Remove target-libiberty. ... JFTR, that's not proper PR annotation. I changed it as obvious to the following,

Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition)

2011-06-20 Thread Hans-Peter Nilsson
On Wed, 18 May 2011, Joseph S. Myers wrote: On Wed, 18 May 2011, DJ Delorie wrote: At this point, though, I'm tempted to say there's no such thing as a target libiberty and rip all the target-libiberty rules out, and let Yes please. I've been arguing for that for some time.

Re: Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition)

2011-06-20 Thread Joseph S. Myers
On Mon, 20 Jun 2011, Hans-Peter Nilsson wrote: It seems none in approval capacity have any objection to (figuratively) s/target-libiberty//g in toplevel/configure.ac on all branches. Is an --enable-target-libiberty or --with-target-libiberty needed? (I'd just rather not.) There should be