| View previous topic :: View next topic |
| Author |
Message |
96140
Retired Dev
Joined: 23 Jan 2005
Posts: 1324
|
 Posted: Sat Apr 02, 2005 7:50 pm Post subject: |
 |
|
| Mmmf. Sorry for the delay, but I've had severe problems getting XP to burn the 2005.0 liveCD .iso to a disc. Still haven't resolved that, but it should be fixed shortly; no worries there. It's just as well, I suppose, since now the regular Pentium stage really needs testing, right? I don't mind putting that on my system and working with it for a week or whatever; I'd prefer to do the P3 again, but from what I've been reading there might be a serious problem with the Pentium stage, so if that's what needs testing, I can use that tarball. |
|
| Back to top |
|
 |
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 8:13 pm Post subject: |
|
|
| Sith_Happens wrote: | | Each time I start on a new stage, I start in a fresh directory, with a fresh stage 3, whatever stage I would normally use to install on that particular system. |
in saying that, do you mean that you're changing which stage 3 tarballs you have been using to perform the install, every time you create a new stage? for example, you use:
/releases/x86/2005.0/stages/x86/stage3-x86-2005.0.tar.bz2 to make the jackass pentium tarball
/releases/x86/2005.0/stages/x86/stage3-i686-2005.0.tar.bz2 to make the packass pentium2 tarball
/releases/x86/2005.0/stages/x86/stage3-pentium3-2005.0.tar.bz2 to make the jackass pentium3 tarball
/releases/x86/2005.0/stages/x86/stage3-pentium4-2005.0.tar.bz2 to make the jackass pentium4 tarball
or are you just installing the pentium4 stage on your box, and then changing the CHOST and march= and mtune= statements in make conf to build the systems for each stage, and then rebuilding?
| Quote: | | I made a mistake in my post earlier, the x86 stage 3's are built with -mcpu=686, so it would still work on all x86's, but would have some optimization. Makes sense to me now. |
yes, it makes sense to enable optimizations for newer cpus, but not break compatability with older cpus. that's a very good choice, actually, if the devs are planning on having people use the x86 tarballs on every platform. i would have expected -mcpu=i686 to be put in the i686/P2 tarball, and mcpu=pentium to have been put in the x86 tarball. but i guess they wanted to optimize x86 for the entire x86 spectrum.
| Quote: | About the baselayout ebuild, it's just one of those things were somebody screws up the ebuild, finds the problem, and fixes it, but in the mean time 200 people have sync'ed and found the problem (or maybe just me  ). The problem was the patch was missing the file name it was supposed to patch, pretty basic. If you synced in the wee-hours of april 1st you should be ok, it was only on the snapshot I made from around 4 pm EST on the 31st that had the problem. I guess you'll find out when you hit the baselayout ebuild. You could also sync in the middle, and fix the ebuild before it gets to it. |
i had the gcc-config update in my build, so if that serves as a marker for having the baselayout fix, i may have dodged the bullet. even so, i decided to cheat -- because i knew that glibc would take a long time to build, i F2'd into another console and emerge --sync'd while glibc was compiling. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 8:37 pm Post subject: |
|
|
| Sith_Happens wrote: | | Sith_Happens wrote: | | Each time I start on a new stage, I start in a fresh directory, with a fresh stage 3, whatever stage I would normally use to install on that particular system. I made a mistake in my post earlier, the x86 stage 3's are built with -mcpu=686, so it would still work on all x86's, but would have some optimization. Makes sense to me now. About the baselayout ebuild, it's just one of those things were somebody screws up the ebuild, finds the problem, and fixes it, but in the mean time 200 people have sync'ed and found the problem (or maybe just me ). The problem was the patch was missing the file name it was supposed to patch, pretty basic. If you synced in the wee-hours of april 1st you should be ok, it was only on the snapshot I made from around 4 pm EST on the 31st that had the problem. I guess you'll find out when you hit the baselayout ebuild. You could also sync in the middle, and fix the ebuild before it gets to it. The latest snapshot also contains a new version of gcc-config, as well as coreutils, so the newer jackass tarballs will contain those as well. |
I hate when I hit quote instead of edit.  |
postcount whore.  |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sat Apr 02, 2005 8:42 pm Post subject: |
|
|
Here are the tarballs I used for each of the Jackass Tarballs:
generic x86 --> Jackass Pentium
generic x86 --> Jackass Pentium 2
Pentium 3 --> Jackass Pentium 3
i686 --> Pentium 4 (I know there is a pentium 4 stage, but since I'm recompiling everything, it's not that big of a deal).
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 8:54 pm Post subject: |
|
|
| great. that is what i was hoping you were doing. that removes one possible source of problems from the list of possibilities, so i'm hoping that the baselayout error is what had caused the problem. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 9:11 pm Post subject: |
|
|
| Did somebody say that they had gmail accounts to give away? i think i need one for a mailing list subscription. thx. |
|
| Back to top |
|
|
obsidianblackhawk
Apprentice
Joined: 28 Mar 2005
Posts: 237
Location: Sac Town USA
|
| Posted: Sat Apr 02, 2005 9:52 pm Post subject: |
|
|
Okay so the pentium stage is ready for testing? Shall i get started?
Also quick question. What prog should I use for a yahoo instant messenger client ? |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 10:43 pm Post subject: |
|
|
yes, go ahead and test the new pentium stage.
ryan, just to make sure things are consistent from stageball to stageball, do you think we should ultimately build all of them using the same portage snapshot? |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sat Apr 02, 2005 10:44 pm Post subject: |
|
|
| Sith_Happens wrote: | Here are the tarballs I used for each of the Jackass Tarballs:
generic x86 --> Jackass Pentium
generic x86 --> Jackass Pentium 2
Pentium 3 --> Jackass Pentium 3
i686 --> Pentium 4 (I know there is a pentium 4 stage, but since I'm recompiling everything, it's not that big of a deal). |
is there any reason that you didn't choose to start with i686 for the pentium2 ball? just wondering, as you used it for P4. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 1:38 am Post subject: |
|
|
<b>Pentium Stage Update</b>
while Ryan has been away for the weekend, i have rebuilt the PC that i had been using for testing the pentium tarball. this is essentially what i did:
| Code: |
# emerge --sync
# emerge gcc-config glibc binutils gcc
# emerge baselayout (picked up the new ebuild)
# tcupdate.sh --exclude=system -ew world --keeplog
|
the final command is a bit of a cheat at performing emerge -e world -- i used minderaser's script. the command as written, will perform an emerge -e world with the exception of skipping all of the system components.
the good news is that the "rsyncing across the lan problem" is gone. 
the bad news is that i'm not exactly sure what constituted the fix. 
it could have been as simple as fixing the baselayout ebuild (which would have made my entire rebuild unnecessary) or it could have been something else that was b0rked in the ebuild.
ryan, since you've looked at that ebuild/patch, was there anything in there that would fubar rsyncing across a LAN? i'd really prefer not to have to wipe this system again and do another reinstall on an old pc if you're confident that the update to baselayout is what fixed the problem. |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sun Apr 03, 2005 2:02 am Post subject: |
|
|
Your one step ahead of me Bob , I had been thinking about freezing the stages at a particular portage snapshot. The answer I came up with is we will wait until we find a snapshot with ebuilds free of bugs. Once we have stages that are stable, I'll freeze the portage tree I build them with. I think that the April Fools snapshot is stable enough (since the baselayout error is fixed) so I'll freeze all future jackass stages with that snapshot. On the rsync problem, I didn't see anything that would cause that problem in the baselayout patch problem. However, it could have easially been linked to a seperate problem in the 3-30-05 snapshot. After the testing of the pentium-rc1 stage is complete, I'll move on to building the rc2 stages. So far, the changes between rc1 and rc2 will be as follows:
1) All the config files will be updated with some kind of copyright header, one which does not violate the Gentoo foundations own copyright.
2) gcc 3.3.5 will be unmerged before tarring the stage
3) All stages will be built with the April Fools snapshot.
4) I'll be more careful when it comes to blanking certain files. 
Thats all I can think of at the moment, but if somebody else thinks of something, be sure to remind me sometime this weekend, because I plan on building the rc2 stages next week.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
obsidianblackhawk
Apprentice
Joined: 28 Mar 2005
Posts: 237
Location: Sac Town USA
|
| Posted: Sun Apr 03, 2005 2:05 am Post subject: |
|
|
| Okay just got done installing the pentium stage with out problems. are there any particular packages you guys would like me to build for testing the install? |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sun Apr 03, 2005 2:12 am Post subject: |
|
|
| obsidianblackhawk wrote: | | Okay just got done installing the pentium stage with out problems. are there any particular packages you guys would like me to build for testing the install? |
We'll, try rsyncing (although the Bob's problem only occured with local rsyncing). Try compiling xorg-x11 and kde, and run it for a few days. Those are some pretty big compiles, and KDE has a ton of other packages that go with it, be sure to test as many as you can.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
obsidianblackhawk
Apprentice
Joined: 28 Mar 2005
Posts: 237
Location: Sac Town USA
|
| Posted: Sun Apr 03, 2005 2:13 am Post subject: |
|
|
| Sith_Happens wrote: | | obsidianblackhawk wrote: | | Okay just got done installing the pentium stage with out problems. are there any particular packages you guys would like me to build for testing the install? |
We'll, try rsyncing (although the Bob's problem only occured with local rsyncing). Try compiling xorg-x11 and kde, and run it for a few days. Those are some pretty big compiles, and KDE has a ton of other packages that go with it, be sure to test as many as you can. |
Will do. I'll get started on those right now |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 2:33 am Post subject: |
|
|
| Sith_Happens wrote: | | Your one step ahead of me Bob , I had been thinking about freezing the stages at a particular portage snapshot. |
great minds think alike!
| Quote: | So far, the changes between rc1 and rc2 will be as follows:
1) All the config files will be updated with some kind of copyright header, one which does not violate the Gentoo foundations own copyright.
2) gcc 3.3.5 will be unmerged before tarring the stage
3) All stages will be built with the April Fools snapshot.
4) I'll be more careful when it comes to blanking certain files. |
1. I will get updated headers sent to you via email, either as file attachments, or as text that you can cut and paste. we should also consider the muted verison of monkey's excellent portage patch.
2a. I've tried removing GCC 3.3.5 from the rebuilt jackass-pentium system, and i can't get gcc-config 1 to change the default gcc compiler from 3.4.3.20050110 to 3.3.5. can anyone explain this?
2b. I've tried unmerging GCC 3.3.5, which is a bit of a PITA since I didn't know the exact name of the ebuild. for anyone who's wondering, the ebuild is 3.3.5-r1, and if you want to unmerge the old GCC from your system, the correct command should be:
| Code: | | emerge -C =sys-devel/gcc-3.3.5-r1 |
4. what was the problem you had with blanking files? IIRC, you simply untarred the stages and rebult them while they were in a chroot, you never actually booted into them, so i wouldn't think you would have problems with existing system password files, etc.
5. have you looked at the jackass-2005.0-instruction-manual-rc01-20050401.pdf yet? can you post it to the server from where you are? |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 4:45 am Post subject: |
|
|
wow. i've just been bodyslammed!
so tell me ryan, what's your feeling on this? for the -rc2 builds, should we add another emerge -e system to the jackass build, or should we run with it as it is?
although it probably won't kill anything not to do change the way that we do the build, it certainly can't hurt to add anther emerge -e system, and i'd much prefer taking the time to do one more pass in compiling to negate the possibility of retaining a static library that's been compiled into the toolkit. i really want to make sure that we get the toolkit right, so i would be in favor of another layer of redundancy by adding a second emerge -e system.
as i had mentioned in my post to moocha, i have re-emerged updates of glibc and gcc 5 or 6 times now. each time that i do a new toolkit build, its followed by an emerge -e system and a pair of emerge -e worlds. there's absolutely no doubt in my mind that one reason that i've never run into the problems that moocha is talking about is becuase i've recompiled so damned many times that all traces of GCC 334 and 335 (even static libs) have long since vanished from my system.
if this is the reason that i have never fallen subject to the problems with GCC 343 that so many people on the forum complain about, then we should certainly include another redundant pass through the system when creating the distfiles.
hiel, this would effect your script too... |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sun Apr 03, 2005 5:27 am Post subject: |
|
|
| Bob P wrote: | | 1. I will get updated headers sent to you via email, either as file attachments, or as text that you can cut and paste. we should also consider the muted verison of monkey's excellent portage patch. |
Just send me those headers sometime tomorrow or Monday, and I'll add them to the config files in rc2. Thanks for reminding me about monkey89's patch. What I'll do is compile portage with the patch, but not include the contents of the portage overlay in the stage. That way somebody can remove the line by simply recompiling portage. | Bob P wrote: | | 2a. I've tried removing GCC 3.3.5 from the rebuilt jackass-pentium system, and i can't get gcc-config 1 to change the default gcc compiler from 3.4.3.20050110 to 3.3.5. Confused can anyone explain this? |
This sounds simaler to the problem I was having earlier, but backwards. Why do you want to do this though? I'm a little confused. Once you've switched to gcc 3.4.3, why not just unmerge gcc 3.3.5? | Bob P wrote: | | 2b. I've tried unmerging GCC 3.3.5, which is a bit of a PITA since I didn't know the exact name of the ebuild. |
The best command for this is emerge -P gcc. This will automatically remove all but the latest version of gcc. | Bob P wrote: | | 5. have you looked at the jackass-2005.0-instruction-manual-rc01-20050401.pdf yet? can you post it to the server from where you are? |
I haven't had a chance to look at it yet, but I'll do that right now. I can also post it on the server from here, or if I don't do it tonight or tomorrow morning, then I'll do it tomorrow afternoon when I get back to school. Either way it will be up by the time I post the rc2 tarballs, which hopefully will be the final pre-release tarballs. | Bob P wrote: | | so tell me ryan, what's your feeling on this? |
I think that's a great idea. When I build the rc2 stages, I'll recompile the hell out of the entire system. Just so you know, I found that emerge -e system and emerge -e world are one in the same on a stage 3 tarball.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sun Apr 03, 2005 6:36 am Post subject: |
|
|
Hey Bob, I like the documentation, did you make those cover ASCII art using figlet?  There's a typo though, "We Can Rebuilt it". There are some more settings in the make.conf file shown in the documentation than I have currently been adding to the jackass make.conf's. Do you want me to add these to the make.conf's in the rc2 stages? Also, I see you decided to stick with Jackass!, despite my contention that it sounds like a broadway musical. I do like the "CONFIDENTIAL" watermark, thats a great idea. Oh well, like I said, I'll leave the marketing to you. I'll post the guide on the server ASAP, which will probably be tomorrow afternoon. Right now I need to go to sleep, and I'll be busy tomorrow morning.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 8:07 am Post subject: |
|
|
| Sith_Happens wrote: | | Bob P wrote: | | 1. I will get updated headers sent to you via email, either as file attachments, or as text that you can cut and paste. we should also consider the muted verison of monkey's excellent portage patch. |
Just send me those headers sometime tomorrow or Monday, and I'll add them to the config files in rc2. Thanks for reminding me about monkey89's patch. What I'll do is compile portage with the patch, but not include the contents of the portage overlay in the stage. That way somebody can remove the line by simply recompiling portage. |
actually, the idea of using the portage overlay for monkey's patch is kind of growing on me. what do you think are the pros and cons of including the overlay?
| Quote: | | Bob P wrote: | | 2a. I've tried removing GCC 3.3.5 from the rebuilt jackass-pentium system, and i can't get gcc-config 1 to change the default gcc compiler from 3.4.3.20050110 to 3.3.5. Confused can anyone explain this? |
This sounds simaler to the problem I was having earlier, but backwards. Why do you want to do this though? I'm a little confused. Once you've switched to gcc 3.4.3, why not just unmerge gcc 3.3.5? |
i was testing to see if the problem with gcc-config not functioning properly was present in the system. yes it is. because we should address every known bug when designing the next build, this is something that we need to find a solution for before we build -r2.
is anyone else having a problem with any of the jackass tarballs, where gcc-config # (where # refers to a number) fails to change the assigned compiler?
| Quote: | | Just so you know, I found that emerge -e system and emerge -e world are one in the same on a stage 3 tarball. |
yes, the system is the world when you first start out with stage 3. but that changes as soon as you emerge your first world program, like ccache.
edit: typos
Last edited by Bob P on Sun Apr 03, 2005 9:03 am; edited 1 time in total |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 8:24 am Post subject: |
|
|
| Sith_Happens wrote: | | Hey Bob, I like the documentation, did you make those cover ASCII art using figlet? There's a typo though, "We Can Rebuilt it". There are some more settings in the make.conf file shown in the documentation than I have currently been adding to the jackass make.conf's. Do you want me to add these to the make.conf's in the rc2 stages? |
yes, that is figlet!
"Rebuild" has been fixed.
yes, i thought it would be good to add the follwing info to the make.conf files: | Code: |
GENTOO_MIRRORS="<your mirror goes here> http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
RSYNC_RETRIES="3"
RSYNC_TIMEOUT=180
PORTAGE_NICENESS=3
AUTOCLEAN="yes"
FEATURES="ccache distlocks sandbox"
|
here's why:
- the user is going to have to add gentoo mirror information anyway, so why not add a template for them. you will have to remember to edit this AFTER you build the stages, otherwise YOUR mirror will be the default mirror. so make a note to change this after finishing the builds so you will not forget!
- the rsync values and portage values for niceness are "typical" values that will need to be set for emerge --sync, so why not put it in the default file?
- the FEATURES statement needs to be standardized for our testers. this was added to prevent errors because there has been some confusion in this thread about FEATURES statements.
- ccache is only being put into the docs as an optional step, so it doesn't need to be added to your make.confs.
| Quote: | Also, I see you decided to stick with Jackass!, despite my contention that it sounds like a broadway musical.
I do like the "CONFIDENTIAL" watermark, thats a great idea. Oh well, like I said, I'll leave the marketing to you. I'll post the guide on the server ASAP, which will probably be tomorrow afternoon. Right now I need to go to sleep, and I'll be busy tomorrow morning. |
a broadway musical!? come on, its not like i named this project "Urinetown!" 
if you don't get the file posted to the server until tomorrow, you'll probably find an updated replacement in your mailbox.
bob
Last edited by Bob P on Sun Apr 03, 2005 8:23 pm; edited 1 time in total |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 9:02 am Post subject: |
|
|
 new PDF should be in your mailbox, ryan. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 8:33 pm Post subject: |
|
|
update on the GCC-CONFIG problem - i have looked for our problem in bugzilla, though i have not found it there. IIRC someone reported this in one of the Stage 1/3 threads, so the problem seems to be have been experienced/reported by at least a handful of people, although it hasn't been reported to bugzilla yet.
i've looked at the CVS ebuild revision history, and it shows that the ebuild has been updated twice in the past few days. the ebuid got updated on 03/31/05 and 04/01/05 -- but i don't know why.
i'd recommend testing the new ebuild to see if it solves the compiler selection problem before removing the gcc 335 compiler. if the new ebuild solves the problem, then we can lock the portage snapshot on a date that includes it and get started on the -r02 build. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
| Posted: Sun Apr 03, 2005 8:47 pm Post subject: |
|
|
GCC-CONFIG update:
my main gentoo box and my jackass test box both suffer from the problem where gcc-config cannot select gcc versions. i have tried the update from gcc-config-1.3.10-r1 to gcc-config-1.3.10-r2 and the problem persists.  |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3374
Location: USA
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
