Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Stage 1/3 Installation Support - 2005.0 & GCC 3.4.3
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 19, 20, 21, 22, 23, 24  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Fri May 27, 2005 5:40 pm    Post subject: Reply with quote

IT wrote:
One thing I am a little worried about...to the point of not wanting to do any emerge -uDav worlds...I don't want to break this install and I don't usually use non-stable releases. would I just use the normal emerge --sync and emerge -uDav world to keep this puppy humming along? I saw an earlier post about this, in which Bob said the answer was posted in the 2004.3 post...but I couldn't find it. If you could point me to the exact post I'd like to read what was said.

Thanks Bob...for a great HOWTO...I'm sure you've heard that enough ;)


thanks for the feedback. in spite of what you might think, i haven't heard enough, so i always enjoy reading more. :)


HOW to UPDATE your SYSTEM AFTER a STAGE 1/3 INSTALL

as far as updates go, its important to remember that a Stage 1/3 install uses a testing branch toolkit. this means that the user is subject to the slings and arrows of outrageous fortune that are inherent in running a testing branch Gentoo box. in other words, a b0rked toolkit ebuild could pop-up into the testing branch in portage without warning. if you were to emerge a bad ebuild into your toolkit, your system could be annihilated. :x

dealing with stable branch toolkit updates is tricky business, but dealing with testing branch toolkit updates is even trickier. unlike stable branch updates, which you can rely on as being fairly innocuous, testing branch toolkit updates could be good for your system, or they could be very, very BAD for it. the user needs to adopt an update policy to protect them from the possibility of a testing branch ebuild borking their system. there are a number of ways to do this.

personally, i will not consider blindly upgrading any toolkit package on my system. before i will consider emerging a testing branch toolkit component onto my system, i will ALWAYS create a chrooted testing environment in which to perform the toolkit upgrade. only after thorough testing of the toolkit upgrade in the chrooted environment will i consider emerging the toolkit upgrade to my main system. this is an extremely important approach from a safety standpoint, and its an advanced method that we haven't specifically addressed in these threads. granted, testing a toolkit in a chrooted environment is a little beyond the scope of this thread, so if anyone wants to pursue this topic, i'd recommend starting a thread about it in Portage & Programming.

an easier approach is to just use hielvc's or minderaser's tcupdate.sh scripts to perform non-toolkit / world-only updates. if you complete a Stage 1/3 install, you'll have a testing branch toolkit on a stable branch system. it makes sense that once you find a stable toolkit in the testing branch, you should NEVER update it until you determine that the update that you are going to replace it with will perform properly. OTOH, you can safely update stable branch world packages whenever you'd like. the hard part about doing this is that you want to update the world packages without updating the toolkit packages, and Gentoo's emerge command doesn't offer this option as a command-line parameter. :?

normally, the process of updating the world packages without updating the toolkit packages requres that the user perform a pretend update of the world files, read the proposed output, and manually emerge the non-toolkit world packages. this is an extremely time consuming job, but its the safest way to update your system. hielvc and minderaser have automated the process so that their scripts perform these updates in an intelligent fasion -- just like a knowledgeable user would if he were performing the updates by hand. 8)

for more information on how to do this, you should follow the links to hielvc's and minderaser's scripts that are provided in the Stage 1/3 Guide. you should download the scripts, and you should use them to perform world updates that do not update the toolkit components. the information on how to do this is discussed in detail in their thread in the Unsupported Software Forum:


https://forums.gentoo.org/viewtopic-t-282474-highlight-emerge+wrapper.html
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
IT
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jul 2004
Posts: 140
Location: Terra Firma

PostPosted: Fri May 27, 2005 9:58 pm    Post subject: Reply with quote

Great! that answered pretty much all of my questions! TY :D and thanks for the quick response.
Back to top
View user's profile Send private message
ravv
n00b
n00b


Joined: 30 May 2005
Posts: 3

PostPosted: Mon May 30, 2005 11:09 am    Post subject: Reply with quote

Maybe this has been discussed but i didn´t find it when i searched.

