Bug 142034 – Add CHOSTS Warning to tarball /etc/make.conf

• Status: RESOLVED FIXED
• Product: Gentoo Hosted Projects

[Description Roy Bamford 2006-07-28 13:49:42 UTC]

The /etc/make.conf supplied with stage3-x86-2006.0.tar.bz2 is

# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O2 -mtune=i686 -pipe"
CHOST="i386-pc-linux-gnu"
CXXFLAGS="-O2 -mtune=i686 -pipe"

Can we add a warning to the effect that the CHOST must not be changed and if its not right, the user must fetch the correct tarball.

Should probably go in all the x86 familly stage tarballs

It takes a long time to sort out the resulting mess and I've had four in the last few days.

[Comment 1 Andrew Gaffney (RETIRED) 2006-07-28 13:53:23 UTC]

The 2006.1 tarballs will all have an i686-pc-linux-gnu CHOST, x86 and i686. The x86 tarballs have a glibc-2.3.x and no NPTL while the i686 have glibc-2.4 and nptl.

[Comment 2 Chris Gianelloni (RETIRED) 2006-08-23 10:05:38 UTC]

All of this is done by catalyst, so I'm assigning this there.

[Comment 3 Chris Gianelloni (RETIRED) 2006-11-03 13:19:17 UTC]

I've now added such a warning to catalyst subversion, so it'll show up in the next catalyst version.

[Comment 4 Chris Gianelloni (RETIRED) 2006-12-20 07:18:56 UTC]

OK.  This is FIXED in catalyst, but I'm leaving this open until a new release comes out with the updated information.

[Comment 5 Richard Scott 2007-01-04 07:38:57 UTC]

I've noticed that my warning is added incorrectly to the /etc/make.conf file inside my newly extracted tar ball:

I'm using Catalyst-2.0.1 and there looks to be a type in generic_stage_target.py where you are writing out \m instead of \n.

Example:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -march=i686 -pipe"
CXXFLAGS="${CFLAGS}"
# This should not be changed unless you know exactly what you are doing.  You
# should probably be using a different stage, instead.\mCHOST="i686-pc-linux-gnu"

[Comment 6 Richard Scott 2007-01-04 07:40:51 UTC]

lol, that should have been  "a typo" and not "a type" ;-)

The line in question is:

myf.write("# This should not be changed unless you know exactly what you are doing.  You\n# should probably be using a different stage, instead.\m")

I've not been able to create a diff for that just yet.

[Comment 7 Richard Scott 2007-01-04 07:44:27 UTC]

Created attachment 105387 [details, diff]
diff patch for generic_stage_target.py

[Comment 8 Andrew Gaffney (RETIRED) 2007-01-04 07:46:28 UTC]

This was fixed in SVN about a month ago. There just hasn't been a new release with it.

[Comment 9 Chris Gianelloni (RETIRED) 2007-04-12 19:43:32 UTC]

This has been fixed for some time.  I just forgot to mark it resolved.

[Comment 10 Chris Gianelloni (RETIRED) 2007-04-13 11:57:57 UTC]

Actually, this should stay open until 2007.0 is out.

[Comment 11 Chris Gianelloni (RETIRED) 2007-05-09 20:26:28 UTC]

OK, 2007.0 is out.