Thanks for the clarification. Luckily I wasn't changing it, just (redundantly) specifying it for each run of catalyst. Any chance you could add a line in the generic spec stating exactly that?<br><br><div class="gmail_quote"> On Dec 17, 2007 12:33 AM, Andrew Gaffney <<a href="mailto:agaffney@gentoo.org">agaffney@gentoo.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">John Eckhart wrote:<br>> I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of<br>> my existing build scripts broke. One of the scripts broke because chost<br>> is now only valid in stage1 and stage2 builds. <br>><br>> This was introduced in svn ver 1237, the ChangeLog reads:<br>><br>> 22 Aug 2007; Andrew Gaffney <<a href="mailto:agaffney@gentoo.org">agaffney@gentoo.org</a><br></div>> <mailto:<a href="mailto:agaffney@gentoo.org"> agaffney@gentoo.org</a>>><br><div class="Ih2E3d">><br>> modules/generic_stage_target.py, modules/stage1_target.py<br>> modules/stage2_target.py<br>> 'chost' option is only valid in stage 1/2 specs. have catalyst error <br>> otherwise<br>><br>> How do I chose what chost to build later stages? Is this always set by<br>> the stage2 chost? I was never changing it from stage2 on but previously<br>> it was always set in the spec file. <br><br></div>Setting chost in stage3.spec is a no-op. Catalyst doesn't do anything with it. I<br>added this error so people wouldn't think it was doing something that it wasn't.<br>It's a very bad idea to change CHOST between stage 2 and 3. If you think you <br>have a reason to do it, you're wrong :)<br><br>--<br>Andrew Gaffney <a href="http://dev.gentoo.org/%7Eagaffney/" target="_blank">http://dev.gentoo.org/~agaffney/</a><br>Gentoo Linux Developer Catalyst/Installer + x86 release coordinator <br><font color="#888888">--<br><a href="mailto:gentoo-catalyst@gentoo.org">gentoo-catalyst@gentoo.org</a> mailing list<br><br></font></blockquote></div><br>