Front page | perl.perl5.porters |
Postings from May 2003
On Mon, May 19, 2003 at 11:35:02PM -0700, Michael G Schwern wrote:
> Writing Makefile.aperl for Pie
> make -f Makefile.aperl perl
> Writing perlmain.c
> cd . && cc -c "-I/usr/local/perl5.8.0/lib/darwin-64all/CORE" \
> -pipe -fno-common -no-cpp-precomp -DDEBUGGING -fno-strict-aliasing -O3 -g \
> -DVERSION=\"0.01\" \
> -DXS_VERSION=\"0.01\" "-I/usr/local/perl5.8.0/lib/darwin-64all/CORE" perlmain.c
> make[1]: *** No rule to make target `/usr/local/perl5.8.0/lib/darwin-64all/CORE/libperl.a', needed by `perl'. Stop.
> make: *** [perl] Error 2
>
> MakeMaker is looking for libperl.a but I have libperl.dylib. MakeMaker
> is using $Config{lib_ext} which is .a here. $Config{so} is .dylib.
> Which is wrong? Config or MakeMaker?
Similar problem on Linux with a Debian built Perl. Do I have to do
something special when Perl is built to have Makefile.aperl work?
Writing "Makefile.aperl" for this perl
Warning: /usr/lib/perl/5.6.1/CORE/libperl.a not found
If you're going to build a static perl binary, make sure perl is installed
otherwise ignore this warning
Writing Makefile.aperl for Pie
make -f Makefile.aperl perl
make[1]: Entering directory `/home/schwern/tmp/Pie-0.01'
Writing perlmain.c
cd . && cc -c -I/usr/lib/perl/5.6.1/CORE -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 \
-DVERSION=\"0.01\" \
-DXS_VERSION=\"0.01\" -fPIC -I/usr/lib/perl/5.6.1/CORE perlmain.c
make[1]: *** No rule to make target `/usr/lib/perl/5.6.1/CORE/libperl.a', needed by `perl'. Stop.
make[1]: Leaving directory `/home/schwern/tmp/Pie-0.01'
make: *** [perl] Error 2
--
Thread Previous
|
Thread Next