From: Jakub Jelinek <jakub@redhat.com>
To: Matthew H Bemis <bemis@iol.unh.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: ios.lo complilation promblems
Date: Tue, 20 Nov 2001 16:50:00 -0000 [thread overview]
Message-ID: <20011128160512.L572@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <3C054756.E391CF77@iol.unh.edu>; from Matthew H Bemis on Wed, Nov 28, 2001 at 03:21:42PM -0500
On Wed, Nov 28, 2001 at 03:21:42PM -0500, Matthew H Bemis wrote:
> after mentioning that gcc.o on the alphas was not being created in
> dozens of builds the problem was solved immediately. thank you. however
> a new problem arose the next day in alomost all the same builds
> there is an error building ios.lo
> has anyone seen this problem ?
See http://gcc.gnu.org/ml/gcc/2001-11/msg01425.html
Jakub
WARNING: multiple messages have this Message-ID
From: Jakub Jelinek <jakub@redhat.com>
To: Matthew H Bemis <bemis@iol.unh.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: ios.lo complilation promblems
Date: Wed, 28 Nov 2001 07:01:00 -0000 [thread overview]
Message-ID: <20011128160512.L572@sunsite.ms.mff.cuni.cz> (raw)
Message-ID: <20011128070100.NpGV3QgNrUAmUzX-65lwBYa5jKqkz9MYb5VjDx_EC7s@z> (raw)
In-Reply-To: <3C054756.E391CF77@iol.unh.edu>
On Wed, Nov 28, 2001 at 03:21:42PM -0500, Matthew H Bemis wrote:
> after mentioning that gcc.o on the alphas was not being created in
> dozens of builds the problem was solved immediately. thank you. however
> a new problem arose the next day in alomost all the same builds
> there is an error building ios.lo
> has anyone seen this problem ?
See http://gcc.gnu.org/ml/gcc/2001-11/msg01425.html
Jakub
next prev parent reply other threads:[~2001-11-28 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 16:21 Matthew H Bemis
2001-11-20 16:50 ` Jakub Jelinek [this message]
2001-11-28 7:01 ` Jakub Jelinek
2001-11-28 6:16 ` Matthew H Bemis
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=20011128160512.L572@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=bemis@iol.unh.edu \
--cc=gcc@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).