cvs commit: modperl/apaci mod_perl.config.sh

[kh...@hyperreal.org]

khera       99/04/07 12:13:23

  Modified:    apaci    mod_perl.config.sh
  Log:
  On BSD/OS 4.x, we cannot pass the ldopts from ExtUtils::Embed to ld,
  which is how these flags are used.  The ldopts here assume they are
  being passed to cc, so what we do is just remove the ccdlflags from
  this string, and are left with the necessary libraries we need for
  linking our libperl.so object.
  
  I suspect this is true for other platforms (you generally don't want
  to pass cc options to ld), but since nobody else seems to have these
  problems, I'm making this a bsd/os specific patch.
  
  Revision  Changes    Path
  1.13      +4 -0      modperl/apaci/mod_perl.config.sh
  
  Index: mod_perl.config.sh
  ===================================================================
  RCS file: /home/cvs/modperl/apaci/mod_perl.config.sh,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- mod_perl.config.sh	1998/11/30 23:14:58	1.12
  +++ mod_perl.config.sh	1999/04/07 19:13:16	1.13
  @@ -116,6 +116,10 @@
   cat >$tmpfile2 <<'EOT'
   use Config;
   my $ldopts = `$^X -MExtUtils::Embed -e ldopts -- -std @ARGV`;
  +# can't pass ccdlflags to ld, which is what happens in this context.  however
  +# we still need the libraries themselves.  I think this should be correct for
  +# other systems, but it bites us on BSD/OS 4.x
  +$ldopts =~ s@$Config{ccdlflags}@@ if ($^O eq 'bsdos');
   $ldopts =~ s,(-bE:)(perl\.exp),$1$Config{archlibexp}/CORE/$2, if($^O eq "aix");
   =pod
   #replace -Wl args meant for gcc with args for ld