search

Perl / perl5

🐪 The Perl programming language
https://dev.perl.org/perl5/
Other
1.96k stars 555 forks source link

Not OK: perl v5.7.0 +SUIDMAIL +DEVEL6866 on sun4-solaris-64int 2.8 (UNINSTALLED) #2482

Closed p5pRT closed 20 years ago

p5pRT commented 24 years ago

Migrated from rt.perl.org#3931 (status was 'resolved')

Searchable as RT3931$

p5pRT commented 24 years ago

From @AlanBurlison

This is a build failure report for perl from Alan.Burlison@​uk.sun.com\, generated with the help of perlbug 1.32 running under perl v5.7.0.

Perl built with -Dusemorebits

Configure errors​:

Try to use long doubles if available? [y]

I do not see the Sun Workshop compiler; therefore I do not see the libsunmath; therefore I do not know how to do long doubles\, sorry. I'm disabling the use of long doubles.

$ cc -V cc​: Sun WorkShop 6 2000/06/19 C 5.1 Patch 109491-02 usage​: cc [ options] files. Use 'cc -flags' for details

'make test' errors​:

lib/ftmp-security....Directory owned neither by root nor the current user at lib/ftmp-security.t line 105 File​::Temp​::_gettemp​: Parent directory (.) is not safe (sticky bit not set when world writable?) at lib/ftmp-security.t line 105 Error in tempfile() using temptestXXXXXXXX at lib/ftmp-security.t line 105 FAILED at test 7

Flags​:   category=install   severity=none

Site configuration information for perl v5.7.0​:

Configured by alanbur at Tue Aug 29 12​:03​:57 BST 2000.

Summary of my perl5 (revision 5.0 version 7 subversion 0) configuration​:   Platform​:   osname=solaris\, osvers=2.8\, archname=sun4-solaris-64int   uname='sunos mower 5.8 generic_108528-02 sun4u sparc sunw\,ultra-60 '   config_args='-dsOE -Dprefix=/home1/software/perl/bldtest -Dinstallprefix=/home1/software/perl/bldtest -Dsiteprefix=/home1/software/perl/bldtest -Doptimize=-g -Duseshrplib -Uusemymalloc -Dusedevel -Ubincompat5005 -Dusemorebits -Accflags=-DDL_UNLOAD_ALL_AT_EXIT'   hint=recommended\, useposix=true\, d_sigaction=define   usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef   useperlio=undef d_sfio=undef uselargefiles=define   use64bitint=define use64bitall=undef uselongdouble=undef usesocks=undef   Compiler​:   cc='cc'\, optimize='-g'\, gccversion=\, gccosandvers=   cppflags='-DDL_UNLOAD_ALL_AT_EXIT -DDEBUGGING -I/usr/local/include'   ccflags ='-DDL_UNLOAD_ALL_AT_EXIT -DDEBUGGING -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'   stdchar='char'\, d_stdstdio=define\, usevfork=false   intsize=4\, longsize=4\, ptrsize=4\, doublesize=8\, byteorder=87654321   d_longlong=define\, longlongsize=8\, d_longdbl=define\, longdblsize=16   ivtype='long long'\, ivsize=8\, nvtype='double'\, nvsize=8\, Off_t='off_t'\, lseeksize=8   alignbytes=8\, usemymalloc=n\, prototype=define   Linker and Libraries​:   ld='cc'\, ldflags =' -L/usr/local/lib -L/opt/SUNWspro/WS6/lib '   libpth=/usr/local/lib /opt/SUNWspro/WS6/lib /lib /usr/lib /usr/ccs/lib   libs=-lsocket -lnsl -ldl -lm -lc -lcrypt -lsec   libc=/lib/libc.so\, so=so\, useshrplib=true\, libperl=libperl.so   Dynamic Linking​:   dlsrc=dl_dlopen.xs\, dlext=so\, d_dlsymun=undef\, ccdlflags=' -R /home1/software/perl/bldtest/lib/5.7.0/sun4-solaris-64int/CORE'   cccdlflags='-KPIC'\, lddlflags='-G -L/usr/local/lib -L/opt/SUNWspro/WS6/lib'

Locally applied patches​:   SUIDMAIL - fixes for suidperl security   DEVEL6866

