Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Need advice on updating world with dependencies
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Fri Oct 06, 2006 4:37 pm    Post subject: [SOLVED] Need advice on updating world with dependencies Reply with quote

Hi,

There's been a long time since the last time I used and updated my gentoo system and now, a new year on the university begins and I need to use linux again; but before all that, I want to updated the system. But I need your help cause I don't want to mess things up...

As I already told, the last time I updated the system was long ago and now, I just did an "emerge -pvuDN world" and I get lots of entries, lots of them blocked and they are about 500mb of downloads (that's not a problem). The thing is, the blocked packages, I think it's something to do with Xorg 7.0 which some packages are already on the stable branch.

What I want to know, is how to update my system, unblocking what is blocked and emerge all packages without having any problems in the future cause of some big changes it may happen.

Below, I posted some files that you may need to take a look. The first one is the output from the "emerge -pvuDN world".

:arrow: emerge -pvuDN world

:arrow: package.keywords

:arrow: package.mask

:arrow: package.unmask


If you need the output from any other command or file, just let me know and I'll post it ASAP...

P.S: If you see the sentence "Clique AQUI para prosseguir" after clicking the package.mask or package.unmask links, just click on the word "AQUI" to see the file...


Last edited by Nazgulled on Wed Oct 18, 2006 9:23 am; edited 1 time in total
Back to top
View user's profile Send private message
bluedevils
Apprentice
Apprentice


Joined: 21 Jul 2004
Posts: 252
Location: Vancouver BC -> NYC, NY

PostPosted: Fri Oct 06, 2006 4:59 pm    Post subject: Reply with quote

xorg went to a modular arch. Do a search on gentoo wiki moduar xorg and there should be an upgrade guide.
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Fri Oct 06, 2006 6:41 pm    Post subject: Reply with quote

So, I just follow that guide and then all packages will be unblocked and will be able to update the whole system without any problems correct? 2 questions though...

1) How long do you think it will take my machine to compile all that 500mb of updates? I have a Pentium 2.0GHz (laptop centrino) with 1GB of ram.

2) That Xorg 7.0 modular doesn't mean I'll have XGL, right? If I want XGL I have to emerge other packages, right?
Back to top
View user's profile Send private message
Section_8
Guru
Guru


Joined: 22 May 2004
Posts: 462
Location: Arlington, TX, US

PostPosted: Fri Oct 06, 2006 7:45 pm    Post subject: Reply with quote

You may also have an upgrade to gcc there. Here is the upgrade guide: http://www.gentoo.org/doc/en/gcc-upgrading.xml

You can pipe the output of emerge --pretend through genlop to get a time estimate:
Code:
emerge --pretend (whatever) | genlop -p
Back to top
View user's profile Send private message
bluedevils
Apprentice
Apprentice


Joined: 21 Jul 2004
Posts: 252
Location: Vancouver BC -> NYC, NY

PostPosted: Fri Oct 06, 2006 8:00 pm    Post subject: Reply with quote

I don't remember xorg being openoffice or kde wise long, but if you upgrade gcc I found the best recompile is just to do everything (emerge -e world). Read the gcc upgrade guide.

I think the modular xorg compile was less than overnight on the sony t140. No XGL by default. In fact you probably won't notice anything blaringly different. I think they moved it this way for development puropses (I could very well be wrong).
Back to top
View user's profile Send private message
bluedevils
Apprentice
Apprentice


Joined: 21 Jul 2004
Posts: 252
Location: Vancouver BC -> NYC, NY

PostPosted: Fri Oct 06, 2006 8:02 pm    Post subject: Reply with quote

BTW the gcc upgrade will probably help you with more than just xorg. I found more and more troubles with compiling ebuilds until I upgraded.
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sat Oct 07, 2006 2:52 am    Post subject: Reply with quote

I'm using gcc 3.4.6-r1 and I really didn't want to upgrade to 4 right now... I think I'll just try to update the system without moving to gcc 4...
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sat Oct 07, 2006 8:12 pm    Post subject: Reply with quote

fixed all the problems.. now I'm just left with 400-500mb of updates...

thank you all.
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sun Oct 08, 2006 11:22 am    Post subject: Reply with quote

Well, I'm left with some other problems that I don't know how to resolve... I've been searching a bit on google, this forums but couldn't find an explicit answer and I really don't know what to do...

