public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Mentovai <mark@moxienet.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
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 16:26:00 -0000	[thread overview]
Message-ID: <20020628232601.5597.qmail@sources.redhat.com> (raw)

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
 


             reply	other threads:[~2002-06-28 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 16:26 Mark Mentovai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-28  8:36 davem
2002-06-28  7:16 mark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020628232601.5597.qmail@sources.redhat.com \
    --to=mark@moxienet.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).