@​INC for perl v5.7.0​:   /home1/software/perl/build/perl/lib   /home1/software/perl/bldtest/lib/5.7.0/sun4-solaris-64int   /home1/software/perl/bldtest/lib/5.7.0   /home1/software/perl/bldtest/lib/site_perl/5.7.0/sun4-solaris-64int   /home1/software/perl/bldtest/lib/site_perl/5.7.0   /home1/software/perl/bldtest/lib/site_perl   .

Environment for perl v5.7.0​:   HOME=/homedir/rootal   LANG (unset)   LANGUAGE (unset)   LD_LIBRARY_PATH=/home1/software/perl/build/perl   LOGDIR (unset)   PATH=/homedir/rootal/bin​:/usr/local/bin​:/bin​:/usr/bin​:/usr/sbin​:/opt/SUNWspro/bin​:/usr/ccs/bin​:/opt/gcc/bin​:/usr/ucb​:/usr/dt/bin​:/usr/openwin/bin​:/opt/SUNWisdn/bin​:/opt/SUNWisdn/tools​:.   PERL_BADLANG (unset)   SHELL=/bin/ksh

p5pRT commented 24 years ago

From @jhi

On Tue\, Aug 29\, 2000 at 12​:34​:22PM +0100\, Alan Burlison wrote​:

This is a build failure report for perl from Alan.Burlison@​uk.sun.com\, generated with the help of perlbug 1.32 running under perl v5.7.0.

Perl built with -Dusemorebits

Configure errors​:

Try to use long doubles if available? [y]

I do not see the Sun Workshop compiler; therefore I do not see the libsunmath; therefore I do not know how to do long doubles\, sorry. I'm disabling the use of long doubles.

$ cc -V cc​: Sun WorkShop 6 2000/06/19 C 5.1 Patch 109491-02 usage​: cc [ options] files. Use 'cc -flags' for details

You could try putting set -x or something similar to hints/solaris_2.sh to find out why the WorkShop is not being detected.

p5pRT commented 24 years ago

From @AlanBurlison

Jarkko Hietaniemi wrote​:

Perl built with -Dusemorebits

Configure errors​:

Try to use long doubles if available? [y]

I do not see the Sun Workshop compiler; therefore I do not see the libsunmath; therefore I do not know how to do long doubles\, sorry. I'm disabling the use of long doubles.

$ cc -V cc​: Sun WorkShop 6 2000/06/19 C 5.1 Patch 109491-02 usage​: cc [ options] files. Use 'cc -flags' for details

You could try putting set -x or something similar to hints/solaris_2.sh to find out why the WorkShop is not being detected.

I've instrumented hints/solaris\, and just after the test for the workshop compilers on line 48\, $ccisworkshop is set ok\, but by the time uselongdouble.cbu is called it has been unset. I suspect the cause is the following at about line 510​:

# keep that leading tab   ccisworkshop=''   ccisgcc=''

If I comment out those 2 lines I get the following different error​:

Try to use long doubles if available? [y]

*** You requested the use of long doubles but you do not seem to have *** the mathematic functions for long doubles. I'm disabling the use *** of long doubles.

This seems to be caused by Configure trying to check for sqrtl - It appears to be checking for it in libc thusly​:

: see if sqrtl exists set sqrtl d_sqrtl eval $inlibc

And of course it isn't there\, it is in libsunmath.

p5pRT commented 24 years ago

From @jhi

On Wed\, Aug 30\, 2000 at 01​:07​:56AM +0100\, Alan Burlison wrote​:

Jarkko Hietaniemi wrote​:

Perl built with -Dusemorebits

Configure errors​:

Try to use long doubles if available? [y]

I do not see the Sun Workshop compiler; therefore I do not see the libsunmath; therefore I do not know how to do long doubles\, sorry. I'm disabling the use of long doubles.

$ cc -V cc​: Sun WorkShop 6 2000/06/19 C 5.1 Patch 109491-02 usage​: cc [ options] files. Use 'cc -flags' for details

You could try putting set -x or something similar to hints/solaris_2.sh to find out why the WorkShop is not being detected.

I've instrumented hints/solaris\, and just after the test for the workshop compilers on line 48\, $ccisworkshop is set ok\, but by the time uselongdouble.cbu is called it has been unset. I suspect the cause is the following at about line 510​:

# keep that leading tab ccisworkshop=''

Very good guess\, that's what's clearing it.

I guess it's time to introduce some additional variable which will contain things like 'cc' (meaning a vendor cc) or 'gcc'\, or 'workshop'\, etc\, since many platforms may have many different C compilers and just continuing to pretend that it's either cc or gcc simply doesn't work anymore. In this new variable we can nicely store the 'workshop'.

