This is the mail archive of the gcc-prs@gcc.gnu.org mailing list for the GCC 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]

Re: target/7156: Should not attempt to build 32/64 bi-archcompiler on sparc-*-solaris2.[789] if unsupported, bootstrap will fail


The following reply was made to PR target/7156; it has been noted by GNATS.

From: Mark Mentovai <mark@moxienet.com>
To: <davem@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: target/7156: Should not attempt to build 32/64 bi-arch
	compiler on sparc-*-solaris2.[789] if unsupported, bootstrap will fail
Date: Fri, 28 Jun 2002 19:17:32 -0400

 davem@gcc.gnu.org wrote:
 >   The build instructions are very precise in telling the user
 >   that they must "--disable-multilib" on the configure command
 >   line if their system does not support generation of 64-bit
 >   binaries.
 >   
 >   Several attempts were made close to the 3.1 release to automate this but
 > none of them proved to be reliable and
 >   do the right thing in cross-compilation scenerios.
 
 Something else must be wrong then if cross-compiling is an important
 consideration: libjava refuses to configure itself when being cross-compiled
 (as described in the PR).
 
 gcc-3.1/libjava/configure:3922
 
   if test "$cross_compiling" = yes; then
     { echo "configure: error: Cannot check for file existence when cross
 compiling" 1>&2; exit 1; }
 else
 # ...
   fi
 
 Provided that this could be fixed, what seems like the correct solution
 would be to check for the appropriate support packages (SUNWarcx and
 SUNWcslx) and automatically disable multilib if both are not present only
 when doing a native build, and retain the current behavior when doing a
 cross build.
 
 Mark
 


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