From: Ben Collins <bcollins@debian.org>
To: Randolph Chung <tausq@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Fix for hppa-linux ld.so with newer binutils
Date: Wed, 24 Oct 2001 21:12:06 -0400 [thread overview]
Message-ID: <20011024211206.Y10952@visi.net> (raw)
In-Reply-To: <20011024175642.X537@tausq.org>
On Wed, Oct 24, 2001 at 05:56:43PM -0700, Randolph Chung wrote:
> Ben,
>
> > Not to mention I am getting random segv's in the rest of the toolchain.
> > I went back to a UP kernel suspecting it to be the cause. Now I'm
> > getting a segv during the package builds due to a segv in the strip
> > program (that may be a binutils bug).
> >
> > So, back to square one. I don't have time tonight to start looking at
> > this, so I'll start on it tomorrow.
> >
> > BTW, most of the iconv/locales tests fail in glibc on parisc.
>
> do you have a build log? if so can you put it on, say, auric?
The build finished without error, so it's of little use. The test suite
output is just a lot og Error 139's, so it too isn't much help.
> also please show dpkg -s output for binutils and gcc-3.0
binutils 2.11.92.0.10-1
gcc-3.0 3.0.2-0pre010922
I'm going to upgrade and try again.
> we seem to be getting some random segvs on A500's. James sees them a lot
> on the hppa buildd (sarti). I have a feeling the toolchain might not be
> at fault in this case.
Agreed. In fact, the machine locked up twice while doing a "debian/rules
clean", which is obviously not a toolchain problem :)
> if you'd like please post the source and I can try to build it here. i'm
> building 2.2.4-3 with the newest tool bits at the moment. basic things
> seem to be ok, but it'll take an hour or more for it to finish.
Will be uploading it later tonight. I have 5 other archs done, so I am
going to upload all of that.
--
.----------=======-=-======-=========-----------=====------------=-=-----.
/ Ben Collins -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
next prev parent reply other threads:[~2001-10-25 1:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 7:39 [parisc-linux] Fix for hppa-linux ld.so with newer binutils Alan Modra
2001-10-20 13:54 ` [parisc-linux] " Ben Collins
2001-10-20 14:34 ` Alan Modra
2001-10-20 15:01 ` Ben Collins
2001-10-24 23:51 ` Ben Collins
2001-10-25 0:56 ` Randolph Chung
2001-10-25 1:12 ` Ben Collins [this message]
2001-10-25 15:07 ` Matthew Wilcox
2001-10-25 15:50 ` Ben Collins
2001-10-22 3:44 ` Alan Modra
2001-10-20 18:01 ` [parisc-linux] " Carlos O'Donell Jr.
2001-10-21 11:20 ` Alan Modra
2001-10-22 14:05 ` [parisc-linux] " Alan Modra
2001-10-22 16:04 ` Carlos O'Donell Jr.
2001-10-22 16:11 ` Alan Modra
2001-10-23 1:31 ` Ben Collins
2001-10-23 1:59 ` Randolph Chung
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=20011024211206.Y10952@visi.net \
--to=bcollins@debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.