From: "Stephen P. Becker" <geoman@gentoo.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Bryan Althouse <bryan.althouse@3phoenix.com>,
"'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread
Date: Fri, 01 Jul 2005 13:15:26 -0400 [thread overview]
Message-ID: <42C57A2E.4070702@gentoo.org> (raw)
In-Reply-To: <20050701170258.GA22405@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Fri, Jul 01, 2005 at 10:56:17AM -0400, Stephen P. Becker wrote:
>
>>The segfault with kernel oops that I can't get around occurs while
>>glib's configure script is checking for libpthread. Specifically, it
>>links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against
>>libpthread and then runs it.
>
>
> If that oopses, your famed emerge testing hasn't run any threaded
> programs, my friend :-)
What do you mean by "famed" emerge testing? In any case, that is what I
am in the process of doing (testing). This userland I am working with
is in no way an official Gentoo install. :) At some point in the
future, we will probably make official n32 install stages available to
the general users, after we work all the bugs out...this just happens to
be one of those bugs.
> Could be kernel, could be library, could be both.
Well, since you say that glibc 2.3.5 probably isn't up to par for
mips64, I'll see if I can get cvs HEAD going in a chroot and see if that
fixes the problem.
> Must be at least kernel because the kernel should never oops.
Agreed.
-Steve
next prev parent reply other threads:[~2005-07-01 17:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 17:33 Seg fault when compiled with -mabi=64 and -lpthread Bryan Althouse
2005-06-30 19:08 ` Stephen P. Becker
2005-06-30 19:31 ` Bryan Althouse
2005-06-30 20:21 ` Ralf Baechle
2005-06-30 21:03 ` Daniel Jacobowitz
2005-06-30 22:09 ` Stephen P. Becker
2005-07-01 3:51 ` Daniel Jacobowitz
2005-07-01 4:44 ` Kumba
2005-07-01 8:49 ` Maciej W. Rozycki
2005-07-01 13:39 ` Daniel Jacobowitz
2005-07-01 14:10 ` Maciej W. Rozycki
2005-07-01 14:46 ` Daniel Jacobowitz
2005-07-01 15:04 ` Maciej W. Rozycki
2005-07-01 14:56 ` Stephen P. Becker
2005-07-01 15:22 ` Maciej W. Rozycki
2005-07-01 16:39 ` Stephen P. Becker
2005-07-01 17:02 ` Daniel Jacobowitz
2005-07-01 17:15 ` Stephen P. Becker [this message]
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 14:54 ` sjhill
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 15:29 ` Maciej W. Rozycki
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=42C57A2E.4070702@gentoo.org \
--to=geoman@gentoo.org \
--cc=bryan.althouse@3phoenix.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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