Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<0a2e01c5c83c$51de8e20$5304a8c0@chimaera>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Cygwin" <cygwin AT cygwin DOT com>
Subject:	Perl ldflags - packaging bug, upstream bug, or weird feature?
Date:	Mon, 3 Oct 2005 18:03:02 +0100
MIME-Version:	1.0
X-IsSubscribed:	yes

$ fgrep -- '-L/usr/local/lib' /usr/lib/perl5/5.8/cygwin/Config_heavy.pl
lddlflags=' -s -L/usr/local/lib'
ldflags=' -s -L/usr/local/lib'
ldflags_nolargefiles=' -s -L/usr/local/lib'


The above shows the presence of -L/usr/local/lib in the packaged perl 
installation config vars.
This is a problem, because when compiling Perl extensions, it places 
/usr/local/lib at the front of the library search path, taking precedence 
over any other paths that the Makefile.PL may take care to specify. This is 
bad, because /usr/local/lib may contain old/incorrect versions of libraries 
which get found instead of the libraries the Makefile.PL attempted to point 
to with explicit -L options.

I don't know enough about the perl build process to know where that option 
is coming from - I'm hoping someone can tell me whether the presence of 
those harmful -L/usr/local/lib options is a packaging bug, an upstream bug, 
or a weird feature.

Max.


--
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/

- Raw text -