Ken Williams wrote:
On Saturday, October 11, 2003, at 11:15 AM, Randy W. Sims wrote:
$self->do_system(@shrp, @ld, @lddlflags, '-o', $lib_file,
"$file_base$cf->{obj_ext}", @$objects,
'-L'.File::Spec->catdir($cf->{archlibexp}, 'CORE'),
'-lperl', @linker_flags)
Hi Randy,
It looks like the -L/foo/perl/CORE and -lperl arguments are the only
differences here, right?
Correct. I just copied and pasted the whole function, makeing only the
changes you pointed out. But this may be a simplification (hack) of what
needs to be done that just works for the most common case. MakeMaker
allows for the case of a statically linked perl under cygwin; I don't
know if anyone actually uses that option. I guess I should probably put
it in as it's a very minor change to allow for both static and dynamic
builds.
I'm curious about something - on my system
(darwin), $Config{shrpenv} is defined as 'env
LD_RUN_PATH=/sw/lib/perl5/5.6.1/darwin/CORE', and that ends up in the
@shrp variable.
On your cygwin, is $Config{shrpenv} empty, or not having any effect, or
what?
It's the same as yours, but for some reason it is not being used. Like I
said earlier, I'm a little uncertain of the differences in the build
process under Cygwin as compared to either Windows or *nix. I intend to
investigate further--maybe I can learn something on the Cygwin mailing
list...
I think in general this is a case of Config.pm being a micro-manager.
It's not describing what it wants done, it's describing how to do it.
That's making our job of interface-writing sort of hard to do.
-Ken
Randy.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
|