Try to use long doubles if available? [y]

*** You requested the use of long doubles but you do not seem to have *** the mathematic functions for long doubles. I'm disabling the use *** of long doubles.

This seems to be caused by Configure trying to check for sqrtl - It appears to be checking for it in libc thusly​:

: see if sqrtl exists set sqrtl d_sqrtl eval $inlibc

And of course it isn't there\, it is in libsunmath.

$inlibc is confusingly named\, it doesn't check libc... what matters in there is $libs. Isn't -lsunmath in libs?

p5pRT commented 24 years ago

From @timj

On Tue\, 29 Aug 2000\, Jarkko Hietaniemi wrote​:

On Wed\, Aug 30\, 2000 at 01​:07​:56AM +0100\, Alan Burlison wrote​:

I've instrumented hints/solaris\, and just after the test for the workshop compilers on line 48\, $ccisworkshop is set ok\, but by the time uselongdouble.cbu is called it has been unset. I suspect the cause is the following at about line 510​:

# keep that leading tab ccisworkshop=''

Very good guess\, that's what's clearing it.

I guess it's time to introduce some additional variable which will contain things like 'cc' (meaning a vendor cc) or 'gcc'\, or 'workshop'\, etc\, since many platforms may have many different C compilers and just continuing to pretend that it's either cc or gcc simply doesn't work anymore. In this new variable we can nicely store the 'workshop'.

If possible I would also like to see a ccversion for none gcc compilers. On Sun using SC4.0 rather than SC6 can make a difference and is just as relevant a number as gccversion. I assume the reason gccversion is in is because it is easy to know how to get the information. For vendor compilers the incantation for the compiler version would have to be in the hints file for the os presumably.

p5pRT commented 24 years ago

From @jhi

I guess it's time to introduce some additional variable which will contain things like 'cc' (meaning a vendor cc) or 'gcc'\, or 'workshop'\, etc\, since many platforms may have many different C compilers and just continuing to pretend that it's either cc or gcc simply doesn't work anymore. In this new variable we can nicely store the 'workshop'.

There now is 'ccname'.

If possible I would also like to see a ccversion for none gcc compilers. On Sun using SC4.0 rather than SC6 can make a difference and is just as relevant a number as gccversion. I assume the reason gccversion is in is because it is easy to know how to get the information. For vendor compilers the incantation for the compiler version would have to be in the hints file for the os presumably.

Yes.

Patches welcome.

p5pRT commented 24 years ago

From @tux

On Wed\, 30 Aug 2000 11​:50​:59 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

I guess it's time to introduce some additional variable which will contain things like 'cc' (meaning a vendor cc) or 'gcc'\, or 'workshop'\, etc\, since many platforms may have many different C compilers and just continuing to pretend that it's either cc or gcc simply doesn't work anymore. In this new variable we can nicely store the 'workshop'.

There now is 'ccname'.

If possible I would also like to see a ccversion for none gcc compilers. On Sun using SC4.0 rather than SC6 can make a difference and is just as relevant a number as gccversion. I assume the reason gccversion is in is because it is easy to know how to get the information. For vendor compilers the incantation for the compiler version would have to be in the hints file for the os presumably.

Yes.

Patches welcome.

I can remember I sent a request for a change like this about half a year ago\, but I did not safe it. Can it be found in the p5p archive somewhere?

It described the ways to get vendor's C compiler version numbers for HP-UX\, AIX and DEC-OSF for all versions available at that time.

p5pRT commented 24 years ago

From @AlanBurlison

"H.Merijn Brand" wrote​:

I can remember I sent a request for a change like this about half a year ago\, but I did not safe it. Can it be found in the p5p archive somewhere?

It described the ways to get vendor's C compiler version numbers for HP-UX\, AIX and DEC-OSF for all versions available at that time.

For Workshop/Forte on Solaris it is this​:

$ cc -V cc​: Sun WorkShop 6 2000/06/19 C 5.1 Patch 109491-02 usage​: cc [ options] files. Use 'cc -flags' for details

p5pRT commented 24 years ago

From @timj

"H.Merijn Brand" wrote​:

I can remember I sent a request for a change like this about half a year ago\, but I did not safe it. Can it be found in the p5p archive somewhere?

http​://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-03/msg02664.html