Changing
CHOST="i586-pc-linux-gnu"
to
CHOST="i686-pc-linux-gnu"
would have saved me alot of time.

According to this thread glibc-2.3.5 failes compiling under i586. I don´t know if it failes for everyone but i did for me.

Yes i know i´m a newbie and shouldn´t be using this guide but i am and you can´t stop me! Feel free to flame me if i´m wrong :)
Back to top
View user's profile Send private message
Sith_Happens
Veteran
Veteran


Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park

PostPosted: Mon May 30, 2005 5:30 pm    Post subject: Reply with quote

ravv wrote:
Maybe this has been discussed but i didn´t find it when i searched.

Changing
CHOST="i586-pc-linux-gnu"
to
CHOST="i686-pc-linux-gnu"
would have saved me alot of time.

According to this thread glibc-2.3.5 failes compiling under i586. I don´t know if it failes for everyone but i did for me.

Yes i know i´m a newbie and shouldn´t be using this guide but i am and you can´t stop me! Feel free to flame me if i´m wrong :)
No, that has been my experience as well. That is why when we developed the Jacakss! project for Gentoo 2005.0, we used GCC 2.3.4 in the i586 stages. However, if you are going to be compiling with an i686 chost, then using GCC 2.3.5 isn't a problem.
_________________
"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
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3063
Location: Korea

PostPosted: Mon May 30, 2005 6:55 pm    Post subject: Reply with quote

ravv wrote:
Maybe this has been discussed but i didn´t find it when i searched.

Changing
CHOST="i586-pc-linux-gnu"
to
CHOST="i686-pc-linux-gnu"
would have saved me alot of time.

According to this thread glibc-2.3.5 failes compiling under i586. I don´t know if it failes for everyone but i did for me.

Yes i know i´m a newbie and shouldn´t be using this guide but i am and you can´t stop me! Feel free to flame me if i´m wrong :)


If you were using something other than i586 pc you shouldn't have:
1) Ever used a stage tarball for an i586
2) Had CHOST="i586-pc-linux-gnu" in your make.conf

The guide clearly says that the only reason it uses an x86 stage tarball and that CHOST value is because Bob was writing it based on his install he did for an old pentium computer. You must tailor it to meet your pc's specification.
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Tue May 31, 2005 5:08 pm    Post subject: Reply with quote

ravv wrote:
Maybe this has been discussed but i didn´t find it when i searched.

Changing
CHOST="i586-pc-linux-gnu"
to
CHOST="i686-pc-linux-gnu"
would have saved me alot of time.

According to this thread glibc-2.3.5 failes compiling under i586. I don´t know if it failes for everyone but i did for me.

Yes i know i´m a newbie and shouldn´t be using this guide but i am and you can´t stop me! Feel free to flame me if i´m wrong :)


as the others have noted, the CHOST specification is something that is based upon your processor type, and it really is not something that you have any freedom about choosing. when you build your system, there is ONE and only ONE CHOST setting that will be the correct choice for your computer. [1] this is really a Gentoo Fundamentals issue that you need to learn early on, so that you don't make repeated mistakes of this type.


[1] ok, i guess you could intentionally use a 586 CHOST on a 686 computer in the case that you're building on one machine to run on another, but strictly speaking, there is only ONE chost setting, tarball, and processor specification that should be used on any given PC.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
ravv
n00b
n00b


Joined: 30 May 2005
Posts: 3

PostPosted: Wed Jun 01, 2005 11:24 pm    Post subject: Reply with quote

Accordning to the thread that version of glibc can only be built with chost 686. It simly won´t build with anything less. I actually have no idea not like i´m going to flush my system to try it :) Oh well i´m not going to complain more now. great guide loved it :)
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3063
Location: Korea

PostPosted: Thu Jun 02, 2005 12:20 am    Post subject: Reply with quote

ravv wrote:
Accordning to the thread that version of glibc can only be built with chost 686. It simly won´t build with anything less. I actually have no idea not like i´m going to flush my system to try it :) Oh well i´m not going to complain more now. great guide loved it :)


That's not entirely correct. That version of glibc can't be built with chost=i586 or lower when you use linuxthreads rather than nptl. So if you force it to build glibc to only use nptl then it will work with chost=i586, if you have chost > i586 it should work with both, and if you have a non-x86 processor it should work with both as well.
Back to top
View user's profile Send private message
kki
n00b
n00b


Joined: 21 Nov 2003
Posts: 10

PostPosted: Thu Jun 02, 2005 9:23 am    Post subject: problem with libstdc++.so.5 Reply with quote

Hello

After i have pruned the old gcc and try to emerge again the new gcc 3.4.4, i obtain this error:
Error while loading shared libraries libstdc++.so.5

and emerge doesn't work anymore :-(

Any idea ?

thanks !
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Jun 02, 2005 4:12 pm    Post subject: Re: problem with libstdc++.so.5 Reply with quote


How To Ask For Support

When asking for support, please give us all of the information that we need to approach your problem. This would include:

1. the full output of the error message you received
2. the output of "emerge --info"
3. the name of the tarball that you installed from

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Naveg
n00b
n00b


Joined: 20 May 2005
Posts: 73

PostPosted: Fri Jun 03, 2005 2:16 am    Post subject: Reply with quote

more of a question than a support request:

If i'm installing via Knoppix, would the command for mounting the /proc differ from the in the guide?
Back to top
View user's profile Send private message
quanttrom
n00b
n00b


Joined: 26 Jan 2004
Posts: 19

PostPosted: Fri Jun 03, 2005 2:25 am    Post subject: missing libstdc++.so.5 Reply with quote

Hello,
I was following the guide that you provided and ended up with the same error that kki is ending up with
mainly missing libstdc++.so.5

when I try to emerge anything I get the following:
Code:

livecd / # emerge glibc
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory


if I try to type in emerge -info .. same result :
Code:
livecd / # emerge -info
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

in fact ANYTHING that uses python won't load because it needs the library..


my make.conf is quite long but here it is:
Code:
CHOST="i686-pc-linux-gnu"
CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe -fforce-addr -fomit-frame-pointer -mmmx -msse -msse2 -m3dnow \
-mfpmath=sse"
CXXFLAGS=${CFLAGS}
ACCEPT_KEYWORDS="x86"

LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"

PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
DISTDIR=${PORTDIR}/distfiles
PKGDIR=${PORTDIR}/packages
PORT_LOGDIR=/var/log/portage
PORTDIR_OVERLAY=/usr/local/portage

GENTOO_MIRRORS="http://adelie.polymtl.ca/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://gentoo.arcticnetwork.ca/ \
http://gentoo.mirrored.ca/"
SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage"

RSYNC_RETRIES="3"
RSYNC_TIMEOUT=180
MAKEOPTS="-j2"
#PORTAGE_NICENESS=3
AUTOCLEAN="yes"
FEATURES="ccache distlocks sandbox userpriv usersandbox"
CCACHE_SIZE="512M"
RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes


USE="-3dfx 3dnow X aax -aalib -accessibility -acl acpi -adabas -adns -afs aim alsa -altivec apache2 apm arts audiofile \
avi bash-completion -bcmath berkdb -bidi -birdstep -bluetooth bmp -bonobo bzlib -canna -caps cdb cdparanoia cdr -chasen \
-cjk crypt cups -db2 -dbase dbus dga dio directfb doc dv dvd dvdr -eds emacs emacs-w3 -emboss -empress encode -esd -esoob \
-ethereal evo exif -fam fbcon -filepro flac truetype -freewnn frontbase ftp gd -geoip gif -glut -gnome gphoto2 gpm -gps \
gtk gtk2 icq -ieee1394  imagemagic -imap -interbase -ipv6 -jabber -jack java javascript -joystick jpeg kde kdeenablefinal \
kdexdeltas lirc lm_sensors mad -migemo mime -nmap mmx mozilla mp3 mpeg msn -msql -mssql mysql -nas ncurses -netboot -nls \
nptl -oci8 -odbc ogg oggvorbis openal opengl -oracle oscar -oss -pcmcia pcre -pda pdflib perl -pfpro php png -portaudio \
-postgres -prelude qt quicktime readline samba -sapdb -sasl -scanner -sdl session sharedext sharedmem -shorten -slang \
-smartcard -sndfile -snmp -soap -socks5 -solid -speex spell spl -sqlite sse -ssl -sybase symlink -tcpd -tetex tiff \
tokenizer truetype usb -v4l vcd -vhosts -videos -voodoo3 vorbis -wifi win32codecs -wmf xine -xinerama xml2 xmms xvid \
yahoo -yaz -zeo"


and I'm installing from stage3-athlon-xp-2005.0.tar.bz2 ...this is the image that comes on one of the LiveCD's

Thank you in advance,
Any help would be greatly appreciated!
Back to top
View user's profile Send private message
Naveg
n00b
n00b


Joined: 20 May 2005
Posts: 73

PostPosted: Fri Jun 03, 2005 5:05 am    Post subject: Reply with quote

I get an error when i issue

# emerge gcc-config glibc binutils gcc

I am installing through knoppix

Here is the output:

Code:
Knoppix / # emerge gcc-config glibc binutils gcc
Calculating dependencies ...done!
>>> emerge (1 of 5) sys-devel/gcc-config-1.3.10-r2 to /
>>> md5 files   ;-) gcc-config-1.3.10-r1.ebuild
>>> md5 files   ;-) gcc-config-1.3.8-r4.ebuild
>>> md5 files   ;-) gcc-config-1.4.0.ebuild
>>> md5 files   ;-) gcc-config-1.3.10-r2.ebuild
>>> md5 files   ;-) ChangeLog
>>> md5 files   ;-) metadata.xml
>>> md5 files   ;-) files/digest-gcc-config-1.4.0
>>> md5 files   ;-) files/digest-gcc-config-1.3.10-r1
>>> md5 files   ;-) files/digest-gcc-config-1.3.10-r2
>>> md5 files   ;-) files/wrapper-1.4.3.c
>>> md5 files   ;-) files/wrapper-1.4.5.c
>>> md5 files   ;-) files/wrapper-1.4.6.c
>>> md5 files   ;-) files/digest-gcc-config-1.3.8-r4
>>> md5 files   ;-) files/gcc-config-1.3.8
>>> md5 files   ;-) files/gcc-config-1.4.0
>>> md5 files   ;-) files/gcc-config-1.3.10
ACCESS DENIED  open_wr:   /UNIONFS/dev/pts/1
ACCESS DENIED  open_wr:   /UNIONFS/dev/pts/1
>>> Unpacking source...
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-sys-devel_-_gcc-config-1.3.10-r2-10495.log"

open_wr:   /UNIONFS/dev/pts/1
open_wr:   /UNIONFS/dev/pts/1
--------------------------------------------------------------------------------
Back to top
View user's profile Send private message
Naveg
n00b
n00b


Joined: 20 May 2005
Posts: 73

PostPosted: Fri Jun 03, 2005 7:04 pm    Post subject: Reply with quote

Ok that problem fixed, but a new one now.

After setting gcc 3.4.4 to be the default compiler using #gcc-config 5 i get this when doing env-update
Code:

Knoppix / # env-update && source /etc/profile
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Back to top
View user's profile Send private message
moocha
Watchman
Watchman


Joined: 21 Oct 2003
Posts: 5722

PostPosted: Fri Jun 03, 2005 7:16 pm    Post subject: Reply with quote

Naveg wrote:
Ok that problem fixed, but a new one now.

After setting gcc 3.4.4 to be the default compiler using #gcc-config 5 i get this when doing env-update
Code:

Knoppix / # env-update && source /etc/profile
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
That's because gcc-3.4.4 doesn't automatically pull in libstdc++-v3 anymore. Get it back from your backup GCC package or from avenj's rescue packages, then re-emerge it manually.
_________________
Military Commissions Act of 2006: http://tinyurl.com/jrcto

"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin
Back to top
View user's profile Send private message
Naveg
n00b
n00b


Joined: 20 May 2005
Posts: 73

PostPosted: Fri Jun 03, 2005 8:25 pm    Post subject: Reply with quote

do i put the file in the new 3.4.4 directories? or should i just symlink to them in /usr/lib
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Fri Jun 03, 2005 11:35 pm    Post subject: Reply with quote

:arrow: Stage 1/3 Installation Support - Gentoo 2005.0 & GCC 3.4.3

there are a number of reasons that the Guide doesn't support the use of GCC 3.4.4 or installation via Knoppix. :idea: your problems are among them. :roll:
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Naveg
n00b
n00b


Joined: 20 May 2005
Posts: 73

PostPosted: Sat Jun 04, 2005 1:53 am    Post subject: Reply with quote

those reasons arent too strong, as both of my problems had very simple solutions.
Back to top
View user's profile Send private message
quanttrom
n00b
n00b


Joined: 26 Jan 2004
Posts: 19

PostPosted: Sat Jun 04, 2005 4:37 am    Post subject: Reply with quote

I have been changing couple of things as I go along the manual..(since I'm installing GCC 3.4.4)
once I'm done I'll see how things go..
and tell you if it worked..
so far so good...

*EDIT*
stumbled again..with notworking tar...hehe..I have no idea how I got that...
*EDIT*
very very stupid mistake...now it seems to be working fine..recompiling my toolchain..
Back to top
View user's profile Send private message
rutski89
Guru
Guru


Joined: 14 Mar 2005
Posts: 468
Location: United States N.Y.

PostPosted: Sat Jun 04, 2005 5:51 pm    Post subject: Reply with quote

So... is a fix for this simply to emerge gcc-3.4.4 for the first time, and then do "emerge -e system && emerge -e world" and THEN AFTER all that you do emerge -P gcc? Will this automatcially link python and everything else against /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 ? Does gcc-config have to be done before or after the world and system emerges? The lib in /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 is libstdc++.so.6, is it OK that its not so.5? This will add another emerge -e system and emerge -e world to Bob P's guide :? That means that if glibc with nptl is compiled 2x times when you run "emerge glibc" then glibc will now be compiled total of 8 times thoughout the guid :roll:
_________________
<< ^ | ~ >>
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Sat Jun 04, 2005 6:42 pm    Post subject: Reply with quote

Naveg wrote:
those reasons arent too strong, as both of my problems had very simple solutions.

i never said that the solutions were complicated. its just that your problems are unsupported. :wink:

one thing that is useful to bear in mind is that this thread is designed to provide Official Support for the Stage 1/3 Installation Guide v. 2005.0, which uses GCC 3.4.3. its scope is limited to 2005.0 and GCC 3.4.3.

GCC 3.4.4 is a completely different animal, and any experienced Gentoo users should expect that as @moocha pointed out, it is going to behave differently -- its the norm to expect that any Gentoo upgrade may not function as an exact drop-in replacment for something that came before it -- that is the price that you have to pay if you want to use a bleeding-edge distribution like Gentoo.

just as installing GCC 3.4.4 involves a significant deviation from the Guide, installing from Knoppix involves a significant deviation from the Guide. the solutions may be simple enough to implement, but they're beyond the scope of the Stage 1/3 Installation Guide for 2005.0 and GCC 3.4.3, and hence they are unsupported.

if you're attempting to install GCC 3.4.4, or if you're attempting to install from Knoppix, then you're not following the Guide. if that's the case, then you're looking in the wrong place for support. if you're interested in adapting the Stage 1/3 Guide to work with GCC 3.4.4, then you should look here:
https://forums.gentoo.org/viewtopic-t-345229.html


just as the original Stage 1/3 Installation Guide for 2004.3 and GCC 3.4.3 had to be extensively rewritten to support the release of Gentoo 2005.0, it looks like the Guide will have to be extensively rewritten to support GCC 3.4.4. unfortunately, the solution is not as simple as just changing the existing Guide to add support for GCC 3.4.4, as doing so would render it incompatible with GCC 3.4.3 -- and all of the information that has been stored in 20+ pages of this support thread would become invalid.

in order to keep this Support Thread on-track, everyone would appreciate it if the topics in this thread are limited to those that actually pertain to the Stage 1/3 Guide for 2005.0 and GCC 3.4.3. this allows the people who are dedicating their free time to offer support not to have to wade through irrelvant material. it also allows thousands of users who are looking for support information not to have to wade through irrelevant material. keeping the support threads on-track is good for everyone. although alternative installation methods are available, posting problems and solutions about them into this thread doesn't help the people who are trying to follow the Guide. it only serves to clutter up the thread with irrelevant information.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Sat Jun 04, 2005 11:40 pm    Post subject: Reply with quote

for those who are looking for support, here's the bottom line: GCC 3.4.3 is currently stable enough for use with a Stage 1/3 Install, while GCC 3.4.4 is not. there are still a number of unresolved issues with GCC 3.4.4 that complicate its use in a Stage 1/3 Install.

:arrow: If you want to perform a reliable install, I recommend the Stage 1/3 Guide for GCC 3.4.3.

:arrow: If you're willing to live on the bleeding edge and to help to blaze the trail, check out the experimental Stage 1/3 Guide for GCC 3.4.4.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
quanttrom
n00b
n00b


Joined: 26 Jan 2004
Posts: 19

PostPosted: Sun Jun 05, 2005 4:36 am    Post subject: GCC 3.4.4 Reply with quote

I'll tell u how the install goes using your new guide for GCC 3.4.4....I started out doing my own modifications to the guide but it seems like so far they are identical..
Back to top
View user's profile Send private message
jmbsvicetto
Moderator
Moderator


Joined: 27 Apr 2005
Posts: 4734
Location: Angra do Heroísmo (PT)

PostPosted: Sun Jun 05, 2005 12:33 pm    Post subject: Reply with quote

Bob,

given the recent problems with Portage updates relating to GCC, I thiink you should post one of your "infamous warnings" ;-) on the opening page about gcc. It would also be helpful if you posted the link to one of the threads relating to that. I'm surprised that this thread hasn't been flooded by this issue.
For those unaware, I'm refering to the dreadful libstdc++.so.5 or libstdc++.so.6 not found errors.
I think the following threads can be helpful on this issue:
https://forums.gentoo.org/viewtopic-t-345446.html
https://forums.gentoo.org/viewtopic-t-345046-highlight-libstdc.html
https://forums.gentoo.org/viewtopic-t-336444-highlight-.html
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Sun Jun 05, 2005 3:40 pm    Post subject: Reply with quote

thanks for the suggestion, Jim. and thanks for the links! :wink:

i've modified the masking atoms in the Stage 1/3 Guide for 2005.0 and GCC 3.4.3 so that instead of emerging the latest version of GCC in the testing branch, portage will emerge the specific version of GCC that is referenced in the Guide. this means that if you follow the Stage 1/3 Guide for GCC 3.4.3 and 2005.0, you will only get GCC 3.4.3, and the Guide itself and the Support Thread will both remain relevant for GCC 3.4.3. from a practical standpoint, this eliminates the GCC 3.4.4 bugs that were happening when the Guide was configured to emerge the most recent version of GCC, without regard to version number.

the way that the Stage 1/3 Guide is written now, the user will only get the desired version of GCC that is specifically intended by that version of the Stage 1/3 Guide. i think that this will markedly simplify the problem -- now the Guide for 3.4.3 will have its own Installation Thread and its own Support Thread, and the Guide for 3.4.4 will have its own Installation Thread and its own Support Thread. the problems that are unique to each version of GCC will be confined to their own threads. that should simplify things ALOT.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3 ... 19, 20, 21, 22, 23, 24  Next
Page 20 of 24

 
Jump to:  
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