[OUTDATED] The Evolution Mission Install Guide 1.1.3

wrc1944 · Posted: Sat Mar 18, 2006 4:19 pm Post subject:

Just finished up X and kde. This version of guide works great here. Only problem I had was I had to edit xorg.conf a little. The Rgb and Modules paths had to be set to:

RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"

For some reason Xorg -configure did not produce a working xorg.conf file this time, so I used my old xorg.conf file from this box from a previous gcc-4.1 and Xorg-7.0 install (not using any version the guide), and assumed my xorg.conf file would at least boot X since it was on the same hardware (except new hard disk). Apparently, since I had previously emerged X on that installation, Xorg has changed the paths.

No big deal. Only other thing (probably unrelated to the guide) was that kde-addons failed to compile, again no big deal- I'll figure that out later.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

In 2.0, I will move back to xorgconf, and have the user change those 2 paths.

vipernicus · Posted: Sat Mar 18, 2006 4:49 pm Post subject:

'emerge -pv binutils' now shows binutils-2.16.91.0.7 from portage.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

I've already uploaded a new overlay which masks it (about 3 hours ago). Please run emission-manager update. The current patches don't work with it so don't expect a bump to it yet.

wrc1944 · Posted: Sat Mar 18, 2006 5:37 pm Post subject:

nesl247,
I just checked the xorg.conf file Xorg -configure produced in /root/xorg.conf.new, and the paths were indeed correct. Just to clarify- my problem (at least with those 2 paths) was my old xorg.conf file, and not the one generated by Xorg -configure.

One other thing I thought I'd mention. Between emerging xorg and emerging kde, I did an emerge --sync (foolishly, as it turned out) to check if my madwifi wireless was up (I had to take this box into another room and install a normal ethernet card/connection to use the Gentoo live cd (it still doesn't work with madwifi).

Anyway, when I tried to emerge kde back in my "office" with the wifi connection, portage installed qt-3.3.6 without my knowledge, and arts then subsequently failed, so I had to go back and manually install qt-3.3.5-r1 in order to get kde to emerge. So- I guess qt-3.3.6 needs to be masked, or put in package.provided until this is sorted out with qt-3.3.6.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

wrc1944: You mean packages failed to compile? If so I have no idea what to say. I am just going to leave it unmasked until I see more complaints, or until nxsty gives some information.

wrc1944 · Posted: Sat Mar 18, 2006 6:13 pm Post subject:

With qt-3.3.6 installed (which apparently emerge --sync now pulls in), arts failed to compile, which prevents an emerge kde from proceeding. After I reverted to qt-3.3.5-r1, arts compiled normally, and then I went on with kde, where only kdeaddons failed. The arts error with qt-3.3.6 had something to do with library qt-mt not being found, and "make sure you compiled qt with thread support." I don't have the whole arts error saved for reference, but the kdeaddons error is below.

