From: David Cummings <real.psyence@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: o32 glibc-2.3.5
Date: Wed, 27 Jul 2005 09:55:58 -0400 [thread overview]
Message-ID: <dbce93020507270655d4a1c6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0507271059110.13819@blysk.ds.pg.gda.pl>
On 7/27/05, Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Tue, 26 Jul 2005, David Cummings wrote:
>
> > greatly appreciate it. I've been looking in glibc's bugzilla but can't
> > find the right bug. Thanks!
>
> #758
>
> Maciej
>
Alright, thanks. I had found that, but it didn't seem to apply to the
problem with socket, as that had already been applied when the socket
happened. I'm also now having a problem with n32 which is similar if
not the same as the one Rolf had not too long ago. Something about a
__fork_block not being found. Anyplace else I should look? Thanks,
-Dave
--
The way that can be named is not the Way.
next prev parent reply other threads:[~2005-07-27 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 19:28 o32 glibc-2.3.5 David Cummings
2005-07-27 9:59 ` Maciej W. Rozycki
2005-07-27 13:55 ` David Cummings [this message]
2005-07-27 14:44 ` 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=dbce93020507270655d4a1c6@mail.gmail.com \
--to=real.psyence@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@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 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.