Ihor Bilyy wrote:
>
> After applying that patches error message is the same.
> ld -V:
> ld: Software Generation Utilities - Solaris Link Editors: 5.8-1.275
This is OK. The Configure script for perl looks for "ld: Software Generation
Utilities", so it should find it.
> btw gcc --version 2.95.2, maybe problem is with gcc ?
I use 2.95.3, from the package at sunfreeware.com.
What does perl -V show? It should show you a bunch of info, with a section that
looks something like this:
Linker and Libraries:
ld='gcc', ldflags ='-R/opt/BerkeleyDB/lib:/opt/lib -L/opt/BerkeleyDB/lib '
libpth=/opt/BerkeleyDB/lib /usr/lib /usr/ccs/lib /usr/local/lib
libs=-lsocket -lnsl -lgdbm -ldb -ldl -lm -lc
perllibs=-lsocket -lnsl -ldl -lm -lc
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
Anything you try to build to add to your perl which has C code (like mod_perl)
will try to use the same compiler and linker options that were used to build
perl. So if you used the Gnu ld, (which you would see in the ldflags of the
Linker section above), then mod_perl will try to build with that linker.
(FYI, the ldflags that I use above are so I do not ever have to set
LD_LIBRARY_PATH in the environment)
Did you build perl on the same box, with the same compiler?? If it was built
somewhere else, and transfered over, you will have to either rebuild perl from
source, or build mod_perl with the original perl, and then transfer it over,
made much easier if you use a prefix to build and install perl into one dir. I
do this with a prefix of /opt/perl5. Then I can just xfer that whole sub-dir
(using rsync and ssh) to any other box with the same OS version.
--
David McCabe Network and Communications Services, McGill University
Montreal, Quebec, Canada [EMAIL PROTECTED]
In theory there is no difference between theory and practice.
In practice there is. -Yogi Berra
