13 # necessary to establish linker dependencies between the various .so files.
  14 #
  15 # This causes several problems.  The first of these is that perl .so files are
  16 # built in one directory (under ../blib in this case) and installed into
  17 # another, so it is necessary to record the dependency using a path relative to
  18 # the dependent. This can be done with the $ORIGIN linker mechanism.
  19 
  20 # The second problem is that it is necessary to specify the name of the
  21 # dependee at link edit time in a manner that doesn't result in the build-time
  22 # path of the dependee being hard coded in to the dependent, as this would
  23 # stop ld.so.1 performing its normal search process for the files.  This can't
  24 # be done with the normal '--L/my/lib/path -lmylib' mechanism, because the XSUB
  25 # .so files aren't prefixed with 'lib'.  To do this the -h linker flag is used
  26 # to explicitly set the SONAME in the dependee.  This is then used as the name
  27 # of the dependent in the dependee rather than the full path by which it was
  28 # found at link edit time.
  29 #
  30 # For more details, refer to the Linker and Libraries Guide.
  31 #
  32 
  33 require 5.8.4;
  34 use strict;
  35 use warnings;
  36 use ExtUtils::MakeMaker;
  37 
  38 our (@defines, @man3pods);
  39 
  40 #
  41 # MakeMaker overrides.
  42 #
  43 package MY;
  44 no warnings qw(once);
  45 
  46 #
  47 # Overrides that are common to both the ON and non-ON build environments.
  48 #
  49 
  50 #
  51 # Force the parent directory to be built first, because the sub-modules all
  52 # have a linker dependency against Exacct.so.
  53 #

  13 # necessary to establish linker dependencies between the various .so files.
  14 #
  15 # This causes several problems.  The first of these is that perl .so files are
  16 # built in one directory (under ../blib in this case) and installed into
  17 # another, so it is necessary to record the dependency using a path relative to
  18 # the dependent. This can be done with the $ORIGIN linker mechanism.
  19 
  20 # The second problem is that it is necessary to specify the name of the
  21 # dependee at link edit time in a manner that doesn't result in the build-time
  22 # path of the dependee being hard coded in to the dependent, as this would
  23 # stop ld.so.1 performing its normal search process for the files.  This can't
  24 # be done with the normal '--L/my/lib/path -lmylib' mechanism, because the XSUB
  25 # .so files aren't prefixed with 'lib'.  To do this the -h linker flag is used
  26 # to explicitly set the SONAME in the dependee.  This is then used as the name
  27 # of the dependent in the dependee rather than the full path by which it was
  28 # found at link edit time.
  29 #
  30 # For more details, refer to the Linker and Libraries Guide.
  31 #
  32 
  33 require 5.0010;
  34 use strict;
  35 use warnings;
  36 use ExtUtils::MakeMaker;
  37 
  38 our (@defines, @man3pods);
  39 
  40 #
  41 # MakeMaker overrides.
  42 #
  43 package MY;
  44 no warnings qw(once);
  45 
  46 #
  47 # Overrides that are common to both the ON and non-ON build environments.
  48 #
  49 
  50 #
  51 # Force the parent directory to be built first, because the sub-modules all
  52 # have a linker dependency against Exacct.so.
  53 #