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


>Number:         7156
>Category:       target
>Synopsis:       Should not attempt to build 32/64 bi-arch compiler on sparc-*-solaris2.[789] if unsupported, bootstrap will fail
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 28 07:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Mark Mentovai
>Release:        3.1, gcc-3_1-branch 3.1.1 20020625 (prerelease), and gcc 3.2 20020618 (experimental)
>Organization:
>Environment:
System: SunOS oak 5.7 Generic_106541-16 sun4m sparc SUNW,SPARCstation-20
Architecture: sun4
Sun SPARCstation 20, 150MHz hyperSPARC, 128MB, 3x4.4GB
Sun Solaris 7 3/99 MU 4
host: sparc-sun-solaris2.7
build: sparc-sun-solaris2.7
target: sparc-sun-solaris2.7
configured with: ../gcc-3.1/configure --enable-shared --with-gnu-as --with-gnu-ld --enable-threads --with-cpu=hypersparc --enable-libgcj --with-system-zlib
>Description:
The build system currently attempts to build a 32/64-bit bi-arch compiler on sparc-*-solaris2.[789] regardless of the system's ability to support such a build.

In order to bootstrap the compiler, the libraries for all environments must be present.  When building a 32/64-bit bi-arch compiler, the libraries for both the 32- and 64-bit environments must be available.  They are usually not present on 32-bit systems (for systems manufactured by Sun, this is anything prior to the Ultra).

Even if both 32- and 64-bit libraries are installed on a 32-bit system, the bootstrap can fail when attempting to build support libraries for some languages.  For example, the configuration of libjava for sparcv9 will fail with:

checking for /proc/self/exe... configure: error: Cannot check for file existence when cross compiling
>How-To-Repeat:
On a 32-bit pre-sun4u system (sun4m, sun4c) running Solaris 7, 8, or 9:

sh ../gcc-3.1/configure --enable-shared --with-gnu-as --with-gnu-ld --enable-threads --with-cpu=hypersparc --enable-libgcj --with-system-zlib
make bootstrap
>Fix:
This patch causes config.gcc to determine whether or not the 64-bit sparcv9 environment is supported, and exclude 64-bit support if it is not.

If the configure scripts for libjava and others can be fixed to not give errors such as the one above, a more appropriate check would be for whether or not the appropriate 64-bit libraries are installed.  If both "pkginfo -q SUNWarcx" and "pkginfo -q SUNWcslx" exit with status 0, even on a system that is incapable of executing 64-bit sparcv9 executables, it is reasonably safe to assume that it is capable of building 64-bit sparcv9 executables.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="gcc-3.1-optisa.patch.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc-3.1-optisa.patch.bz2"

QlpoOTFBWSZTWcx+ycIAAwPfgEAwXP//+k8zDor////qUAVejUjK0JAUFSBppBCepsmqbTVP0Jmp
NHqfqeqaaB6RiDanqDQEoCBJoap6IeSaAGgADQAGgDmjJiYAJiMCNMCDEYJkwCMOaMmJgAmIwI0w
IMRgmTAIwSJBAJkhhTxDVPRqHqNA0xAB5I9T1GBgLIaKSHKG3IhQMJP7yAgA+OnwYdbgPq6nDztD
g4qq9vLhVz0B9B8ywdoQLxUcuOfw5eD2g5O4yczypaKERk0G3f43Zq4Bol1XzHjY7suw0rjprvMd
ljgUDeYEYAsraTl0RTbGP65YbaKzPPYecibYOspu0ekPFrg8zv1kw8u+pg4HAV1CXmLdC3tXDpCu
wp2Nl+idWObpz655pbROVrZPbHSbyLW3PxjusgXfiNQgRFXgCdgNmcoLOtTjCgxJkzlFvEuzzilN
3Sl897Y/wjFkfM4Psu2exxqWkstUN8aYicLvmFMm8CGIvo9krpa+U6GUlTqtzO1Kg7UG8aAkP6Kr
i8JgAQR1o4BQc4UEC9ddL9yZIEwBfXjolfiRW24dHAQRMRHYPgrWIJOGQEa2Kq6iQEKI4axmRfYy
jdKprVNjOoLwCQTsO4WozFNGiXfW9j0mgpDW48HLIXfQlMbMjvBgw1qEVooLYG9yGkPry96ApBMp
70NLAflIvI+aHyuKCZ6UNOzXjVkaOu4NI9ViCkAY/EM3kMbpEJo8iIG3LxJeI+1YK8PrBfAl91QN
WyG2FXiVvSP3O8eaaZHNm+eUIshSxO/mIEjL5V49aVKmYL1h4EAfL2+2qtRivKZNl51GPcYGJfaj
S3zJYNXMMxeB80IC8hKlAcSRJKTVpNovGhjR8YAmuHMjWgJb1nUGyhfedC3zSm80NHGUbrIsVqDb
imlScpOHBE3CZLGdSVtTsKbuPDItg2rwV1r/GlUw5JJBAsViCLcrx1LZQcUsB7g1OYSUaWgZ8lcE
kCo2RJtpyQaQlroLtZLxNOBe1U3+4OFcjCuCImYQzg0SoLq+WPIY2lET9Vhpxs1I3IKeYA4Gl4uE
qC6/7OZ2hgyxHQjHrJVLC+9bLh9gDIFChB5tKE0f93OAZOZIgx3I4dwJm5JozDah8aoLA3iISPYA
xO7IsXI59plnibqysWcM5x3BNcawNqqoi09eoCiGgjUY5aULth0h0EWLeuYD0hRzGG0ZiMMBjucA
WjAg0gXbrShZNr6tW27qvuRALsFDG3Z1w3RCBnYBzWyCwVUHlRVZe3DzEok0pRNA0E4B1Vr6mE6B
ag6SyAeGwYH+NtZXBrBdCCBXyiSCYS1qDX/Pk+3FebL+iFLGLqc44IZsEZKmxctfRTqR0giwwQax
4o3IqUMBnfQqE0aR3kt7Gy6ITBg2NPKrWSKYAlRtkN4DddeB0sqhmkBhKoMqULaK4Vcp2n7oWpoO
ymtWLOMQpKlYndWBSUUFQXWONrZg8tZMTVamw6SQJvm9ZdW8hGBiW2R9KU81WU0UEhlL1wkQDKuj
IQSw7w6OoMbkaiG0go5cULAthQwgoZ5IWMKrAg47alvqxlCH/vqbXoLkQWoVOepWyHir0bXn7KnO
0LpchFxP09zhHG1bcnlyNJpEi95x6b8wsQWaQiaVjIRK3ScjB8gzSv2CqL/xdyRThQkMx+ycIA==


             reply	other threads:[~2002-06-28 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28  7:16 mark [this message]
2002-06-28  8:36 davem
2002-06-28 16:26 Mark Mentovai

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=20020628140828.3475.qmail@sources.redhat.com \
    --to=mark@moxienet.com \
    --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).