Code:
nazbox nazgulled # emerge -vuDN world
Calculating world dependencies... done!

>>> Emerging (1 of 213) sys-libs/glibc-2.4-r3 to /
 * glibc-libidn-2.4.tar.bz2 MD5 ;-) ...                                   [ ok ]
 * glibc-libidn-2.4.tar.bz2 RMD160 ;-) ...                                [ ok ]
 * glibc-libidn-2.4.tar.bz2 SHA1 ;-) ...                                  [ ok ]
 * glibc-libidn-2.4.tar.bz2 SHA256 ;-) ...                                [ ok ]
 * glibc-libidn-2.4.tar.bz2 size ;-) ...                                  [ ok ]
 * glibc-2.4.tar.bz2 MD5 ;-) ...                                          [ ok ]
 * glibc-2.4.tar.bz2 RMD160 ;-) ...                                       [ ok ]
 * glibc-2.4.tar.bz2 SHA1 ;-) ...                                         [ ok ]
 * glibc-2.4.tar.bz2 SHA256 ;-) ...                                       [ ok ]
 * glibc-2.4.tar.bz2 size ;-) ...                                         [ ok ]
 * glibc-ports-2.4.tar.bz2 MD5 ;-) ...                                    [ ok ]
 * glibc-ports-2.4.tar.bz2 RMD160 ;-) ...                                 [ ok ]
 * glibc-ports-2.4.tar.bz2 SHA1 ;-) ...                                   [ ok ]
 * glibc-ports-2.4.tar.bz2 SHA256 ;-) ...                                 [ ok ]
 * glibc-ports-2.4.tar.bz2 size ;-) ...                                   [ ok ]
 * glibc-2.4-patches-1.17.tar.bz2 MD5 ;-) ...                             [ ok ]
 * glibc-2.4-patches-1.17.tar.bz2 RMD160 ;-) ...                          [ ok ]
 * glibc-2.4-patches-1.17.tar.bz2 SHA1 ;-) ...                            [ ok ]
 * glibc-2.4-patches-1.17.tar.bz2 SHA256 ;-) ...                          [ ok ]
 * glibc-2.4-patches-1.17.tar.bz2 size ;-) ...                            [ ok ]
 * glibc-powerpc-cpu-addon-v0.01.tgz MD5 ;-) ...                          [ ok ]
 * glibc-powerpc-cpu-addon-v0.01.tgz RMD160 ;-) ...                       [ ok ]
 * glibc-powerpc-cpu-addon-v0.01.tgz SHA1 ;-) ...                         [ ok ]
 * glibc-powerpc-cpu-addon-v0.01.tgz SHA256 ;-) ...                       [ ok ]
 * glibc-powerpc-cpu-addon-v0.01.tgz size ;-) ...                         [ ok ]
 * glibc-linuxthreads-20060605.tar.bz2 MD5 ;-) ...                        [ ok ]
 * glibc-linuxthreads-20060605.tar.bz2 RMD160 ;-) ...                     [ ok ]
 * glibc-linuxthreads-20060605.tar.bz2 SHA1 ;-) ...                       [ ok ]
 * glibc-linuxthreads-20060605.tar.bz2 SHA256 ;-) ...                     [ ok ]
 * glibc-linuxthreads-20060605.tar.bz2 size ;-) ...                       [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking glibc-2.4.tar.bz2 ;-) ...                                     [ ok ]
 * checking glibc-ports-2.4.tar.bz2 ;-) ...                               [ ok ]
 * checking glibc-libidn-2.4.tar.bz2 ;-) ...                              [ ok ]
 * checking glibc-2.4-patches-1.17.tar.bz2 ;-) ...                        [ ok ]
 * checking glibc-linuxthreads-20060605.tar.bz2 ;-) ...                   [ ok ]
 * checking glibc-powerpc-cpu-addon-v0.01.tgz ;-) ...                     [ ok ]
 * glibc-2.4 is nptl-only!
 * NPTL requires a CHOST of i486 or better

!!! ERROR: sys-libs/glibc-2.4-r3 failed.
Call stack:
  ebuild.sh, line 1562:   Called dyn_setup
  ebuild.sh, line 665:   Called pkg_setup
  glibc-2.4-r3.ebuild, line 1087:   Called die

!!! please add USE='nptl nptlonly' to make.conf
!!! If you need support, post the topmost build error, and the call stack if rel evant.


