From Kevin.Ruscoe@ubsw.com

This is a bug report for perl from Kevin.Ruscoe@​ubsw.com,
generated with the help of perlbug 1.28 running under perl v5.6.0.

Hi

Line 390 of .../hints/solaris_2.sh uses the match string "2.[1-6]" to
determine
whether the version of Solaris is late enough to support 64 bit
integers.
However, uname(1) reports the operating system release level using
the kernel's
5.x numbering system, so the string should be "5.[1-6]".

Best wishes

Kevin

Flags​:
  category=install
  severity=low

Site configuration information for perl v5.6.0​:

Configured by ruscoekm at Tue May 16 13​:32​:43 BST 2000.

Summary of my perl5 (revision 5.0 version 6 subversion 0)
configuration​:
  Platform​:
  osname=solaris, osvers=2.6, archname=sun4-solaris-thread
  uname='sunos ln16p1166swk 5.6 generic_105181-12 sun4u sparc
sunw,ultra-2 '
  config_args=''
  hint=recommended, useposix=true, d_sigaction=define
  usethreads=define use5005threads=define useithreads=undef
usemultiplicity=undef
  useperlio=undef d_sfio=undef uselargefiles=define
  use64bitint=undef use64bitall=undef uselongdouble=undef
usesocks=undef
  Compiler​:
  cc='cc', optimize='-O', gccversion=
  cppflags='-D_REENTRANT'
  ccflags ='-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
  stdchar='unsigned char', d_stdstdio=define, usevfork=false
  intsize=4, longsize=4, ptrsize=4, doublesize=8
  d_longlong=define, longlongsize=8, d_longdbl=define,
longdblsize=16
  ivtype='long', ivsize=4, nvtype='double', nvsize=8,
Off_t='off_t', lseeksize=8
  alignbytes=8, usemymalloc=y, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags =' '
  libpth=/lib /usr/lib /usr/ccs/lib
  libs=-lsocket -lnsl -ldl -lm -lposix4 -lpthread -lc -lcrypt -lsec
  libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
  cccdlflags='-KPIC', lddlflags='-G'

Locally applied patches​:
 

@​INC for perl v5.6.0​:
  /home/ruscoekm/wa_tree/lib
  /home/ruscoekm/3ps/perl_modules/install/lib/site_perl
  /home/ruscoekm/3ps/perl_modules/install/lib/site_perl/sun4-solaris
  /home/ruscoekm/3ps/perl/install/lib/5.6.0/sun4-solaris-thread
  /home/ruscoekm/3ps/perl/install/lib/5.6.0
 
/home/ruscoekm/3ps/perl/install/lib/site_perl/5.6.0/sun4-solaris-threa
d
  /home/ruscoekm/3ps/perl/install/lib/site_perl/5.6.0
  /home/ruscoekm/3ps/perl/install/lib/site_perl
  .

Environment for perl v5.6.0​:
  HOME=/home/ruscoekm
  LANG=C
  LANGUAGE (unset)
  LC_CTYPE=C
 
LD_LIBRARY_PATH=/usr/dt/lib​:/usr/openwin/lib​:/home/ruscoekm/wa_tree/li
nks/sybase/lib​:/home/ruscoekm/wa_tree/links/xemacs/lib​:/home/ruscoekm/
wa_tree/links/png/lib​:/home/ruscoekm/wa_tree/links/xpm/lib​:/home/rusco
ekm/wa_tree/links/reuters/lib/sun4_5.5​:/home/ruscoekm/wa_tree/links/re
uters/lib/sun4_5.5-sw​:/home/ruscoekm/wa_tree/links/rogue/4d/lib​:/home/
ruscoekm/wa_tree/links/rogue/7d/lib​:/home/ruscoekm/wa_tree/links/tcl/l
ib​:/home/ruscoekm/wa_tree/lib
  LOGDIR (unset)
 