p5pRT commented 24 years ago

From @tux

On Thu\, 31 Aug 2000 00​:15​:24 -1000 (HST)\, Tim Jenness \timj@​jach\.hawaii\.edu wrote​:

"H.Merijn Brand" wrote​:

I can remember I sent a request for a change like this about half a year ago\, but I did not safe it. Can it be found in the p5p archive somewhere?

http​://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-03/msg02664.html

Thanks\, now saved for future re-sent/re-edit for up-to-date info's in the future.

p5pRT commented 24 years ago

From @tux

On Thu\, 31 Aug 2000 00​:15​:24 -1000 (HST)\, Tim Jenness \timj@​jach\.hawaii\.edu wrote​:

"H.Merijn Brand" wrote​:

I can remember I sent a request for a change like this about half a year ago\, but I did not safe it. Can it be found in the p5p archive somewhere?

http​://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-03/msg02664.html

Updated here to latest output.

Shouldn't 'make ok' and 'make nok' also try to find out the version of the C compiler used if it's not gcc.

HP-UX​: swlist -l bundle | grep B3901BA

  11.00​: B3901BA B.11.01.20 HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800)   10.20​: B3901BA B.10.20.15 HP C/ANSI C Developer's Bundle for HP-UX 10.20 (S800)  
AIX​: lslpp -L | grep 'C for AIX'

  4.3.2​: vac.C 4.4.0.3 C C for AIX Compiler   4.2.1​: xlC.C 3.1.4.0 C C for AIX Compiler  
OSF/1​: setld -i | grep ^OSFCMPLRS; cc -V | head -3

  OSFCMPLRS425 installed Compiler Back End (Software Development)   cc (cc)   Digital UNIX Compiler Driver 3.11   DEC C V5.6-084 on Digital UNIX V4.0 (Rev. 878)

p5pRT commented 24 years ago

From @jhi

Shouldn't 'make ok' and 'make nok' also try to find out the version of the C compiler used if it's not gcc.

Yes. But not for 5.7.0. For example\, in the below you've got several compilers installed for for HP-UX and AIX. We need only one\, the one used to compile Perl. For OSF/1\, we really would like to have all the information in one line. Et cetera. Nice\, I want it\, but not now.

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 09​:22​:30 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

Shouldn't 'make ok' and 'make nok' also try to find out the version of the C compiler used if it's not gcc.

Yes. But not for 5.7.0. For example\, in the below you've got several compilers installed for for HP-UX and AIX. We need only one\, the one used to compile Perl. For OSF/1\, we really would like to have all the information in one line. Et cetera. Nice\, I want it\, but not now.

No\, one for each system. Look at the start of each line. Let's be more verbose​:

  for HP-UX 11.00 the latest HP-UX ANSI C compiler version is​:

  B3901BA B.11.01.20 HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800)

  for HP-UX 10.20 the latest HP-UX ANSI C compiler version is​:

  B3901BA B.10.20.15 HP C/ANSI C Developer's Bundle for HP-UX 10.20 (S800)

  for AIX 4.3 the latest AIX C compiler version is​:

  vac.C 4.4.0.3 C C for AIX Compiler

  for AIX 4.2 the latest AIX C compiler version is​:

  xlC.C 3.1.4.0 C C for AIX Compiler

  for DEC-Alpha OSF/1 4.0 D the latest C compiler is​:

  OSFCMPLRS425 installed Compiler Back End (Software Development)   cc (cc)   Digital UNIX Compiler Driver 3.11   DEC C V5.6-084 on Digital UNIX V4.0 (Rev. 878)

Note that DEC-Alpha 4.0D is NOT the latest OS release.

Better this way?

p5pRT commented 24 years ago

From @jhi

No\, one for each system. Look at the start of each line. Let's be more

Yes\, I could see that.

verbose​:

for HP\-UX 11\.00 the latest HP\-UX ANSI C compiler version is​:

B3901BA  B\.11\.01\.20 HP C/ANSI C Developer's Bundle for HP\-UX 11\.00 \(S800\)

for HP\-UX 10\.20 the latest HP\-UX ANSI C compiler version is​:

B3901BA  B\.10\.20\.15 HP C/ANSI C Developer's Bundle for HP\-UX 10\.20 \(S800\)

for AIX 4\.3  the latest AIX C compiler version is​:

vac\.C    4\.4\.0\.3    C         C for AIX Compiler

