Hallo Michael,
Am Samstag, 3. April 2004 um 22:44 schriebst du:
> On Sat, Mar 27, 2004 at 10:25:24PM +0100, Gerrit P. Haase wrote:
>> LIB is picked up by MakeMaker if it is available in the environment, it causes
>> failures everytime when LIB contains spaces as it is usually the case in a
>> default Visual Studio setup.
>>
>> This is a problem on Cygwin.
>>
>> Just unset LIB in your Cygwin startup batch or redefine it to s.th. useful in
>> your .bashrc
>>
>> This should be fixed in MakeMaker.
> What would the fix be? There's this code in ExtUtils::Liblist::Kid which is,
> I presume, the problem:
> if ($VC and exists $ENV{LIB} and $ENV{LIB}) {
> push @libpath, split /;/, $ENV{LIB};
> }
> which seems to pretty explicitly want to pull LIB from the environment when
> using Visual C. Can something be done to handle the spaces?
> Also, since the code is only tripped when $Config{cc} =~ /^cl/i (I presume
> this is Visual C/Studio), how is it true in Cygwin?
Since we use GCC on Cuygwin and not VC, I wonder why this part might
be the culprit, anyway, excluding the rule when OS is cygwin should be
enough.
Ciao,
Gerrit P. Haase
--
=^..^=
