Re: make test FAILED--23 test scripts
Robin... (robin02@mygale.org)
Thu, 16 Jul 1998 12:59:06 +0200
Gisle wrote:
>> Can anyone explain why the choice of directories mattered in this case?
>
>Just a wild guess: Perhaps because libwww-perl did not contain any XS
>code?
I'm not quite sure if this is the cause but one of my neurons
triggered and brought back a memory of MakeMaker's documentation which
includes the following:
Determination of Perl Library and Installation Locations
MakeMaker needs to know, or to guess, where certain things are located.
Especially INST_LIB and INST_ARCHLIB (where to put the files during the
make(1) run), PERL_LIB and PERL_ARCHLIB (where to read existing modules
from), and PERL_INC (header files and libperl*.*).
Extensions may be built either using the contents of the perl source
directory tree or from the installed perl library. The recommended way is to
build extensions after you have run 'make install' on perl itself. You can
do that in any directory on your hard disk that is not below the perl source
tree. The support for extensions below the ext directory of the perl
distribution is only good for the standard extensions that come with perl.
If an extension is being built below the ext/ directory of the perl source
then MakeMaker will set PERL_SRC automatically (e.g., ../..). If PERL_SRC is
defined and the extension is recognized as a standard extension, then other
variables default to the following:
PERL_INC = PERL_SRC
PERL_LIB = PERL_SRC/lib
PERL_ARCHLIB = PERL_SRC/lib
INST_LIB = PERL_LIB
INST_ARCHLIB = PERL_ARCHLIB
If an extension is being built away from the perl source then MakeMaker will
leave PERL_SRC undefined and default to using the installed copy of the perl
library. The other variables default to the following:
PERL_INC = $archlibexp/CORE
PERL_LIB = $privlibexp
PERL_ARCHLIB = $archlibexp
INST_LIB = ./blib/lib
INST_ARCHLIB = ./blib/arch
This seems to explain why you can build under any directory *except*
ext/.
Have a nice day all of you,
Robin