| 1 |
On 17/02/06, Karl Zander <gentoolist@××××××××××××.com> wrote: |
| 2 |
> Doing a new install. I got to the part about editing make.conf. I used a |
| 3 |
> stage3 tarball on x86 from the 2005.1-r1 release. |
| 4 |
> |
| 5 |
> /code |
| 6 |
> make.conf |
| 7 |
> CFLAGS="-0s -mcpu=i686 -pipe" |
| 8 |
> CHOST="i386-pc-linux-gnu" |
| 9 |
> CXXFLAGS="${CFLAGS}" |
| 10 |
> /end code |
| 11 |
> |
| 12 |
> I am not sure why CHOST="i386-pc-linux-gnu". Even make.conf.example says |
| 13 |
> |
| 14 |
> "All modern systems (even Athalons) should use "i686-pc-linux-gnu" |
| 15 |
|
| 16 |
Read that as "are capable of using" rather than "should use" and it |
| 17 |
makes more sense. |
| 18 |
|
| 19 |
> |
| 20 |
> Do I have the right tarball? I got the tarball from the cd, not from the |
| 21 |
|
| 22 |
Yes, you do. The 2005.1-r1 LiveCD only ships with a generic x86 stage3 |
| 23 |
tarball. There are two good reasons for this: |
| 24 |
|
| 25 |
1) It simplifies the job of release engineering considerably. |
| 26 |
|
| 27 |
2) The most broadly distributed packages CD featured binary packages |
| 28 |
which are (and always have been) built in the same manner - that is, |
| 29 |
with CHOST="i386-pc-linux-gnu" and -mcpu=i686. Thus you get packages |
| 30 |
which are optimised for the i686 family of processors in general but |
| 31 |
which will run on >=i386 processor. People were all too often mixing |
| 32 |
the wrong stageball with said packages and running into compilation |
| 33 |
issues further down the line. |
| 34 |
|
| 35 |
Here are three plausible solutions: |
| 36 |
|
| 37 |
Solution 1) Accept it and go with the flow. You can still set |
| 38 |
CFLAGS/CXXFLAGS any which way you like ("-march=pentium4" for |
| 39 |
example). The most obvious drawback when using this stageball is that |
| 40 |
you can't build glibc with NPTL support ... assuming that matters to |
| 41 |
you. It really isn't a big deal apart from that. |
| 42 |
|
| 43 |
Solution 2) Don't use the supplied stageball and instead download |
| 44 |
another one from a mirror using wget or whatever. The most "optimal" |
| 45 |
choice for you is: |
| 46 |
releases/x86/2005.1-r1/stages/pentium4/stage3-pentium4-2005.1-r1.tar.bz2 |
| 47 |
|
| 48 |
Solution 3) If you're very experienced with gentoo installation |
| 49 |
procedure then you could perform a stage1 type installation (i.e. |
| 50 |
bootstrap.sh to get to stage2, then emerge -e system to get to |
| 51 |
stage3). Yes, you can do this even if you begin with a stage3 tarball. |
| 52 |
|
| 53 |
Cheers, |
| 54 |
|
| 55 |
--Kerin |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-server@g.o mailing list |
Archives