PATH=/home/staffoph/sccs/prod/bin​:/home/wa_dev/sccs/prod/bin​:/usr/bin​:
/usr/dt/bin​:/usr/openwin/bin​:/usr/ccs/bin​:/home/ruscoekm/wa_tree/links
/sybase/bin​:/home/ruscoekm/wa_tree/links/xemacs/bin​:/home/ruscoekm/wa_
tree/links/xpm/bin​:/home/ruscoekm/wa_tree/links/sparcworks/bin​:/home/r
uscoekm/wa_tree/links/perl/bin​:/home/ruscoekm/wa_tree/links/bash/bin​:/
home/ruscoekm/wa_tree/links/ddd/bin​:/home/ruscoekm/wa_tree/links/gzip/
bin​:/home/ruscoekm/wa_tree/links/sqsh/bin​:/home/ruscoekm/wa_tree/bin​:/
home/ruscoekm/wa_tree/links/enscript/bin​:/home/ruscoekm/wa_tree/links/
books/power_tools/prod/bin​:/home/ruscoekm/bin​:/home/ruscoekm/wa_tree/l
inks/gnats/bin​:/home/ruscoekm/wa_tree/links/gnats/libexec/gnats​:/home/
ruscoekm/wa_tree/links/tcl/bin
 
PERLLIB=/home/ruscoekm/wa_tree/lib​:/home/ruscoekm/3ps/perl_modules/ins
tall/lib/site_perl​:/home/ruscoekm/3ps/perl_modules/install/lib/site_pe
rl/sun4-solaris
  PERL_BADLANG (unset)
  SHELL=/sbcimp/run/pd/bash/prod/bin/bash

From Kevin.Ruscoe@ubsw.com

To​: perlbug@​perl.com
Subject​: Typo on line 390 of .../hints/solaris_2.sh
Cc​: Kevin.Ruscoe@​ubsw.com
Reply-To​: Kevin.Ruscoe@​ubsw.com

This is a bug report for perl from Kevin.Ruscoe@​ubsw.com,
generated with the help of perlbug 1.28 running under perl v5.6.0.

Line 390 of .../hints/solaris_2.sh uses the match string "2.[1-6]" to determine
whether the version of Solaris is late enough to support 64 bit integers.
However, uname(1) reports the operating system release level using the kernel's
5.x numbering system, so the string should be "5.[1-6]".

Flags​:
  category=install
  severity=low

Site configuration information for perl v5.6.0​:

Configured by ruscoekm at Tue May 16 13​:32​:43 BST 2000.

Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration​:
  Platform​:
  osname=solaris, osvers=2.6, archname=sun4-solaris-thread
  uname='sunos ln16p1166swk 5.6 generic_105181-12 sun4u sparc sunw,ultra-2 '
  config_args=''
  hint=recommended, useposix=true, d_sigaction=define
  usethreads=define use5005threads=define useithreads=undef usemultiplicity=undef
  useperlio=undef d_sfio=undef uselargefiles=define
  use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
  Compiler​:
  cc='cc', optimize='-O', gccversion=
  cppflags='-D_REENTRANT'
  ccflags ='-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
  stdchar='unsigned char', d_stdstdio=define, usevfork=false
  intsize=4, longsize=4, ptrsize=4, doublesize=8
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
  ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
  alignbytes=8, usemymalloc=y, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags =' '
  libpth=/lib /usr/lib /usr/ccs/lib
  libs=-lsocket -lnsl -ldl -lm -lposix4 -lpthread -lc -lcrypt -lsec
  libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
  cccdlflags='-KPIC', lddlflags='-G'

Locally applied patches​:
 

@​INC for perl v5.6.0​:
  /home/ruscoekm/wa_tree/lib
  /home/ruscoekm/3ps/perl_modules/install/lib/site_perl
  /home/ruscoekm/3ps/perl_modules/install/lib/site_perl/sun4-solaris
  /home/ruscoekm/3ps/perl/install/lib/5.6.0/sun4-solaris-thread
  /home/ruscoekm/3ps/perl/install/lib/5.6.0
  /home/ruscoekm/3ps/perl/install/lib/site_perl/5.6.0/sun4-solaris-thread
  /home/ruscoekm/3ps/perl/install/lib/site_perl/5.6.0
  /home/ruscoekm/3ps/perl/install/lib/site_perl
  .

