From: "Randolph Chung" <randolph@tausq.org>
To: "Matthew Wilcox" <matthew@wil.cx>
Cc: "Alan Modra" <alan@linuxcare.com.au>,
"Matt Taggart" <taggart@fc.hp.com>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] segfaults with new binutils
Date: Sun, 11 Mar 2001 09:49:21 -0700 [thread overview]
Message-ID: <20010311094921.V18113@tausq.org> (raw)
In-Reply-To: <20010311125007.A21169@parcelfarce.linux.theplanet.co.uk>; from matthew@wil.cx on Sun, Mar 11, 2001 at 12:50:07PM +0000
In reference to a message from Matthew Wilcox, dated Mar 11:
> On Sun, Mar 11, 2001 at 02:31:26PM +1100, Alan Modra wrote:
> > Incidentally, I'm not actively updating binutils CVS on pehc any longer.
> > If you want the latest code, get it from sourceware.cygnus.com CVS, either
> > the 2.11 branch, or trunk for bleeding edge code. At the moment, there's
> > no particular reason to not use pehc for hppa-linux binutils, as it's not
> > too far behind, but that will no doubt change in the future...
>
> Is there any point in keeping this CVS module then? Shall we just delete it?
i'm not sure what taggart did to build the deb on pehc, but i've been
building from Debian's source package. If we are at a point where we can
rely on the Debian maintainer to get the sources from upstream that we
need I think we'll be much better off.
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-03-11 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 16:39 [parisc-linux] segfaults with new binutils Randolph Chung
2001-03-10 17:21 ` Randolph Chung
2001-03-11 2:55 ` Alan Modra
2001-03-11 3:31 ` Alan Modra
2001-03-11 12:50 ` Matthew Wilcox
2001-03-11 16:49 ` Randolph Chung [this message]
2001-03-11 23:44 ` Alan Modra
2001-03-11 16:55 ` Randolph Chung
2001-03-11 23:41 ` Alan Modra
2001-03-12 4:31 ` Jes Sorensen
2001-03-12 4:55 ` Alan Modra
2001-03-12 5:04 ` Randolph Chung
[not found] <Pine.LNX.4.21.0103141045320.27636-100000@front.linuxcare.com.au>
2001-03-14 0:22 ` Alan Modra
2001-03-14 4:24 ` Alan Modra
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=20010311094921.V18113@tausq.org \
--to=randolph@tausq.org \
--cc=alan@linuxcare.com.au \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.org \
--cc=taggart@fc.hp.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