[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-readline] making shared link failures fatal

From: Chet Ramey
Subject: Re: [Bug-readline] making shared link failures fatal
Date: Sat, 26 Mar 2011 13:47:20 -0400
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7

On 3/25/11 2:55 PM, Mike Frysinger wrote:

>> The question is whether or not a failure to build the shared version of
>> readline should cause the build to fail, even if the static library is
>> created successfully.
> i cant see how ignoring the shared link is sane anymore.  what
> reasonable OS doesnt use shared libraries anymore ?

That doesn't have anything to do with it.  If I've made a mistake in
shobj-conf or shlib-install, should that kill the build?  It's ok if
your answer is "yes," and I'm open to the discussion.  I was starting
to come around to your position, as a matter of fact.

> how unreasonable is it really to have the 1 or 2 random people running
> on old pos hardware to pass --disable-shared at configure time ?
> or even better, why not just convert to libtool already ?  every other
> major project out there has long ago switched to libtool.  that would
> detect whether the target supports shared libraries at configure time
> and disable it by default.

I'd advise you to take a look at it before shooting from the hip next
time.  The readline build system has always detected supported and
unsupported systems at configure time.  It's reasonable to have a
discussion about this, but don't pull bogus arguments out of your ass
to do it.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]