Environment for perl v5.6.0​:
  HOME=/home/ruscoekm
  LANG=C
  LANGUAGE (unset)
  LC_CTYPE=C
  LD_LIBRARY_PATH=/usr/dt/lib​:/usr/openwin/lib​:/home/ruscoekm/wa_tree/links/sybase/lib​:/home/ruscoekm/wa_tree/links/xemacs/lib​:/home/ruscoekm/wa_tree/links/png/lib​:/home/ruscoekm/wa_tree/links/xpm/lib​:/home/ruscoekm/wa_tree/links/reuters/lib/sun4_5.5​:/home/ruscoekm/wa_tree/links/reuters/lib/sun4_5.5-sw​:/home/ruscoekm/wa_tree/links/rogue/4d/lib​:/home/ruscoekm/wa_tree/links/rogue/7d/lib​:/home/ruscoekm/wa_tree/links/tcl/lib​:/home/ruscoekm/wa_tree/lib
  LOGDIR (unset)
  PATH=/home/staffoph/sccs/prod/bin​:/home/wa_dev/sccs/prod/bin​:/usr/bin​:/usr/dt/bin​:/usr/openwin/bin​:/usr/ccs/bin​:/home/ruscoekm/wa_tree/links/sybase/bin​:/home/ruscoekm/wa_tree/links/xemacs/bin​:/home/ruscoekm/wa_tree/links/xpm/bin​:/home/ruscoekm/wa_tree/links/sparcworks/bin​:/home/ruscoekm/wa_tree/links/perl/bin​:/home/ruscoekm/wa_tree/links/bash/bin​:/home/ruscoekm/wa_tree/links/ddd/bin​:/home/ruscoekm/wa_tree/links/gzip/bin​:/home/ruscoekm/wa_tree/links/sqsh/bin​:/home/ruscoekm/wa_tree/bin​:/home/ruscoekm/wa_tree/links/enscript/bin​:/home/ruscoekm/wa_tree/links/books/power_tools/prod/bin​:/home/ruscoekm/bin​:/home/ruscoekm/wa_tree/links/gnats/bin​:/home/ruscoekm/wa_tree/links/gnats/libexec/gnats​:/home/ruscoekm/wa_tree/links/tcl/bin
  PERLLIB=/home/ruscoekm/wa_tree/lib​:/home/ruscoekm/3ps/perl_modules/install/lib/site_perl​:/home/ruscoekm/3ps/perl_modules/install/lib/site_perl/sun4-solaris
  PERL_BADLANG (unset)
  SHELL=/sbcimp/run/pd/bash/prod/bin/bash

From Kevin.Ruscoe@ubsw.com

This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

From [Unknown Contact. See original ticket]

Kevin.Ruscoe@​ubsw.com [Kevin.Ruscoe@​ubsw.com] quoth​:
*>
*>Line 390 of .../hints/solaris_2.sh uses the match string "2.[1-6]" to
*>determine whether the version of Solaris is late enough to support 64 bit
*>integers. However, uname(1) reports the operating system release level using
*>the kernel's 5.x numbering system, so the string should be "5.[1-6]".

Since it is using 'uname -r' 2.* would not match as Solaris, despite the
new numbering of 8 and 7, etc., still call themselves 5.8 and 5.7 like its
5.6, 5.5.1 and brethren. Solaris 1.1.1 is SunOS 4.1.4 and SunOS 5.6 is really
Solaris 2.6...now 8 can be either 2.8 or 5.8....It can get confusing.

I don't have a < 2.6 box anymore but I don't recall ever seeing uname return
anything but a 5.* on a Solaris system so there may be more to this than
meets the eye.

e.

