public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: jwsacksteder@ramprecision.com
To: gentoo-alpha@gentoo.org
Subject: RE: [gentoo-alpha] glibc blew up...
Date: Tue, 7 Oct 2003 23:23:26 -0400	[thread overview]
Message-ID: <71650A6F73F1D411BE8000805F65E3CB3B367A@SRV-03> (raw)

I did not see anything hard-coded into it. I did not make much of an effort,
though. I just unpacked the stage1 again. I will rebuild and let you know in
the morning. 

I need to point out that the install-guide tells you to add the "~alpha" to
the config file. That most likely needs to be qualified with "use at your
own risk".

-----Original Message-----
From: Aron Griffis [mailto:agriffis@gentoo.org]
Sent: Tuesday, October 07, 2003 10:44 PM
To: gentoo-alpha@gentoo.org
Subject: Re: [gentoo-alpha] glibc blew up...


jwsacksteder@ramprecision.com wrote:	[Tue Oct 07 2003, 09:58:59PM EDT]
> So, is it wise to have the bootstrap.sh build this alternate version?

...which is exactly why I just changed it from KEYWORDS=alpha to ~alpha.

Is this all we need to make bootstrap.sh work, or does it have its own
list of "stable" packages.

The problem here is that this version used to work until gcc caught up
and started flagging the errors.. :-(

Aron

--
gentoo-alpha@gentoo.org mailing list


             reply	other threads:[~2003-10-08  3:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08  3:23 jwsacksteder [this message]
2003-10-08  3:24 ` [gentoo-alpha] glibc blew up Aron Griffis
  -- strict thread matches above, loose matches on Subject: below --
2003-10-08  1:58 jwsacksteder
2003-10-08  2:43 ` Aron Griffis
2003-10-06 11:51 jwsacksteder
2003-10-06 18:17 ` Mathieu MILLET
2003-10-08  1:10 ` Aron Griffis
2003-10-06  4:05 jwsacksteder
2003-10-06  6:07 ` Mathieu MILLET
2003-10-06  7:08   ` Marc Giger
2003-10-08  1:09   ` Aron Griffis

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=71650A6F73F1D411BE8000805F65E3CB3B367A@SRV-03 \
    --to=jwsacksteder@ramprecision.com \
    --cc=gentoo-alpha@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