From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: basic-improvements merged to trunk
Date: Mon, 16 Dec 2002 14:38:00 -0000 [thread overview]
Message-ID: <3DFE53DB.7050909@moene.indiv.nluug.nl> (raw)
In-Reply-To: <874r9dyg4b.fsf@egil.codesourcery.com>
Zack Weinberg wrote:
> I've checked in the merge of basic-improvements to the trunk. You'll
> note that version.c has had "3.3" changed to "3.4" now, too.
Got that (at 18:35 UTC).
Unfortunately, it doesn't build on my system (powerpc-unknown-linux-gnu)
- probably not your fault. The final link of the (shared) libgcj fails
with:
ld terminated with signal 9 [killed], core dumped.
Probably this 256 Mbyte Titanium is too small to build it.
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
next prev parent reply other threads:[~2002-12-16 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 10:49 Zack Weinberg
2002-12-16 14:38 ` Toon Moene [this message]
2002-12-27 0:51 ` PATCH for " Gerald Pfeifer
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=3DFE53DB.7050909@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=gcc@gcc.gnu.org \
--cc=zack@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).