*** solaris_2.sh.orig Fri Jun 16 12​:58​:03 2000
--- solaris_2.sh Fri Jun 16 12​:59​:14 2000
***************
*** 385,395 ****
  # This script UU/use64bitint.cbu will get 'called-back' by Configure
  # after it has prompted the user for whether to use 64 bit integers.
  case "$use64bitint" in
  "$define"|true|[yY]*)
  case "`uname -r`" in
! 2.[1-6])
  cat >&4 <<EOM
  Solaris `uname -r` does not support 64-bit integers.
  You should upgrade to at least Solaris 2.7.
  EOM
  exit 1
--- 385,395 ----
  # This script UU/use64bitint.cbu will get 'called-back' by Configure
  # after it has prompted the user for whether to use 64 bit integers.
  case "$use64bitint" in
  "$define"|true|[yY]*)
  case "`uname -r`" in
! 5.[1-6])
  cat >&4 <<EOM
  Solaris `uname -r` does not support 64-bit integers.
  You should upgrade to at least Solaris 2.7.
  EOM
  exit 1

From [Unknown Contact. See original ticket]

From perl5-porters-return-13783-rmb1=cise.npl.co.uk@​perl.org Fri Jun 16 19​:09​:43 2000
Kevin.Ruscoe@​ubsw.com [Kevin.Ruscoe@​ubsw.com] quoth​:
*>
*>Line 390 of .../hints/solaris_2.sh uses the match string "2.[1-6]" to
*>determine whether the version of Solaris is late enough to support 64 bit
*>integers. However, uname(1) reports the operating system release level using
*>the kernel's 5.x numbering system, so the string should be "5.[1-6]".

Since it is using 'uname -r' 2.* would not match as Solaris, despite the
new numbering of 8 and 7, etc., still call themselves 5.8 and 5.7 like its
5.6, 5.5.1 and brethren. Solaris 1.1.1 is SunOS 4.1.4 and SunOS 5.6 is really
Solaris 2.6...now 8 can be either 2.8 or 5.8....It can get confusing.

I don't have a < 2.6 box anymore but I don't recall ever seeing uname return
anything but a 5.* on a Solaris system so there may be more to this than
meets the eye.

To my eye, you are violently agreeing.

e.

*** solaris_2.sh.orig Fri Jun 16 12​:58​:03 2000
--- solaris_2.sh Fri Jun 16 12​:59​:14 2000
***************
*** 385,395 ****
# This script UU/use64bitint.cbu will get 'called-back' by Configure
# after it has prompted the user for whether to use 64 bit integers.
case "$use64bitint" in
"$define"|true|[yY]*)
case "`uname -r`" in
! 2.[1-6])
cat >&4 <<EOM
Solaris `uname -r` does not support 64-bit integers.
You should upgrade to at least Solaris 2.7.
EOM
exit 1
--- 385,395 ----
# This script UU/use64bitint.cbu will get 'called-back' by Configure
# after it has prompted the user for whether to use 64 bit integers.
case "$use64bitint" in
"$define"|true|[yY]*)
case "`uname -r`" in
! 5.[1-6])
cat >&4 <<EOM
Solaris `uname -r` does not support 64-bit integers.
You should upgrade to at least Solaris 2.7.
EOM
exit 1

Don't we need
*** solaris_2.sh.orig Fri Jun 16 12​:58​:03 2000
--- solaris_2.sh Fri Jun 16 12​:59​:14 2000
***************
*** 385,395 ****
  # This script UU/use64bitint.cbu will get 'called-back' by Configure
  # after it has prompted the user for whether to use 64 bit integers.
  case "$use64bitint" in
  "$define"|true|[yY]*)
  case "`uname -r`" in
! 2.[1-6])
  cat >&4 <<EOM
! Solaris `uname -r` does not support 64-bit integers.
! You should upgrade to at least Solaris 2.7.
  EOM
  exit 1
--- 385,395 ----
  # This script UU/use64bitint.cbu will get 'called-back' by Configure
  # after it has prompted the user for whether to use 64 bit integers.
  case "$use64bitint" in
  "$define"|true|[yY]*)
  case "`uname -r`" in