My CHOST is i386 and I do have nptl and nptlonly USE flags enabled (as reported by emerge --info, not on make.conf though).
Back to top
View user's profile Send private message
mark_alec
Bodhisattva
Bodhisattva


Joined: 11 Sep 2004
Posts: 6066
Location: Melbourne, Australia

PostPosted: Sun Oct 08, 2006 11:33 am    Post subject: Reply with quote

Moved from Other Things Gentoo to Portage & Programming. Couldn't see anything much unsupported.

For the CHOST error, read http://forums.gentoo.org/viewtopic-t-494147.html
_________________
www.gentoo.org.au || #gentoo-au
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Sun Oct 08, 2006 11:58 am    Post subject: Reply with quote

Nazgulled wrote:
* NPTL requires a CHOST of i486 or better


Quote:
My CHOST is i386


That's your problem.
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sun Oct 08, 2006 12:01 pm    Post subject: Reply with quote

that thread is pretty long but I read it all and found many links to other posts and there's too many opinions on what to do and there's lot of stuff I don't understand and I don't know what to do to fix this...

I just want to update my system and if possible not change the CHOST right now nor update to gcc 4.1.1 nor glibc, why can't I just leave this things how they are and update my system?

How can I do it without needing to change the CHOST?
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Sun Oct 08, 2006 12:24 pm    Post subject: Reply with quote

YOU CAN'T

NPTL requires at least a 486. And i386 CHOST only guarentees that you are doing instructions that will run on a 386.
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sun Oct 08, 2006 1:19 pm    Post subject: Reply with quote

sorry, but... what's NPTL?

I guess my only option is to upgrade to gcc 4.1.1 (already blocked glibc 2.4) emerge -e system, emerge -e world and then unblock glibc 2.4 and change CHOST according to this guide: http://dev.gentoo.org/~amne/temp/change-chost.xml.

Is this enough?
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Sun Oct 08, 2006 2:05 pm    Post subject: Reply with quote

native posix threading library

It's a replacement for LinuxThreads.
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Sun Oct 08, 2006 2:09 pm    Post subject: Reply with quote

Nazgulled wrote:
I guess my only option is to upgrade to gcc 4.1.1 (already blocked glibc 2.4) emerge -e system, emerge -e world and then unblock glibc 2.4 and change CHOST according to this guide: http://dev.gentoo.org/~amne/temp/change-chost.xml.

Is this enough?


I think you should do it in a different order:
1) Upgrade gcc
2) Unblock glibc 2.4
3) Change CHOST
4) Then do "emerge -e system && emerge -e world"
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Sun Oct 08, 2006 2:57 pm    Post subject: Reply with quote

But the gcc upgrading guide tells me to emerge system and world after the gcc upgrade.

Should I just do the following step from gcc upgrade guide:

Quote:
# emerge -uav gcc

(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
version and CHOST settings you've upgraded to:)
# gcc-config i686-pc-linux-gnu-4.1.1
# env-update && source /etc/profile

If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
example) you will have to run fix_libtool_files.sh manually
# fix_libtool_files.sh 3.4.6

(Rebuilding libtool)
# emerge --oneshot -av libtool


Then go to point 2 in your last post and follow from there?
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Mon Oct 09, 2006 3:59 am    Post subject: Reply with quote

Nazgulled wrote:
But the gcc upgrading guide tells me to emerge system and world after the gcc upgrade.


if you update glibc you should also emerge system and world because everything should be rebuilt to utilize the new c library
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Mon Oct 09, 2006 6:35 am    Post subject: Reply with quote

Nazgulled wrote:
Should I just do the following step from gcc upgrade guide:

Quote:
# emerge -uav gcc

(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
version and CHOST settings you've upgraded to:)
# gcc-config i686-pc-linux-gnu-4.1.1
# env-update && source /etc/profile

If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
example) you will have to run fix_libtool_files.sh manually
# fix_libtool_files.sh 3.4.6

(Rebuilding libtool)
# emerge --oneshot -av libtool


Then go to point 2 in your last post and follow from there?


That would probably work.

edit: except the "change CHOST" step really should be "change CHOST and follow steps mentioned in the CHOST-changing thread"
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Mon Oct 09, 2006 1:17 pm    Post subject: Reply with quote

By CHOST-changing thread you mean this guide: http://dev.gentoo.org/~amne/temp/change-chost.xml ?

