Front page | perl.perl5.porters |
Postings from October 2000
On Mon, 09 Oct 2000 17:18:40 CDT, Jarkko Hietaniemi wrote:
>It was pointed out to me that we have a nasty problem now that vendors
>are shipping Perl with their OSes. This Perl is most naturally
>compiled with the vendor's compiler kit. Now, if the compiler kit is
>'unbundled' building any additional modules or trying to update
>existing ones will fail spectacularly because one or more of the
>compiler/linker name, compiler/linker flags will mismatch. In some
>cases it could be possible and even feasible to try to probe for
>alternative compilers, such as gcc. (*)
Messing around in Config.pm is the only viable approach I've found for
this. The problem with doing that: you lose information about how Perl
was built, since there's only one $Config{cc}. Ideally there'd be some
way to keep the old one around. ($Config{cc_when_built},
$Config{cc_current} and so on.)
The "messing around in Config.pm" part is also non-trivial, since it
needs parts of the Configure logic to do it right.
Sarathy
gsar@ActiveState.com
Thread Previous
|
Thread Next