for AIX 4\.2  the latest AIX C compiler version is​:

xlC\.C    3\.1\.4\.0    C         C for AIX Compiler

for DEC\-Alpha OSF/1 4\.0 D the latest C compiler is​:

Still many lines of information here. We need something more compact.

OSFCMPLRS425    installed            Compiler Back End \(Software Development\)
cc  \(cc\)
    Digital UNIX Compiler Driver 3\.11
DEC C V5\.6\-084 on Digital UNIX V4\.0 \(Rev\. 878\)

Note that DEC-Alpha 4.0D is NOT the latest OS release.

I'm aware of that.

Better this way?

Yes. But I still do not see hints patches.

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 10​:50​:49 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

No\, one for each system. Look at the start of each line. Let's be more

Yes\, I could see that.

Better this way?

Yes. But I still do not see hints patches.

And put the version info where? in a new - not yet existing - ccversion?

p5pRT commented 24 years ago

From @jhi

Yes. But I still do not see hints patches.

And put the version info where? in a new - not yet existing - ccversion?

Yes.

Remember Solaris.

Don't forget to patch myconfig.SH.

p5pRT commented 24 years ago

From @jhi

AIX​: lslpp -L | grep 'C for AIX'

4.3.2​: vac.C 4.4.0.3 C C for AIX Compiler 4.2.1​: xlC.C 3.1.4.0 C C for AIX Compiler

I seem have an AIX 4.3.1.0 box with both​:

  vac.C 4.4.0.0 C C for AIX Compiler   vac.C.readme.ibm 4.4.0.0 C C for AIX iFOR/LS Information   vac.html.SBCS.search 4.4.0.0 C C for AIX Compiler Documentation   vac.html.common.search 4.4.0.0 C C for AIX Compiler Documentation   vac.html.en_US.C 4.4.0.0 C C for AIX Compiler Documentation   vac.html.en_US.search 4.4.0.0 C C for AIX Compiler Documentation   vac.msg.en_US.C 4.4.0.0 C C for AIX Compiler Messages -   xlC.cpp 4.3.0.1 C C for AIX Preprocessor   xlC.msg.en_US.cpp 4.3.0.1 C C for AIX Preprocessor Messages