Cause that's what I was using to change the CHOST...
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Mon Oct 09, 2006 10:39 pm    Post subject: Reply with quote

I was at the this step: Code Listing 2.10: Verifying refernces to the old CHOST are removed on the above guide and I got this:

Code:
nazbox gcc # grep -r 386 /etc/env.d/
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardened.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednossp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednopie.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednopiessp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardened.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednossp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednopie.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednopiessp.specs"
/etc/env.d/java/20blackdown-jdk-1.4.2.03:ADDLDPATH="${JAVA_HOME}/jre/lib/i386/:${JAVA_HOME}/jre/lib/i386/native_threads/:${JAVA_HOME}/jre/lib/i386/client/:${JAVA_HOME}/jre/lib/i386/server/"
/etc/env.d/java/20blackdown-jre-1.4.2.03:ADDLDPATH="/opt/blackdown-jre-1.4.2.03/lib/i386/:/opt/blackdown-jre-1.4.2.03/lib/i386/server/"
/etc/env.d/20java:LDPATH="/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/native_threads/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/client/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/server/"


I don't know what to do right now...
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Tue Oct 10, 2006 3:38 am    Post subject: Reply with quote

You must've skipped the earlier steps. The earlier steps tell you to remove those files (once you've verified that the 686 files have been created).

Code Listing 2.5: Removing the files with incorrect references

# rm 05gcc-i386-pc-linux-gnu

edit:
And remember that it's telling you to remove THE FILES that have the old references. Not just the file referred to in the code listing (because this code listing is based on the earlier one in the guide that only shows this one file having the old references).
Back to top
View user's profile Send private message
Nazgulled
Guru
Guru


Joined: 04 Aug 2005
Posts: 485

PostPosted: Tue Oct 10, 2006 10:25 am    Post subject: Reply with quote

But I havent' skipped any steps, I did everything as the guide told me to do. However, none of those files were found during the earlier steps and that's why I don't understand why I got all those results...

Doing this:

# rm 05gcc-i386-pc-linux-gnu

I get a file not found error...
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Tue Oct 10, 2006 6:38 pm    Post subject: Reply with quote

I'm sorry I don't know what to say. Never had to use that guide myself.

It might be (due to spending so much time trying to figure this out) quicker just to backup any important data and wipe the partition then use an i686 tarball for a reinstall.
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3053
Location: Redmond, WA

PostPosted: Tue Oct 10, 2006 6:45 pm    Post subject: Reply with quote

Nazgulled wrote:
I was at the this step: Code Listing 2.10: Verifying refernces to the old CHOST are removed on the above guide and I got this:

Code:
nazbox gcc # grep -r 386 /etc/env.d/
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardened:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardened.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednossp:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednossp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopie:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednopie.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:LDPATH="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.4.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.4.6-hardenednopiessp:GCC_SPECS="/usr/lib/gcc/i386-pc-linux-gnu/3.4.6/hardenednopiessp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardened:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardened.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednossp:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednossp.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopie:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednopie.specs"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:PATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:LDPATH="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:MANPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/man"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:INFOPATH="/usr/share/gcc-data/i386-pc-linux-gnu/3.3.6/info"
/etc/env.d/gcc/i386-pc-linux-gnu-3.3.6-hardenednopiessp:GCC_SPECS="/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6/hardenednopiessp.specs"
/etc/env.d/java/20blackdown-jdk-1.4.2.03:ADDLDPATH="${JAVA_HOME}/jre/lib/i386/:${JAVA_HOME}/jre/lib/i386/native_threads/:${JAVA_HOME}/jre/lib/i386/client/:${JAVA_HOME}/jre/lib/i386/server/"
/etc/env.d/java/20blackdown-jre-1.4.2.03:ADDLDPATH="/opt/blackdown-jre-1.4.2.03/lib/i386/:/opt/blackdown-jre-1.4.2.03/lib/i386/server/"
/etc/env.d/20java:LDPATH="/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/native_threads/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/client/:/opt/blackdown-jdk-1.4.2.03/jre/lib/i386/server/"


I don't know what to do right now...


Dude, you didn't even read the whole step:

Quote:
Code Listing 2.10: Verifying refernces to the old CHOST are removed

# grep -r 386 /etc/env.d/

If you still find something, you must have missed some file, try to track it down before going on.



Note the last sentence.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
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