Tom, After 3 days of banging my head against brick walls I have found the solution! I am SO pleased. The problem was the result of inadvertently trying to mix and match gcc and HP tools. I had read about this being a problem and had ensured that I compiled gcc myself then used that to compile perl, make etc. What I had not realised - as it had not been a problem with and of the other 100+ perl modules I've loaded - is that the Makefile.PL files were using the following settings: FULL_AR = /usr/bin/ar LD = /usr/bin/ld LDDLFLAGS = -b These are the HP tools obviously. Whilst they appear to work happily in most instances, certain perl modules won't compile/link with HP tools when using gcc-compiled perl etc. I changed the Makefile.PL of DBD-SQLite-1.14 and Crypt-SSLeay-0.57 (the 2 difficult ones so far) to point to the gcc-compiled tools: FULL_AR = /opt/product/ticm/build_tools/hp/binutil/binutil-2.18/bin/ar LD = /opt/product/ticm/build_tools/hp/gcc/gcc-3.4.6/bin/gcc LDDLFLAGS = -shared Both modules installed with 100% successful tests first time. Thanks for taking the trouble to make some suggestions Tom. I am one happy admin. regards Tony > ---------------------------------------- > From: Tom Browder <tom.browder@xxxxxxxxx> > Sent: Thu May 15 15:39:57 CEST 2008 > To: Anthony Kent <tonykent@xxxxxxxxxxx> > Subject: Re: Unresolved symbol problem > > > On 5/15/08, Anthony Kent <tonykent@xxxxxxxxxxx> wrote: > > I have just tried the CPAN shell and unfortunately got exactly the same failure messages on the make test phase: > ... > > I suspect that the gcc library is not being found/declared properly, but I'm not sure how to prove this. > > Try setting an environment variable to the desired gcc: > > export CC='<path-to-gcc>' > > And make sure LD_LIBRARY_PATH has the path to your locally-installed libs. > > Then remake the module's Makefile.PL and retry the build. > > -Tom > > P.S. Are you locked into that old gcc version? > > P.P.S. As administrator, you sure have some ugly paths on that > host--that may be the source of some of the problems (later if not > now) if there are years of old cruft hangin around--especially the way > some Perl packages are cavalier about where modules are installed and > how Perl's @INC is configured. ----------------------------------------------------- Le bureau virtuel http://www.lamessagerie.com
