libtool 20030216: problem recognizing import libraries

[Charles Wilson]

Okay, the patch I posted to libtool-patches works on my system (of 
course, the UNpatched libtool works on my system) -- but the patch ought 
to fix this problem.  It hunts specifically for head.exe and uses that, 
if found, falling back to 'head' only if 'head.exe' is not found in the 
path.

I'd give a link, but it hasn't shown up yet.  Go here
http://mail.gnu.org/archive/html/libtool-patches/2003-03/index.html
and click 'reload' until it does.  I'm off to bed.

--Chuck

Charles Wilson wrote:

> Maybe, but I'm NOT going to require that folks who want to build 
> ANYTHING that uses libtool to set check_case on their machine.
> 
> But I also can't hardcode "head.exe" because that would break 
> cygwin-target cross-compiles (the build platform's native head is 
> certainly not 'head.exe' -- and the build platform probably doesn't 
> suffer from 'case-insensitive/case-preserving' filesystem, coupled with 
> 'automatic appending of .exe'.
> 
> I think this will actually require more intrusive hacking in libtool; 
> detect the "appropriate" name for head on the build platfrom, set a 
> variable, use that, instead of invoking 'head' directly.
> 
> I don't think perl will EVER fix their problem; for all their talk about 
> platform neutrality they have KNOWN about this problem for ages (since 
> long before last Sept, Igor) and have evidenced no intention of fixing it.
> 
> "Hey guys, there's a name conflict between one of your packages's 
> scripts and a widely deployed binary from the textutils package"
> 
> "That only affects cygwin; fixing it would break thousands of apps on 
> dozens of platforms."
> 
> So we need to come up with a way around it.  I'll try to come up with 
> something.  It'll probably involve hacking libtool.m4...and I better get 
> cracking.  libtool-1.5 is due out before April 15.
> 
> --Chuck
> 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/