public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Matt Chorman <matt@legalizefreedom.org>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: glibc-2.3.2-r[68] libpthread -> segmentation fault
Date: Tue, 28 Oct 2003 06:35:01 +0200	[thread overview]
Message-ID: <1067315701.9405.29.camel@nosferatu.lan> (raw)
In-Reply-To: <200310272021.57907.matt@legalizefreedom.org>

[-- Attachment #1: Type: text/plain, Size: 619 bytes --]

On Tue, 2003-10-28 at 06:21, Matt Chorman wrote:
> On Monday 27 October 2003 08:09 pm, Martin Schlemmer wrote:
> > On Tue, 2003-10-28 at 01:46, Matt Chorman wrote:
> > > My experience with ntpl has been exaclty like this - even downgrading did
> > > not help. Try recompiling glibc WITHOUT use=ntpl. Your binaries will
> > > (should?) start to work again. Mine did....
> >
> > What CPU is in this box ?
> 
> This is running an AthlonXP 2000+.. Ye Olde AMD chips... ;-)
> 

What gcc/binutils ?


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-28  4:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 13:04 [gentoo-dev] glibc-2.3.2-r[68] libpthread -> segmentation fault Norberto Bensa
2003-10-27 20:00 ` Kumba
2003-10-28  6:19   ` Norberto Bensa
2003-10-28  7:03     ` Kumba
2003-10-28 16:55       ` Norberto Bensa
2003-10-29 17:35         ` Martin Schlemmer
2003-10-30  7:07           ` Norberto Bensa
2003-10-30 18:18             ` Martin Schlemmer
2003-10-31  1:22               ` Norberto Bensa
2003-10-31 17:28                 ` Martin Schlemmer
2003-11-01  6:43                   ` Norberto Bensa
2003-11-01  6:50                     ` Robin H. Johnson
2003-11-01  6:51                       ` Norberto Bensa
2003-11-01 14:40                       ` James Harlow
2003-11-01 15:02                     ` Martin Schlemmer
2003-11-01 16:30                       ` Norberto Bensa
2003-11-01 17:00                         ` Martin Schlemmer
2003-11-01 19:35                         ` Martin Schlemmer
2003-11-01 19:39                           ` Norberto Bensa
2003-11-02 21:45                         ` Martin Schlemmer
2003-11-03  3:31                           ` Norberto Bensa
2003-11-03  4:10                             ` Martin Schlemmer
2003-10-27 20:44 ` [gentoo-dev] " Martin Schlemmer
2003-10-27 21:28   ` Martin Schlemmer
2003-10-27 22:14     ` Andrei Ivanov
2003-10-27 23:46       ` Matt Chorman
2003-10-28  4:09         ` Martin Schlemmer
2003-10-28  4:21           ` Matt Chorman
2003-10-28  4:35             ` Martin Schlemmer [this message]
2003-10-28  5:45               ` Matt Chorman
2003-10-28  9:16                 ` Paul de Vrieze
2003-10-28 17:09                   ` Matt Chorman
2003-10-29 17:35                     ` Martin Schlemmer
2003-10-29 17:31                 ` Martin Schlemmer
2003-10-28  4:08       ` Martin Schlemmer
2003-10-28  6:06   ` Norberto Bensa

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=1067315701.9405.29.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=matt@legalizefreedom.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