ons -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o mainWidget.lo mainWidget.cpp
./mainWidget.h:39: error: expected class-name before '{' token
./mainWidget.h:95: error: 'QListViewItem' has not been declared
./mainWidget.h:100: error: 'QListViewItem' has not been declared
./mainWidget.h:105: error: 'QListViewItem' has not been declared
./mainWidget.h:110: error: 'QListViewItem' has not been declared
make[5]: *** [plugin_skel.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
make[5]: Leaving directory `/var/tmp/portage/kdeaddons-3.5.1/work/kdeaddons-3.5.1/konq-plugins/sidebar/delicious'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/var/tmp/portage/kdeaddons-3.5.1/work/kdeaddons-3.5.1/konq-plugins/sidebar/delicious'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdeaddons-3.5.1/work/kdeaddons-3.5.1/konq-plugins/sidebar'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdeaddons-3.5.1/work/kdeaddons-3.5.1/konq-plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdeaddons-3.5.1/work/kdeaddons-3.5.1'
make: *** [all] Error 2

!!! ERROR: kde-base/kdeaddons-3.5.1 failed.
Call stack:
ebuild.sh, line 1557: Called dyn_compile
ebuild.sh, line 966: Called src_compile
kdeaddons-3.5.1.ebuild, line 37: Called kde_src_compile
kde.eclass, line 111: Called kde_src_compile 'all'
kde.eclass, line 228: Called kde_src_compile 'myconf' 'configure' 'make'

!!! died running emake, kde_src_compile:make
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

Emerge the version (3.3.5-r1) included with my overlay. I will add the 3.3.6 to package.mask later today.

wrc1944 · Posted: Sat Mar 18, 2006 7:11 pm Post subject:

I guess this definitely means we shouldn't do another emerge --sync after the one in step 6.2, until after we have completed the entire installation, including X and kde/gnome/whatever. :wink:

_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

No, you just shouldn't ever do an emerge --sync during an emerge.

wrc1944 · Posted: Sat Mar 18, 2006 7:54 pm Post subject:

Actually, to be more precise, I had already completed the base install, rebooted, and was beginning emerge xorg when I did the additional sync just to check my wireless connection- I should have realized that was a mistake. :oops:

I just redownloaded the kdeaddons tarball, and emerged kdeaddons successfully this time, so that problem was just a corrupt tarball, and had nothing to do with qt or X, or the root-overlay and the guide. But I guess the qt-3.3.6 issue still stands for the present.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

I have just uploaded a new overlay that masks 3.3.6 because it doesn't include the risky/pertty patches. Waiting on nxsty to update his overlay.

ericsson · n00b Joined: 08 Oct 2004 Posts: 24

Good work,

Used your guide to upgrade from GCC 3.4. No problems (E17, gnome, fvwm).

Thanks
Keep up the good work

vipernicus · Posted: Sun Mar 19, 2006 12:35 am Post subject:

During the 'emerge -e world' step, after coreutils gets installed, I'm getting this error:

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

vipernicus · Posted: Sun Mar 19, 2006 12:58 am Post subject:

Thanks for the fast reply, but it didn't work, same error.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

For all users please do the following:

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

Once again:

wrc1944 · Posted: Sun Mar 19, 2006 5:40 pm Post subject:

OK- I ran the first update, and world needed 3 items. Went fine.

On the second update, I got this, with a huge warning, which I'm relunctant to do, because binutils-config -l shows this is the only version on my system!
--------------------------------------------------------------------------------------------------
gentoo wrc # binutils-config i686-pc-linux-gnu-2.16.91.0.6
* Switching to i686-pc-linux-gnu-2.16.91.0.6 ... [ ok ]
>>> Regenerating /etc/ld.so.cache...

* Please remember to run:

* # source /etc/profile
----------------------------------------------------------------------------------------
gentoo wrc # emerge -aC =sys-devel/binutils-2.16.91.0.6

>>> These are the packages that would be unmerged:

!!! 'sys-devel/binutils' is part of your system profile.
!!! Unmerging it may be damaging to your system.

sys-devel/binutils
selected: 2.16.91.0.6
protected: none
omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Do you want me to unmerge these packages? [Yes/No]
-----------------------------------------------------------------------------------------
Of course I answered No, as I obviously need binutils! What does all this mean- it seems totally wrong, so I must be misunderstanding something. I can't believe you mean for us to unmerge our only version of binutils. Please advise.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

I did that late at night sorry. I just corrected the post to have 0.7 unmerged. There was a bug in the overlay which didn't mask 0.7 correctly, so I needed to gurantee no one was running it.

wrc1944 · Posted: Sun Mar 19, 2006 6:10 pm Post subject:

Thanks for the quick clarification! I guess this proves it's always wise to actually read the commands before you copy/paste them into a terminal and execute them. :wink:

_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.39-r7, gcc-14
kernel-6.9.3 USE=experimental python3_12.3-final

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

Good thing I have a warning saying I gurantee nothing, because I get to say, next time read the warnings before you do anything, if someone screwed their system.

nesl247 · Veteran Joined: 15 Jun 2004 Posts: 1614 Location: Florida

For all users, please check /etc/fstab for "data=journal" next to noatime for all ext3 partitions. If it is not there add it. An example would be

Vla · Posted: Mon Mar 20, 2006 5:29 pm Post subject:

Are those updates included in the files used in the install guide or do I have to take these steps if I started a fresh install right now?