From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Date: Mon Feb 5 16:02:01 2001 [thread overview]
Message-ID: <20010205160141.B13748@cvs.gentoo.org> (raw)
In-Reply-To: <3A7F27BF.43961400@gottinger.de>; from 320095285153-0001@t-online.de on Mon, Feb 05, 2001 at 11:22:55PM +0100
On Mon, Feb 05, 2001 at 11:22:55PM +0100, Achim Gottinger wrote:
> >
> > Oh, and I ran make check on the glibc build again, and it went fine this
> > time... The problem was the one you mentioned before. I wan't doing
> > anything other than compiling glibc, though, so I'm not sure what cause
> > the problem.
>
> This is definately a kernel/reiserfs problem. Take a look at the reiserfs
> mailinglist and
> watch out for low latency relatet mails.
> What kerenle did you use 2.4.1-pre8 or 2.4.0-ac11 ?
>
> achim~
>
I was using 2.4.1-pre8.
Pete
next prev parent reply other threads:[~2001-02-05 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 14:43 [gentoo-dev] allowing configuration of builds? Pete Gavin
2001-02-05 15:07 ` Pete Gavin
2001-02-05 15:31 ` Achim Gottinger
2001-02-05 15:37 ` Pete Gavin
2001-02-05 15:49 ` Achim Gottinger
2001-02-05 16:02 ` Pete Gavin [this message]
2001-02-05 16:33 ` Achim Gottinger
2001-02-05 16:39 ` Pete Gavin
2001-02-05 18:05 ` drobbins
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=20010205160141.B13748@cvs.gentoo.org \
--to=pete@gentoo.org \
--cc=gentoo-dev@gentoo.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