public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ralfixx@gmx.de To: gcc-gnats@gcc.gnu.org Subject: bootstrap/6952: gcc 3.1 fails to configure on HP-UX A.09 Date: Fri, 07 Jun 2002 02:46:00 -0000 [thread overview] Message-ID: <20020607094556.583.qmail@sources.redhat.com> (raw) >Number: 6952 >Category: bootstrap >Synopsis: gcc 3.1 fails to configure on HP-UX A.09 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jun 07 02:46:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ralf Fassel >Release: gcc 3.1 >Organization: >Environment: HP-UX venus A.09.05 A 9000/712 gcc 3.1 >Description: configure fails in gcc-3.1/gcc due to od -c output. On HP-UX A09, `od -c' lists offset information in decimal by default, but the configure script expects octal numbers. This breaks the tests for endianness and floating point format. I am aware that HP A09 is quite old, but I thought I report it anyway. >How-To-Repeat: HP-UX venus A.09.05 A 9000/712 ./configure ... Configuring gcc... ... checking for CHAR_BIT... yes checking byte ordering... unknown configure: error: *** unable to determine endianness >Fix: Changing the arguments to od from `od -c' to `od -tc -Ao'. I don't know whether other systems will break. *** gcc-3.1/gcc/aclocal.m4~ Tue Jan 22 23:48:45 2002 --- gcc-3.1/gcc/aclocal.m4 Fri Jun 7 11:42:00 2002 *************** *** 935,941 **** $1 ]EOF if AC_TRY_EVAL(ac_compile); then ! od -c conftest.o | sed ['s/^[0-7]*[ ]*/ / s/\*/./g s/ \\n/*/g --- 935,941 ---- $1 ]EOF if AC_TRY_EVAL(ac_compile); then ! od -tc -Ao conftest.o | sed ['s/^[0-7]*[ ]*/ / s/\*/./g s/ \\n/*/g Diff finished at Fri Jun 7 11:42:05 >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-07 9:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-07 2:46 ralfixx [this message] 2003-05-07 18:26 Dara Hazeghi 2003-05-07 21:22 bangerth
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=20020607094556.583.qmail@sources.redhat.com \ --to=ralfixx@gmx.de \ --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: linkBe 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).