public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: shrao@nyx.net
To: gcc-gnats@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: fortran/10686: g77 configure script rejected on MacOS X
Date: Thu, 08 May 2003 16:46:00 -0000 [thread overview]
Message-ID: <20030508164342.23534.qmail@sources.redhat.com> (raw)
>Number: 10686
>Category: fortran
>Synopsis: g77 configure script rejected on MacOS X
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu May 08 16:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Shrisha Rao
>Release: gcc 3.3-prerelease
>Organization:
>Environment:
MacOS X 10.2.6 (Darwin 6.6)
>Description:
If a bootstrap build of gcc is attempted with f77 enabled, then the build fails because of an apparent error in libf2c/libU77/configure.
The error message:
../../../../../gcc_cvs/libf2c/libU77/configure: line 268: syntax error near unexpected token `<<<'
../../../../../gcc_cvs/libf2c/libU77/configure: line 268: `<<<<<<< configure'
configure: error: ../../../../../gcc_cvs/libf2c/libU77/configure failed for libU77
make[1]: *** [configure-target-libf2c] Error 1
make: *** [bootstrap] Error 2
If this line (which is different from the configure file used elsewhere) is commented out, then also the build fails because "libI77: No such file or directory."
This error condition is common to the gcc3.3 prerelease and gcc3.4 from CVS. However, I have a working g77 (but not the source) from the gcc3.4 experimental dated 2002-12-28, so the error is new since then.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-05-08 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 16:46 shrao [this message]
2003-05-08 22:01 toon
2003-05-09 5:06 Shrisha Rao
2003-05-09 6:43 toon
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=20030508164342.23534.qmail@sources.redhat.com \
--to=shrao@nyx.net \
--cc=gcc-gnats@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).