From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: S390[x] configuration update
Date: Tue, 30 Apr 2002 09:21:00 -0000 [thread overview]
Message-ID: <je7kmpqhsc.fsf@sykes.suse.de> (raw)
In-Reply-To: <3CCD8AD4.2070807@cygnus.com> (Andrew Cagney's message of "Mon, 29 Apr 2002 14:03:00 -0400")
Andrew Cagney <ac131313@cygnus.com> writes:
|> >> Yes, definitly closed.
|> >> I also suspect there is no benefit in pulling it into the 5.2 branch
|> >> once unfrozen. The existing stuff ``works'' - as they say, if it ain't
|> >> broke don't fix it :-)
|> > By ``works'' you mean doesn't build? :) See above; 5.2 won't build on
|> > S/390.
|>
|> My understanding of Andreas's original post is that it updated things to
|> current wisdom rather than fixed a pre-existing build problem.
Sloppy phrasing, sorry. The current wisdom includes that linux-proc.o has
to be linked in.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-04-30 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 15:41 Andreas Schwab
2002-04-27 16:23 ` Daniel Jacobowitz
2002-04-27 17:13 ` Andreas Schwab
2002-04-27 17:25 ` Daniel Jacobowitz
2002-04-27 17:31 ` Andreas Schwab
2002-04-27 17:36 ` Daniel Jacobowitz
2002-04-29 9:18 ` Andrew Cagney
2002-04-29 9:32 ` Daniel Jacobowitz
2002-04-29 11:03 ` Andrew Cagney
2002-04-29 12:06 ` Daniel Jacobowitz
2002-04-29 13:33 ` Andrew Cagney
2002-04-30 9:21 ` Andreas Schwab [this message]
2002-04-30 12:05 ` Andrew Cagney
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=je7kmpqhsc.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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