Stage 1/3 Installation Guide for 2005.0 and GCC 3.4.4

netjunkie · Tux's lil' helper Joined: 03 May 2005 Posts: 98

Hi,

after following this guild everything works until step 7.2.4

Bob P · Posted: Wed Jun 08, 2005 4:56 pm Post subject:

No answers to support questions will be posted here. You need to use the Support Thread. :idea:

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

spidna · Tux's lil' helper Joined: 17 Feb 2004 Posts: 148

quick question on Bob P installation guide, after the installation do i have to emerge sync, emerge -u world, emerge xorg. i'm going to try that today night when i get home with a friends computer. going install windows xp , gentoo and centos. centos on /dev/hdb while other operating system would be on /dev/hda. I guess i'm going to use grub from centos, would not have to install grub on gentoo but fix the /etc/fstab. using ext3 filesystem.

Naveg · n00b Joined: 20 May 2005 Posts: 73

well....technically you dont HAVE to emerge xorg-X11.....but i think most people do

Iron_DragonLord · Apprentice Joined: 04 Nov 2004 Posts: 273

This is not really a support question but one about the installation method.

Are hotplug and coldplug really needed? My friend is using udev without them, and I just switched my server to udev and I did not emerge hotplug and coldplug, it seems to be working fine.

Iron_DragonLord · Apprentice Joined: 04 Nov 2004 Posts: 273

Nevermind, I answered my own question:

http://www.gentoo.org/doc/en/udev-guide.xml#doc_chap2

Bob P · Posted: Wed Jun 15, 2005 9:10 pm Post subject:

Problems Setting Hostname & Domainname

the new stable branch versions of baselayout have deprecated the use of /etc/hostname and /etc/dnsdomainname in favor of /etc/conf.d/hostname and /etc/conf.d/domainname. if you install/update to sys-apps/baselayout-1.11.12-r4 or later and you've used the deprecated /etc/hostname and /etc/dnsdomainname methods, you'll notice boot warnings. you can make them go away by following the second set of examples in Section 10.2 of the Stage 1/3 Guide.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

slaterson · Guru Joined: 26 Feb 2003 Posts: 313

i have been going through this howto today and ran into the following error when doing an 'emerge -e system'. the error occurs on package dev-python/python-fchksum-1.7.1 (18 of 90 for emerge -e system).

j-m · Retired Dev Joined: 31 Oct 2004 Posts: 975

slaterson · Guru Joined: 26 Feb 2003 Posts: 313

rutski89

Bob P · Posted: Fri Jun 24, 2005 8:58 pm Post subject:

Bob P

zendal · n00b Joined: 30 Nov 2002 Posts: 23 Location: Olympia, WA

changes for grub due to 2.6.12 kernel
and splashutils due to themes are no longer included must emerge the themes

Bob P · Posted: Thu Jul 14, 2005 9:12 am Post subject: Re: Need some changes

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

I think he means that with the 2.6.12 kernel series and the newest stable splashutils, warnings pop up during their emerge that say to re-emerge splashutils after upgrading to that new kernel, which the newest splashutils requires. Also, the splash themes are no longer included in the splashutils package; they must be separately emerged with, for example, emerge media-gfx/splash-themes-gentoo. And finally, the new splash needs to be rebuilt by another geninitramfs command.

Oh, and there are now several *required* boot options that must be appended to the appropriate grub entries, including new formats for the previous options present in this Guide. I've been following the splash/kernel developments, and here are the related threads:

gentoo-sources-2.6.12 borks fbsplash
Kernel upgrade - bootsplash broken
boot error, vesafb/splashutils related
fbsplash problems with 2.6.12-gentoo-r4

zendal · n00b Joined: 30 Nov 2002 Posts: 23 Location: Olympia, WA

I went back
2.6.11 kernel
0.94 grub
and emerged the themes

There is also error in the package.keywords he typed

Bob P · Posted: Thu Jul 14, 2005 4:32 pm Post subject: Re: FBSplash

kueitao · Apprentice Joined: 22 Jan 2005 Posts: 241

Hello,

I have some questions about some steps in the guide that I don't understand.

