On Mon, Aug 6, 2012 at 9:50 AM, Don Walters <[email protected]> wrote:
> Oops: Makefile.PL output was truncated. Here's the full output: > > srvdfj239 /DBI-1.622 # perl Makefile.PL > > *** You are using a perl configured with threading enabled. > *** You should be aware that using multiple threads is > *** not recommended for production environments. > > Creating test wrappers for DBD::Gofer: > t/zvg_01basics.t > t/zvg_02dbidrv.t > [...] > Creating test wrappers for DBD::Gofer + DBI::SQL::Nano + DBI::PurePerl: > t/zvxgnp_48dbi_dbd_sqlengine.t > t/zvxgnp_49dbd_file.t > t/zvxgnp_50dbm_simple.t > t/zvxgnp_51dbm_file.t > t/zvxgnp_52dbm_complex.t > t/zvxgnp_85gofer.t > > I see you're using perl 5.008008 on aix-thread-multi-64all, okay. > Remember to actually *read* the README file! > Use 'make' to build the software (dmake or nmake on Windows). > Then 'make test' to execute self tests. > Then 'make install' to install the DBI and then delete this working > directory before unpacking and building any DBD::* drivers. > > Writing Makefile for DBI > Writing MYMETA.yml and MYMETA.json > srvdfj239 /DBI-1.622 # > I had to go digging in amongst deleted messages to find this message which I sent you (and not the mailing list) on Friday: On Fri, Aug 3, 2012 at 8:34 AM, Don Walters <[email protected]> wrote: > >> [...] >> >> -Dprefix=/usr/opt/perl5 -Dcc=xlc_r -Duseshrplib -Dusethreads' >> hint=recommended, useposix=true, d_sigaction=define >> usethreads=define use5005threads=undef useithreads=define >> usemultiplicity=define >> useperlio=define d_sfio=undef uselargefiles=define usesocks=undef >> use64bitint=define use64bitall=define uselongdouble=undef >> usemymalloc=n, bincompat5005=undef >> Compiler: >> cc='cc_r', ccflags ='-D_ALL_SOURCE -D_ANSI_C_SOURCE >> -D_POSIX_SOURCE -qmaxmem=-1 -qnoansialias -DUSE_NATIVE_DLOPEN >> -DNEED_PTHREAD_INIT -q64 -DUSE_64_BIT_ALL -q64', >> [...] >> >> Compilers is not really my thing. Currently I'm using >> /usr/ccs/lib/cpp. Is that not the same thing? >> > > > /usr/ccs/lib/cpp is the C pre-processor, not the C compiler. DBI.o will > not be created by running cpp on a .c file. > > As already indicated, you will need to install xlc (notice that the names > used in the configuration are 'cc_r' and 'xlc_r'). Or, as an alternative > but somewhat long winded process, install GCC and build your own Perl using > that (and then install DBI). > The output from 'perl Makefile.PL' looks fine. We now need to see how you invoke the build (it should be just 'make'), and the output from the build. The part of most interest is the compilation of DBI.o. If you're still using /usr/ccs/lib/cpp, you still have a problem. Assuming you're not doing that, we need to see how DBI.o is being compiled (so we can perhaps guess why the compilation is failing to produce DBI.o). And for those, like me, who don't necessarily keep every message, the original problem was reported as: I'm running Perl in 64bit on AIX5.3. [...] > > Here is the last part of the output before it fails: > Running Mkbootstrap for DBI () > chmod 644 DBI.bs > rm -f blib/arch/auto/DBI/DBI.so > ld -b64 -bhalt:4 -bexpall -G -bnoentry -lpthreads -lc DBI.o > -o blib/arch/auto/DBI/DBI.so > ld: 0706-005 Cannot find or open file: DBI.o > ld:open(): A file or directory in the path name does not exist. > make: 1254-004 The error code from the last command is 255. > > Stop. > /usr/bin/make -- NOT OK > Running make test > Can't test without successful make > Running make install > make had returned bad status, install seems impossible > -- Jonathan Leffler <[email protected]> #include <disclaimer.h> Guardian of DBD::Informix - v2011.0612 - http://dbi.perl.org "Blessed are we who can laugh at ourselves, for we shall never cease to be amused."