Now\, if I run 'cc'\, which one do I get? How do I tell? Parse the output of 'cc -v'? Parse /etc/*.cfg? (as in /etc/xlC.cfg?)

p5pRT commented 24 years ago

From @jhi

HP-UX​: swlist -l bundle | grep B3901BA

swlist requires superuser privileges. (And getting to that error took like 20 seconds in an uploaded machines).

OSF/1​: setld -i | grep ^OSFCMPLRS; cc -V | head -3

Any faster way to do this than wade through the whole setld db?

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 10​:50​:49 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

Yes. But I still do not see hints patches.

Asuming it will be stored in ccversion (like gccversion)

*** hints/hpux.sh.orig Wed Aug 30 18​:14​:35 2000 --- hints/hpux.sh Fri Sep 1 18​:18​:49 2000 *************** *** 108\,113 **** --- 108\,114 ----   case `$cc -v 2>&1`"" in   *gcc*) ccisgcc="$define" ;;   *) ccisgcc='' ;; + ccversion=`which cc | xargs what | grep Compiler | awk '{print $2}'`   esac

  # Determine the architecture type of this system. *** hints/aix.sh.orig Fri Sep 1 18​:30​:35 2000 --- hints/aix.sh Fri Sep 1 18​:39​:08 2000 *************** *** 128\,133 **** --- 128\,137 ----   # Tell perl which symbols to export for dynamic linking.   case "$cc" in   *gcc*) ccdlflags='-Xlinker' ;; + *) ccversion=`lslpp -L | grep 'C for AIX Compiler$' | awk '{print $2}'` + case "$ccversion" in + 4.4.0.0|4.4.0.1|4.4.0.2) echo "This compiler is outdated now\, please upgrade to at least 4.4.0.3!" + esac   esac   # the required -bE​:$installarchlib/CORE/perl.exp is added by   # libperl.U (Configure) later. *** myconfig.SH.orig Fri Sep 1 18​:32​:59 2000 --- myconfig.SH Fri Sep 1 18​:33​:14 2000 *************** *** 39\,45 ****   Compiler​:   cc='$cc'\, optimize='$optimize'\, gccversion=$gccversion\, gccosandvers=$gccosandvers   cppflags='$cppflags' ! ccflags ='$ccflags'   stdchar='$stdchar'\, d_stdstdio=$d_stdstdio\, usevfork=$usevfork   intsize=$intsize\, longsize=$longsize\, ptrsize=$ptrsize\, doublesize=$doublesize\, byteorder=$byteorder   d_longlong=$d_longlong\, longlongsize=$longlongsize\, d_longdbl=$d_longdbl\, longdblsize=$longdblsize --- 39\,45 ----   Compiler​:   cc='$cc'\, optimize='$optimize'\, gccversion=$gccversion\, gccosandvers=$gccosandvers   cppflags='$cppflags' ! ccflags ='$ccflags'\, ccversion='$ccversion'   stdchar='$stdchar'\, d_stdstdio=$d_stdstdio\, usevfork=$usevfork   intsize=$intsize\, longsize=$longsize\, ptrsize=$ptrsize\, doublesize=$doublesize\, byteorder=$byteorder   d_longlong=$d_longlong\, longlongsize=$longlongsize\, d_longdbl=$d_longdbl\, longdblsize=$longdblsize *** Configure.orig Fri Sep 1 18​:35​:05 2000 --- Configure Fri Sep 1 18​:35​:54 2000 *************** *** 599\,604 **** --- 599\,605 ----   fpossize=''   fpostype=''   ccname='' + ccversion=''   gccosandvers=''   gccversion=''   gidformat=''

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 11​:22​:26 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

AIX​: lslpp -L | grep 'C for AIX'

4.3.2​: vac.C 4.4.0.3 C C for AIX Compiler 4.2.1​: xlC.C 3.1.4.0 C C for AIX Compiler

I seem have an AIX 4.3.1.0 box with both​:

vac.C 4.4.0.0 C C for AIX Compiler vac.C.readme.ibm 4.4.0.0 C C for AIX iFOR/LS Information vac.html.SBCS.search 4.4.0.0 C C for AIX Compiler Documentation vac.html.common.search 4.4.0.0 C C for AIX Compiler Documentation vac.html.en_US.C 4.4.0.0 C C for AIX Compiler Documentation vac.html.en_US.search 4.4.0.0 C C for AIX Compiler Documentation vac.msg.en_US.C 4.4.0.0 C C for AIX Compiler Messages - xlC.cpp 4.3.0.1 C C for AIX Preprocessor   ^^^^^^^^^^^^ xlC.msg.en_US.cpp 4.3.0.1 C C for AIX Preprocessor Messages

Now\, if I run 'cc'\, which one do I get? How do I tell? Parse the output of 'cc -v'? Parse /etc/*.cfg? (as in /etc/xlC.cfg?)

You have\, the heavily outdated and bogus\, 4.4.0.0 vac

Sorry for sending in too fast​:

*** hints/hpux.sh.orig Wed Aug 30 18​:14​:35 2000 --- hints/hpux.sh Fri Sep 1 18​:41​:41 2000 *************** *** 107\,113 ****

  case `$cc -v 2>&1`"" in   *gcc*) ccisgcc="$define" ;; ! *) ccisgcc='' ;;   esac

  # Determine the architecture type of this system. --- 107\,114 ----

  case `$cc -v 2>&1`"" in   *gcc*) ccisgcc="$define" ;; ! *) ccisgcc='' ! ccversion=`which cc | xargs what | grep Compiler | awk '{print $2}'` ;;   esac

  # Determine the architecture type of this system. *** Configure.orig Fri Sep 1 18​:35​:05 2000 --- Configure Fri Sep 1 18​:45​:48 2000 *************** *** 599\,604 **** --- 599\,605 ----   fpossize=''   fpostype=''   ccname='' + ccversion=''   gccosandvers=''   gccversion=''   gidformat='' *************** *** 15431\,15436 **** --- 15432\,15438 ----   ccflags_uselargefiles='$ccflags_uselargefiles'   ccname='$ccname'   ccsymbols='$ccsymbols' + ccversion='$ccversion'   cf_by='$cf_by'   cf_email='$cf_email'   cf_time='$cf_time' *** hints/aix.sh.orig Fri Sep 1 18​:30​:35 2000 --- hints/aix.sh Fri Sep 1 18​:46​:45 2000 *************** *** 128\,133 **** --- 128\,137 ----   # Tell perl which symbols to export for dynamic linking.   case "$cc" in   *gcc*) ccdlflags='-Xlinker' ;; + *) ccversion=`lslpp -L | grep 'C for AIX Compiler$' | awk '{print $2}'` + case "$ccversion" in + 4.4.0.0|4.4.0.1|4.4.0.2) echo "This compiler is outdated now\, please upgrade to at least 4.4.0.3!" ;; + esac ;;   esac   # the required -bE​:$installarchlib/CORE/perl.exp is added by   # libperl.U (Configure) later.

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 11​:27​:07 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

HP-UX​: swlist -l bundle | grep B3901BA

swlist requires superuser privileges. (And getting to that error took like 20 seconds in an uploaded machines).

fixed in patch.

OSF/1​: setld -i | grep ^OSFCMPLRS; cc -V | head -3

Any faster way to do this than wade through the whole setld db?

How do I hate DEC-OSF/1 ;-) (yes I really do)

I'll check\, but didn't find it yet.

We'll remove this machine from our company in Januari 2001\, due to that single customar finaly decided that there are better machines :-)))

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 11​:08​:55 -0500\, Jarkko Hietaniemi \jhi@​iki\.fi wrote​:

Yes. But I still do not see hints patches.

And put the version info where? in a new - not yet existing - ccversion?

Yes.

Remember Solaris.

Don't forget to patch myconfig.SH.

Last one​:

*** hints/dec_osf.sh.orig Fri Sep 1 18​:56​:52 2000 --- hints/dec_osf.sh Fri Sep 1 18​:57​:20 2000 *************** *** 99\,104 **** --- 99\,105 ----   fi   ;;   *) # compile something small​: taint.c is fine for this. + ccversion=`cc -V | grep 'DEC C' | awk '{print $3}'`   # the main point is the '-v' flag of 'cc'.   case "`cc -v -I. -c taint.c -o taint$$.o 2>&1`" in   */gemc_cc*) # we have the new DEC GEM CC