! 5.[1-6])
  cat >&4 <<EOM
! SunOS `uname -r` does not support 64-bit integers.
! You should upgrade to at least SunOS 5.7 (i.e. Solaris 2.7).
  EOM
  exit 1

Robin

From [Unknown Contact. See original ticket]

Robin Barker [rmb1@​cise.npl.co.uk] quoth​:
*>
*>To my eye, you are violently agreeing.

No, I was sure it couldn't be quite that obvious, but sometimes the
obvious is the most often overlooked.

Configure does "$sed 's/^5/2/g'" on the osversion for solaris. I don't
even want to know why :)

e.

From [Unknown Contact. See original ticket]

On Fri, Jun 16, 2000 at 01​:09​:19PM -0500, HappyFunBall wrote​:

Kevin.Ruscoe@​ubsw.com [Kevin.Ruscoe@​ubsw.com] quoth​:
*>
*>Line 390 of .../hints/solaris_2.sh uses the match string "2.[1-6]" to
*>determine whether the version of Solaris is late enough to support 64 bit
*>integers. However, uname(1) reports the operating system release level using
*>the kernel's 5.x numbering system, so the string should be "5.[1-6]".

Since it is using 'uname -r' 2.* would not match as Solaris, despite the
new numbering of 8 and 7, etc., still call themselves 5.8 and 5.7 like its
5.6, 5.5.1 and brethren. Solaris 1.1.1 is SunOS 4.1.4 and SunOS 5.6 is really
Solaris 2.6...now 8 can be either 2.8 or 5.8....It can get confusing.

I don't have a < 2.6 box anymore but I don't recall ever seeing uname return
anything but a 5.* on a Solaris system so there may be more to this than
meets the eye.

  FYI, Solaris 2.5.1 returns `5.5.1'.

  Peace,
* Kurt Starsinic (kstar@​orientation.com) ---------- Senior Network Engineer *
| `People keep pretending they can make things deeply |
| hierarchical, categorizable and sequential when they can't. |
| Everything is deeply intertwingled.' -- Ted Nelson |

From [Unknown Contact. See original ticket]

rmb1@​cise.npl.co.uk (Robin Barker ) writes​:

Don't we need
*** solaris_2.sh.orig Fri Jun 16 12​:58​:03 2000
--- solaris_2.sh Fri Jun 16 12​:59​:14 2000
***************
*** 385,395 ****
# This script UU/use64bitint.cbu will get 'called-back' by Configure
# after it has prompted the user for whether to use 64 bit integers.
case "$use64bitint" in
"$define"|true|[yY]*)
case "`uname -r`" in
! 2.[1-6])
cat >&4 <<EOM
! Solaris `uname -r` does not support 64-bit integers.
! You should upgrade to at least Solaris 2.7.
EOM
exit 1
--- 385,395 ----
# This script UU/use64bitint.cbu will get 'called-back' by Configure
# after it has prompted the user for whether to use 64 bit integers.
case "$use64bitint" in
"$define"|true|[yY]*)
case "`uname -r`" in
! 5.[1-6])
cat >&4 <<EOM
! SunOS `uname -r` does not support 64-bit integers.
! You should upgrade to at least SunOS 5.7 (i.e. Solaris 2.7).
EOM
exit 1

I'd recommend using the following message to avoid confusing people​:

Solaris `uname -r | sed -e 's/^5\.\(\<[0-6]\>\)/2.\1/' -e 's/^5\.//'` does not support 64-bit integers.
You should upgrade to at least Solaris 7.

This follows Sun's marketing nomenclature of 2.0 .. 2.6, 7, 8 and
assumes that future releases will continue to use Solaris \d+.
I think many people believe SunOS != Solaris (disjuct), while
SunOS < Solaris (part-of). (Excuses to all math people for the
notation...)

Lupe Christoph

From @iabyn

This appears to have been fixed at some point.

@iabyn - Status changed from 'open' to 'resolved'