This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

config.guess change for solaris

The intent here is to be able to distinguish a machine
that can execute 64-bit binaries from one that cannot.
This is hindered by the fact that one can install a
32-bit only kernel on a machine otherwise capable of
64-bit operation.

We're using the following designations in gcc 3.1:

	sparc-solaris		32-bit only
	sparcv9-solaris		32-bit default, 64-bit capable
	sparc64-solaris		64-bit default

Note that config.guess never chooses sparc64-solaris.
With the sparcv9 configury, one can use -m64 if you 
want to generate 64-bit code.


        * config.guess (sun4u:SunOS:5.*:*): Guess sparcv9 if 64-bit isa
        is supported.

Index: config.guess
RCS file: /cvs/gcc/gcc/config.guess,v
retrieving revision 1.49
diff -c -p -d -r1.49 config.guess
*** config.guess	9 Feb 2002 03:00:13 -0000	1.49
--- config.guess	12 Apr 2002 22:21:43 -0000
*************** EOF
*** 315,320 ****
--- 315,330 ----
  	echo sparc-hal-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
  	exit 0 ;;
+     sun4u:SunOS:5.*:*)
+ 	# Detect whether or not this machine can run 64-bit binaries.
+ 	# Note that even with hardware that is capable, the user can
+ 	# run a kernel that only allows 32-bit binaries.
+ 	case `(isalist) 2>/dev/null || echo sparc` in
+ 	    *sparcv9*)	UNAME_MACHINE=sparcv9 ;;
+ 	    *)		UNAME_MACHINE=sparc ;;
+ 	esac
+ 	echo ${UNAME_MACHINE}-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
+ 	exit 0 ;;
      sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
  	echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
  	exit 0 ;;

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]