public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: Craig Burley <burley@gnu.org>, drees@oto.dyn.ml.org
Cc: egcs@cygnus.com
Subject: libf2c build problems? Was: Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental) testsuite on i586-pc-linux-gnulibc1
Date: Sun, 27 Sep 1998 20:41:00 -0000	[thread overview]
Message-ID: <19980927224057.A15624@dgii.com> (raw)
In-Reply-To: <199809271850.OAA00646@melange.gnu.org>

Craig Burley wrote:

> On my Alpha (RH 5.0 Linux), this snapshot didn't even bother building
> some libraries, such as libf2c.  I haven't had time to investigate

Ewww. Bummer.

I just tried a build on a RH5.1 Linux/x86 version on a version patched
up from who-knows-what snapshot of the past and it died during the build
of libf2c.  I did a 'make clean-target-libf2c' followed by a 'make
all-target-libf2c' and it passed.  I was unable to recreate the failure,
so I'm going to assume (?) that there was some stamp file or something
else left over that confused things when that directory got multilibbed
last week.   A 'make check-target-libf2c' seems to work OK, so whatever
the original failure was (it's not in my scrollback) seems to be gone.

If you and the original poster could try this same "fix", that might
be an easy out...

> I suspect the snapshot includes a misapplied patch or two that
> makes it DOA, or nearly so...but if nobody speaks up with
> an "aha!", I'll try and look into it later this week.  (By "misapplied"
> I include partially applied patches as well.)

If it simplifies things, you can blame me for mangling the Makefiles
until a more clearly identifiable culprit steps forward. :-)



      parent reply	other threads:[~1998-09-27 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-26 17:40 Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)testsuite " David Rees
1998-09-27 11:51 ` Craig Burley
1998-09-27 17:34   ` Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental) H.J. Lu
1998-09-28  3:19     ` Jeffrey A Law
1998-09-29 10:10       ` Manfred Hollstein
1998-09-29 13:08         ` H.J. Lu
1998-09-29 22:26           ` Jeffrey A Law
1998-09-27 20:41   ` Robert Lipe [this message]

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=19980927224057.A15624@dgii.com \
    --to=robertl@dgii.com \
    --cc=burley@gnu.org \
    --cc=drees@oto.dyn.ml.org \
    --cc=egcs@cygnus.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).