p5pRT commented 24 years ago

From [Unknown Contact. See original ticket]

On Fri\, 1 Sep 2000\, Jarkko Hietaniemi wrote​:

AIX​: lslpp -L | grep 'C for AIX'

4.3.2​: vac.C 4.4.0.3 C C for AIX Compiler 4.2.1​: xlC.C 3.1.4.0 C C for AIX Compiler

I seem have an AIX 4.3.1.0 box with both​:

vac.C 4.4.0.0 C C for AIX Compiler vac.C.readme.ibm 4.4.0.0 C C for AIX iFOR/LS Information vac.html.SBCS.search 4.4.0.0 C C for AIX Compiler Documentation vac.html.common.search 4.4.0.0 C C for AIX Compiler Documentation vac.html.en_US.C 4.4.0.0 C C for AIX Compiler Documentation vac.html.en_US.search 4.4.0.0 C C for AIX Compiler Documentation vac.msg.en_US.C 4.4.0.0 C C for AIX Compiler Messages - xlC.cpp 4.3.0.1 C C for AIX Preprocessor xlC.msg.en_US.cpp 4.3.0.1 C C for AIX Preprocessor Messages

Now\, if I run 'cc'\, which one do I get? How do I tell? Parse the output of 'cc -v'? Parse /etc/*.cfg? (as in /etc/xlC.cfg?)

You can get the AIX "fileset" that a given file is in with lslpp -w\, so something like this would work​:

  cc=$(which cc)   truecc=$(ls -l $cc | awk '{ print $NF }')   fileset=$(lslpp -w $truecc | awk 'NR == 3 { print $2 }')   ccversion=$(lslpp -L $fileset | awk 'NR == 3 { print }')

BTW\, there's now also a version 5 compiler for AIX.

John.

p5pRT commented 24 years ago

From @tux

On Fri\, 1 Sep 2000 13​:38​:38 -0400 (EDT)\, "John L. Allen" \allen@​grumman\.com wrote​:

You can get the AIX "fileset" that a given file is in with lslpp -w\, so something like this would work​:

cc=$(which cc) truecc=$(ls -l $cc | awk '{ print $NF }') fileset=$(lslpp -w $truecc | awk 'NR == 3 { print $2 }') ccversion=$(lslpp -L $fileset | awk 'NR == 3 { print }')

BTW\, there's now also a version 5 compiler for AIX.

I know\, but FAFAIK that's supposed to work only on AIX 4.3.3 and up\, not on 4.3.2. Is this correct\, or is it worthwhile and possible to upgrade to 5?