(1) Why do we need to install libstdc++-v3? I know that when compiling gcc from sources, at least from version 3.4.0, the c++ library is automatically compiled at the same time. I've compiled lots of gcc-3.4.0 to gcc-4.0.0, with support for C,C++ and other languages, without ever undertaking any special actions with regard to libstdc++, except asking C++ support at configure. Is it perhaps because "emerge" doesn't work as a normal "configure && make (bootstrap) && make install" cicle?

(1.5) I have put parenthesys in "make bootstrap" because I want to know whether or not "emerge gcc" performs a real gcc bootstrap (three stages) or a simple make. How does it work?

(2) In section 7.2.4 (Rebuilding the System Toolkit) there's the following instruction:

# emerge -e system && emerge -e system

Why is it needed to repeat twice the same operation, seen that before that point we already have a new toolchain built with gcc-3.4.4? What am I missing?

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

1) IIRC, libstdc++ provides backward compatibility for the regular 3.3.x gcc series.

1.5) Emerging gcc is just that--compilation and installation of a package, not any special bootstrap per se.

2) This has been explained many times in the Stage 1/3 guides, the Jackass! Guide, and heilvc's correct toolchain thread. Please do look through those for detailed answers, but in short, recompiling the toolchain is necessary. Until that step, the only thing you have done is emerged a new toolchain and switched to that compiler. However, you have not yet begun using it; every package has been build with the wrong (read: OLD) gcc. Thus, now you have to recompile your packages in order to get immediate benefits of the new toolchain. If you do not recompile your system, then not only will it be somewhat unstable, but only future packages you emerge--like Gnome or AbiWord--will be built with the 3.4.4 toolchain. The rest of your system will still only be compiled from a 3.3.x toolchain, which is obviously undesirable.

Again, please search for the threads that I mentioned if you need further clarification; these questions come up over and over in those guides.

kueitao · Apprentice Joined: 22 Jan 2005 Posts: 241

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

Dark_Cloud · n00b Joined: 29 Jun 2003 Posts: 27

Sorry, but i still disagree with you... in 7.2.4 Rebuilding the System Toolkit the toolkit was totally rebuilt and at the final of that we had a working gcc-3.4.4 and all the packages (of course) built with gcc-3.3.5. When we performe the emerge -e system we are compiling all the packages including the gcc with the existing gcc-3.4.4... so after that we have a system totally built with gcc-3.4.4... it isn't necessary to use emerge -e system again.

sorry about my poor english, trying to develop it :wink:

cheers:D
_________________
Powerred by Gentoo Linux 2005.0
2.6.12-ck4 i686 AMD Athlon(TM) XP 2600+
GCC 3.4.4, glibc 2.3.5 (NPTL)

E17 cuz it's CUTE and FAST! Just Get-E

kueitao · Apprentice Joined: 22 Jan 2005 Posts: 241

I'm sorry about my poor English, as Dark_Cloud is. It seems I am not able to drive nightmorph to the point. Except for the issues related to the old libstdc++ and the "make (profiled)bootstrap", for which He didn't reply to my last post, I suppose...

Please read carefully the following from Dark _Cloud. I hope He is better than me in showing the issue:

Bob P · Posted: Sat Jul 16, 2005 3:14 pm Post subject:

the answer: STATICALLY RETAINED LIBRARIES.

the need to perform redundant compilations to purge the system of statically retained libraries is a well established fact. those who understand the nature of the problem accept the need for redundant compilation. those who do not understand the nature of the problem tend to be the ones who start agruments about it.

if the guide doesn't suit your needs, you don't have to use it. but please, don't use your theoretical explanations to try to prove that the guide is wrong. over 100,000 people have installed using this method. it started off in theory using methods similar to what you are suggesting, and it has refined to its current state of revision by trial and error. the guide is written the way it is written because that method results in a system that works reliably. the suggestions that you are arguing would result in a system that would not work reliably.

please try to accept the fact that the Guide is written the way it is because this is the way that you have to do it. please don't argue that the Guide needs to be changed just because you don't fully understand what the Guide is doing. we've had 100,000+ test builds refine the installation method, and we won't consider changing it just because a couple of people who don't understand our methods start an argument about it.

the reasons for the steps are clearly outlined in the hundreds of pages of posts in the multiple threads related to this installation method. if you don't understand what is being done and why it is being done, please don't ask us to explain it for you. everything has already been well documented, and all that you need to do is read the threads to understand the logic.

best of luck.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks