| 1 |
On Wed, 2005-12-14 at 14:35 -0600, Mikey wrote: |
| 2 |
> Well, I will have to argue with you on this point. It is important to me |
| 3 |
> that the toolchain is compiled against itself. Catching weird toolchain |
| 4 |
> errors on down the road in a production environment is not my idea of fun. |
| 5 |
> I suppose I will repeat the use of the word anal again... |
| 6 |
|
| 7 |
That is what the later stages are there for, to recompile the toolchain. |
| 8 |
Argue all you want, this is fact. |
| 9 |
|
| 10 |
> > You cannot set USE flags for your lower stages. You will need to create |
| 11 |
> > a profile. The USE flags *must* match what is in the profile. |
| 12 |
> |
| 13 |
> Lower stages being 1-3? During which stage are USE flags intended to be |
| 14 |
> used with catalyst? |
| 15 |
|
| 16 |
Correct. Only stage4 is safe for changing USE flags. |
| 17 |
|
| 18 |
> > Well, stage2/use is invalid and ignored. Also, stage3/use is invalid |
| 19 |
> > and ignored. You do not change the USE in stages 1 through 3. Period. |
| 20 |
> > To make changes to these stages, you need to make a new profile with |
| 21 |
> > your changes. This could either be done via editing your portage tree |
| 22 |
> > before making the snapshot, or as portdir_overlay in each spec file. No |
| 23 |
> > hand-editing is ever required. |
| 24 |
> |
| 25 |
> What about stage4? If I want to build snapshots with nptl, userlocales, and |
| 26 |
> -nls, for example, I have to use a stage4? |
| 27 |
|
| 28 |
No, you do what I said and make a profile. I am honestly getting a |
| 29 |
little frustrated with having to repeat this. With a proper profile, |
| 30 |
you can have a stage2/stage3 with nptl. It isn't possible to have a |
| 31 |
stage1 with nptl on x86, since nptl isn't ported to i386 CHOST. Look at |
| 32 |
default-linux/x86/dev/2006.0 as a good example, as we're using nptl by |
| 33 |
default there. |
| 34 |
|
| 35 |
> On the bug I submitted yesterday. I just completed a stage1 -> stage2 -> |
| 36 |
> stage3 -> stage1 cycle, using no environment script, no USE flags, no |
| 37 |
> optimizations, the same thing happens. It attempts to emerge glibc before |
| 38 |
> linux-headers, glibc looks for the headers in stage1root, they don't exist, |
| 39 |
> so it bombs.... |
| 40 |
|
| 41 |
I have no way of guaranteeing that the stages you made are good. Please |
| 42 |
follow the instructions I sent in my last email for your builds, as |
| 43 |
there is no way for me to verify anything other than the recommended |
| 44 |
procedures. Use a known good stage3 tarball as a stage1 seed. At that |
| 45 |
point, you don't need to rebuild stage1. Basically, to duplicate what |
| 46 |
you have done you would need: stage3 -> stage1 -> stage2 -> stage3 |
| 47 |
(remember that the stage3 *must* be generic to build a stage1) -> |
| 48 |
stage1. |
| 49 |
|
| 50 |
Unfortunately, in many cases, catalyst is a "fix it yourself" |
| 51 |
application. If it doesn't break our release-building, it is reduced in |
| 52 |
priority, as catalyst is first and foremost our release-building tool. |
| 53 |
|
| 54 |
Patches are always welcome, however. |
| 55 |
|
| 56 |
-- |
| 57 |
Chris Gianelloni |
| 58 |
Release Engineering - Strategic Lead |
| 59 |
x86 Architecture Team |
| 60 |
Games - Developer |
| 61 |
Gentoo Linux |
Archives