public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: marcus@mc.pp.se
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/7454: make boostraps fails on SPARC v8
Date: Wed, 31 Jul 2002 07:36:00 -0000 [thread overview]
Message-ID: <20020731142810.02FF5C1EE@continuity.mc.pp.se> (raw)
>Number: 7454
>Category: bootstrap
>Synopsis: make boostraps fails on SPARC v8
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jul 31 07:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Marcus Comstedt
>Release: 3.1.1
>Organization:
>Environment:
System: SunOS continuity 5.8 Generic_108528-10 sun4m sparc SUNW,SPARCstation-10
Architecture: sun4
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: /home/marcus/gcc-3.1.1/configure --with-cpu=hypersparc
>Description:
When making bootstrap on a SPARC v8 machine (supersparc/hypersparc), the
build bombs out while building target libs. The reason is that
A) the default is to build libs for SPARC v9 as well (in which case GCC
will act as a cross compiler, since v9 executables can't be run on a
v8 CPU)
B) the libffi and libjava configure scripts have one test each (for
processor endianness and /proc/self/exe existence respectively)
which will abort the build if configured with a cross compiler
(Also note that if a configure script for a multilib subtarget fails, and it
is not the first multilib subtarget in the list, then `make bootstrap' will
fail to resume the build after the error is corrected, since it assumes
that if the configuration of the first subtarget succeeded, then _all_
subtargets have been configured successfully.)
>How-To-Repeat:
`make bootstrap' on a sun4m machine running solaris 8.
>Fix:
By manually providing the correct answers to the two configure tests, a
complete bootstrap including SPARC v9 libs can be built:
ac_cv_c_bigendian=yes
ac_cv_file__proc_self_exe=no
export ac_cv_c_bigendian
export ac_cv_file__proc_self_exe
(These values are correct for Solaris 8. For other operating systems
(Linux?) another value for ac_cv_file__proc_self_exe may be appropriate.)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-07-31 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 7:36 marcus [this message]
2002-07-31 7:40 davem
2002-07-31 8:36 Marcus Comstedt
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=20020731142810.02FF5C1EE@continuity.mc.pp.se \
--to=marcus@mc.pp.se \
--cc=gcc-gnats@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).