LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions
User Name
Password
Linux - Distributions This forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on... Note: An (*) indicates there is no official participation from that distribution here at LQ.

Notices

Reply
 
Search this Thread
Old 01-16-2008, 02:05 AM   #1
ade05fr
LQ Newbie
 
Registered: Sep 2007
Location: Metz - France
Distribution: Gentoo
Posts: 16

Rep: Reputation: 0
Question GENTOO : emerge PORTAGE Failed due to sandbox


Hello everyone,

since one month i cannot emerge portage portage with my gentoo 2007-1 version.
I've tried to compil sandbox with a simple 'emerge sandbox' but i have the same error.

does anyone know how to solve my problem ?

Here is the compil error :
ULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:686: warning: implicit
declaration of function 'true_getcwd_DEFAULT'
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:686: warning: return
makes pointer from integer without a cast
make[2]: *** [libsandbox_la-wrappers.lo] Erreur 1
make[2]: *** Attente des tâches non terminées....
make[1]: *** [all-recursive] Erreur 1
make: *** [all] Erreur 2

* Building failed for ABI=x86!. This usually means a broken
* multilib setup. Please fix that before filling a bugreport
* against sandbox.

*
* ERROR: sys-apps/sandbox-1.2.20_alpha2-r1 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 2449: Called die
* The specific snippet of code:
* diefunc "$FUNCNAME" "$LINENO" "$?" "emake failed for
${ABI}"
* The die message:
* emake failed for x86
*
* If you need support, post the topmost build error, and the call stack
if relevant.
* A complete build log is located at
'/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/environment'.
*

* Messages for package sys-apps/sandbox-1.2.20_alpha2-r1:

* If configure fails with a 'cannot run C compiled programs' error, try
this:
* FEATURES=-sandbox emerge sandbox
* Building failed for ABI=x86!. This usually means a broken
* multilib setup. Please fix that before filling a bugreport
* against sandbox.
*
* ERROR: sys-apps/sandbox-1.2.20_alpha2-r1 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 2449: Called die
* The specific snippet of code:
* diefunc "$FUNCNAME" "$LINENO" "$?" "emake failed for
${ABI}"
* The die message:
* emake failed for x86
*
* If you need support, post the topmost build error, and the call stack
if relevant.
* A complete build log is located at
'/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/environment'.
 
Old 01-17-2008, 02:09 AM   #2
ade05fr
LQ Newbie
 
Registered: Sep 2007
Location: Metz - France
Distribution: Gentoo
Posts: 16

Original Poster
Rep: Reputation: 0
here is a full update of my error compilation
gcc -DHAVE_CONFIG_H -I. -I../../sandbox-1.2.20alpha2/libsandbox -I.. -I../../sandbox-1.2.20alpha2/libsbutil -I../../sandbox-1.2.20alpha2/libsbutil/include -DETCDIR=\"/etc\" -DLIBSANDBOX_PATH=\"/usr/lib32\" -DSANDBOX_BASHRC_PATH=\"/usr/share/sandbox\" -DPIC -fPIC -D_REENTRANT -I../../sandbox-1.2.20alpha2 -Wall -fexceptions -O2 -march=x86-64 -pipe -MT libsandbox_la-wrappers.lo -MD -MP -MF .deps/libsandbox_la-wrappers.Tpo -c ../../sandbox-1.2.20alpha2/libsandbox/wrappers.c -fPIC -DPIC -o .libs/libsandbox_la-wrappers.o
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c: In function 'libsb_open':
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:673: error: 'true_open_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:673: error: (Each undeclared identifier is reported only once
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:673: error: for each function it appears in.)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:673: error: 'symname_open_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:673: error: 'symver_open_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:675: warning: implicit declaration of function 'true_open_DEFAULT'
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c: In function 'libsb_getcwd':
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:684: error: 'true_getcwd_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:684: error: 'symname_getcwd_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:684: error: 'symver_getcwd_DEFAULT' undeclared (first use in this function)
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:686: warning: implicit declaration of function 'true_getcwd_DEFAULT'
../../sandbox-1.2.20alpha2/libsandbox/wrappers.c:686: warning: return makes pointer from integer without a cast
make[2]: *** [libsandbox_la-wrappers.lo] Erreur 1
make[2]: *** Attente des tâches non terminées....
make[1]: *** [all-recursive] Erreur 1
make: *** [all] Erreur 2

* Building failed for ABI=x86!. This usually means a broken
* multilib setup. Please fix that before filling a bugreport
* against sandbox.

*
* ERROR: sys-apps/sandbox-1.2.20_alpha2-r1 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 2448: Called die
* The specific snippet of code:
* diefunc "$FUNCNAME" "$LINENO" "$?" "emake failed for ${ABI}"
* The die message:
* emake failed for x86
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/environment'.
*

* Messages for package sys-apps/sandbox-1.2.20_alpha2-r1:

* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Building failed for ABI=x86!. This usually means a broken
* multilib setup. Please fix that before filling a bugreport
* against sandbox.
*
* ERROR: sys-apps/sandbox-1.2.20_alpha2-r1 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 2448: Called die
* The specific snippet of code:
* diefunc "$FUNCNAME" "$LINENO" "$?" "emake failed for ${ABI}"
* The die message:
* emake failed for x86
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-1.2.20_alpha2-r1/temp/environment'.
 
Old 01-18-2008, 01:48 PM   #3
ade05fr
LQ Newbie
 
Registered: Sep 2007
Location: Metz - France
Distribution: Gentoo
Posts: 16

Original Poster
Rep: Reputation: 0
Solved, i've removed /etc/portage/package.unmask and now it's working fine again. :-)
 
Old 01-31-2008, 04:50 PM   #4
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Quote:
Originally Posted by ade05fr View Post
Solved, i've removed /etc/portage/package.unmask and now it's working fine again. :-)
I am just installing Gentoo AMD64. "emerge portage" fails on sandbox. It says something about FEATURES="-sandbox emerge sandbox". I think I was supposed to add that to my /etc/make.conf (the output doesn't actually say where to edit this). But here's the output that I'm getting from "emerge portage":

*************************************************************************
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log

!!! ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 3347: Called src_compile
sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
ebuild.sh, line 577: Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
*************************************************************************
That was the original output. So I edited /etc/make.conf as stated and ran it again. This is what I get now.

*************************************************************************
If you meant to cross compile, use `--host'.
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log

!!! ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 3347: Called src_compile
sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
ebuild.sh, line 577: Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.

I don't know why it says anything about cross-compiling. I just want to update my system as I was told to do after running my first "emerge --sync".

Why am I getting this, when my /etc/make.conf is setup for x86_64? Where can I change this to ABI=X86_64? Or should I?

On further examination, it seems it should be ABI=amd64. But I have that already set. Should I not have installed the multilib stage3 or not?
*************************************************************************
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu

Shingoshi

Last edited by Shingoshi; 01-31-2008 at 05:34 PM.
 
Old 02-05-2008, 05:57 PM   #5
Emerson
Senior Member
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~
Posts: 3,177

Rep: Reputation: Disabled
You have to set it for one-time only

FEATURES="-sandbox -usersandbox" emerge -av sandbox
 
Old 02-06-2008, 12:00 AM   #6
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Please tell me exactly how to do this.

Quote:
Originally Posted by Emerson View Post
You have to set it for one-time only

FEATURES="-sandbox -usersandbox" emerge -av sandbox
All of my guesswork isn't working. Am I supposed to put this in make.conf or not? What exactly am I supposed to run on the command line? Look at the line which you wrote carefully, and tell me if it is written as it should be. Because I am getting nothing but errors whenever I try to use this. Is there supposed to be a space between user and sandbox? Should that line have been written as:

make.conf << FEATURES="-sandbox -user sandbox"
commandprompt: emerge -av sandbox

Please think for a moment. If I knew what I was supposed to be doing, I wouldn't be asking for help. So please don't assume that I should know what I am doing, because I don't!

I haven't been able to get Gentoo to run once. So I have absolutely no experience at this. I need to know how to get my system up and running. Once I have a working system, I can then learn the intricacies of it. But right now, I need it to run.

Shingoshi
 
Old 02-06-2008, 01:00 AM   #7
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Just a few more questions.

I put this message in the wrong place. Sorry about that!

Shingoshi

Last edited by Shingoshi; 02-06-2008 at 03:28 AM.
 
Old 02-06-2008, 07:22 AM   #8
Emerson
Senior Member
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~
Posts: 3,177

Rep: Reputation: Disabled
This is the exact command line, no mistakes, use it as root.

Code:
FEATURES="-sandbox -usersandbox" emerge -av sandbox
This overrides your environment variable FEATURES set elsewhere and executes emerge command.
 
Old 02-06-2008, 11:46 PM   #9
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
This is what happens when I run the command as stated.

Quote:
Originally Posted by Emerson View Post
This is the exact command line, no mistakes, use it as root.

Code:
FEATURES="-sandbox -usersandbox" emerge -av sandbox
This overrides your environment variable FEATURES set elsewhere and executes emerge command.
If I say yes to the prompt, I get this:
starbase64 / # FEATURES="-sandbox -usersandbox" emerge -av sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17] 0 kB

Total: 1 package (1 upgrade), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] Yes

>>> Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to /
* sandbox-1.2.18.1.tar.bz2 RMD160 ;-) ... [ ok ]
* sandbox-1.2.18.1.tar.bz2 SHA1 ;-) ... [ ok ]
* sandbox-1.2.18.1.tar.bz2 SHA256 ;-) ... [ ok ]
* sandbox-1.2.18.1.tar.bz2 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking sandbox-1.2.18.1.tar.bz2 ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work
* Applying sandbox-1.2.18.1-open-normal-fail.patch ... [ ok ]
* Applying sandbox-1.2.18.1-open-cloexec.patch ... [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log

!!! ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 3346: Called src_compile
sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
ebuild.sh, line 577: Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.

starbase64 / #

If I say no to the prompt, I get this:
starbase64 / # FEATURES="-sandbox -usersandbox" emerge -av sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17] 0 kB

Total: 1 package (1 upgrade), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] No

Quitting.

starbase64 / #

In either case, I get nothing that helps me move beyond this point. I am simply hung at the build of the sandbox. I cannot proceed any further. So what should I do now? Remove this environment and use multilib without hardening? Can I change the profile, so that hardened status is no longer in effect? Because trying to keep things as they are, isn't working.

This is a bug that was claimed to have been fixed. It isn't.

Shingoshi
 
Old 02-07-2008, 07:58 AM   #10
Emerson
Senior Member
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~
Posts: 3,177

Rep: Reputation: Disabled
Remove all cruft from /var/tmp/portage and try again?
 
Old 02-08-2008, 02:28 AM   #11
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Quote:
Originally Posted by Emerson View Post
:twocents: Remove all cruft from /var/tmp/portage and try again?
I've done that, and nothing is better than it was before. I am getting the same error messages as before. I am beginning to think Gentoo is the cruft. Why can't I eliminate any attempt to upgrade the sandbox? Because the suggestions given so far, don't work. I have even tried emerge --unmerge sandbox. That didn't help either.

What's the problem here. That I am attempting to run multilib, hardened or both? Does it matter that I'm running Gentoo in a chroot? I don't see why it should, since I am fully able to run NetBSD pkgsrc in a chroot.

Forget everything else. Just tell me how to change the profile I am running, so that multilib hardened doesn't prevent me from running my system. I'd rather have a running system, than some flaky features that aren't ironed out. And they are indeed flaky, since I have seen many bug reports on this issue. So my situation is not unique.

Shingoshi
 
Old 02-08-2008, 02:44 AM   #12
billymayday
Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
I had all sorts of sandbox problems on Gentoo. The response I got to a slightly different problem on the Gentoo forum was:

Quote:
looks like your sandbox is broken. You have to go in and

emerge --oneshot sandbox

and theres a chance it might not work. so you might have to go into your make.conf and set
FEATURES="-sandbox"
then emerge --oneshot sandbox
then it should work better for you
Give it a go - can't hurt (I hope)
 
Old 02-08-2008, 07:26 AM   #13
Emerson
Senior Member
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~
Posts: 3,177

Rep: Reputation: Disabled
Use eselect profile list to see common profiles. Profiles are stored in /usr/portage/profiles/, to use them symlink desired one to /etc/make profile.

/etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2007.0

If you have working sandbox you can skip the build in emerge -e system/world process, use emerge --skipfirst, you can even come back after emerge -e is finished and try again, it may build then.
You can also live without sandbox, to turn it off permanently add FEATURES="-sandbox" to your make.conf.


@billymayday
Setting FEATURES in make.conf has same effect as setting it from command line. Actually command line overrides everything else. -oneshot option does not change anything in build process, the only difference it makes is package is not stored in world file.
 
Old 02-08-2008, 02:28 PM   #14
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Quote:
Originally Posted by Emerson View Post
Use eselect profile list to see common profiles. Profiles are stored in /usr/portage/profiles/, to use them symlink desired one to /etc/make profile.

/etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2007.0

If you have working sandbox you can skip the build in emerge -e system/world process, use emerge --skipfirst, you can even come back after emerge -e is finished and try again, it may build then.
You can also live without sandbox, to turn it off permanently add FEATURES="-sandbox" to your make.conf.
Thank you!!!

I have changed my profile to: ../usr/portage/profiles/default-linux/amd64/2007.0

I also had to run "emerge --skipfirst". Without this, sandbox kept asserting itself. I'm now running "emerge kde". So that's 165 packages going to be to be installed.

Shingoshi

Last edited by Shingoshi; 02-08-2008 at 02:38 PM.
 
Old 02-08-2008, 02:38 PM   #15
Emerson
Senior Member
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~
Posts: 3,177

Rep: Reputation: Disabled
You are welcome!
For a desktop you may want .../profiles/default-linux/amd64/2007.0/desktop
It really isn't very important, it just gives different USE flag set to begin with.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Graphical Portage/Emerge GUI (Gentoo) BuckRogers01 Gentoo 37 06-03-2008 08:49 AM
Gentoo emerge howto do ./configure --options-stuff via portage humbletech99 Linux - Distributions 7 05-08-2008 05:06 AM
Can't emerge gnome on gentoo due to ffmpeg plugins aeruzcar Linux - Software 3 07-02-2006 11:55 AM
emerge,portage, upgrading gentoo confusion darkangel29 Linux - Newbie 2 06-03-2006 10:53 AM
KANOTIX , walkthough for installing gentoo portage & emerge on debian pure sid MaximalSbcYahoo Debian 2 04-01-2006 04:10 PM


All times are GMT -5. The time now is 02:10 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration