Have you looked at the README.solaris file (I assume 5.14 has one just like 5.10.1 did)? And I assume you are using /usr/sfw/bin/gcc?

Using tcsh, this is the environment I setup before building Perl 5.10.1 a couple years ago. Maybe it will help you. For bash, use export VAR="VALUE" instead.

setenv PATH /usr/sbin:/sbin:/usr/bin:/usr/sfw/bin:/usr/sfw/libexec:/us +r/ccs/bin:. setenv LD_LIBRARY_PATH /usr/lib:/usr/sfw/lib:/usr/local/ssl/lib setenv LD_LIBRARY_PATH_64 /usr/lib/sparcv9:/usr/sfw/lib/sparcv9 setenv MANPATH /usr/share/man:/usr/sfw/man unalias *
And below is my myconfig file (again, from Perl 5.10.1). I would suggest you compare your 5.12 and my 5.10.1 stuff with your 5.14 stuff to see what's different.
#!/bin/sh # This script is designed to provide a handy summary of the configurat +ion # information being used to build perl. This is especially useful if y +ou # are requesting help from comp.lang.perl.misc on usenet or via mail. # Note that the text lines /^Summary of/ .. /^\s*$/ are copied into Co +nfig.pm. cat <<'!NO!SUBS!' Summary of my perl5 (revision 5 version 10 subversion 1) configuration +: Platform: osname=solaris, osvers=2.10, archname=sun4-solaris-thread-multi uname='sunos searay 5.10 generic_137111-06 sun4u sparc sunw,sun-fi +re-880 ' config_args='' hint=recommended, useposix=true, d_sigaction=define useithreads=define, usemultiplicity=define useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=und +ef use64bitint=undef, use64bitall=undef, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr +/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_ +SAFE_PUTENV', optimize='-O', cppflags='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/inc +lude' ccversion='', gccversion='3.4.3 (csl-sol210-3_4-branch+sol_rpath)' +, gccosandvers='solaris2.10' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=1 +6 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', + lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='gcc', ldflags ='-L/usr/lib/sparcv9 -L/usr/sfw/lib/sparcv9 -L/u +sr/lib -L/usr/sfw/lib -L/usr/local/ssl/lib ' libpth=/usr/lib/sparcv9 /usr/sfw/lib/sparcv9 /usr/lib /usr/sfw/lib + /usr/local/ssl/lib libs=-lsocket -lnsl -lgdbm -ldl -lm -lpthread -lc perllibs=-lsocket -lnsl -ldl -lm -lpthread -lc libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-fPIC', lddlflags='-G -L/usr/lib/sparcv9 -L/usr/sfw/li +b/sparcv9 -L/usr/lib -L/usr/sfw/lib -L/usr/local/ssl/lib' !NO!SUBS!

Elda Taluta; Sarks Sark; Ark Arks
My deviantART gallery


In reply to Re: threads.xs compile error by Argel
in thread threads.xs compile error by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.