From: "John Eckhart" <jweckhart@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] chost setting for later stages
Date: Mon, 17 Dec 2007 00:28:40 -0500 [thread overview]
Message-ID: <e532144c0712162128v764f6e0dufb892cc6c64befa9@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of my
existing build scripts broke. One of the scripts broke because chost is now
only valid in stage1 and stage2 builds.
This was introduced in svn ver 1237, the ChangeLog reads:
22 Aug 2007; Andrew Gaffney
<agaffney@gentoo.org>modules/generic_stage_target.py,
modules/stage1_target.py
modules/stage2_target.py
'chost' option is only valid in stage 1/2 specs. have catalyst error
otherwise
How do I chose what chost to build later stages? Is this always set by the
stage2 chost? I was never changing it from stage2 on but previously it was
always set in the spec file.
Thanks,
John
[-- Attachment #2: Type: text/html, Size: 864 bytes --]
next reply other threads:[~2007-12-17 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 5:28 John Eckhart [this message]
2007-12-17 5:33 ` [gentoo-catalyst] chost setting for later stages Andrew Gaffney
2007-12-17 5:44 ` John Eckhart
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=e532144c0712162128v764f6e0dufb892cc6c64befa9@mail.gmail.com \
--to=jweckhart@gmail.com \
--cc=gentoo-catalyst@lists.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