[SOLVED] Gentoo begginers problems on Sony VAIO-VGN-NW21MF emerge portage failed

artur13 · 12-27-2009, 12:51 PM

Hello Dear Community,
This is my first post on this forum so probably i should first tell a few words about me. I am just starting the adventure with linux and I will try to do it with Gentoo. For now I don't have any knowledge about linux system but I really want to learn sth and I think the Gentoo is the best way to get familiar with linux concepts in general. I;m trying to build "professional dektop". I tried Ubuntu but I don't like when I have a dozens of packages that I will never use and obviously there is no fun.Ok i think this is enough

I am installing it from stage3 for i686 and doing the same as it is written in the handbook but I am not able to do emerge portage. Im chrooting from ubuntu 9.10. Here is my make.conf

Code:

CFLAGS="-O2 -march=i686 -pipe"
CXXFLAGS="-O2 -march=i686 -pipe"
CHOST="i686-pc-linux-gnu"
GENTOO_MIRRORS="http://gentoo.prz.rzeszow.pl "
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
MAKEOPTS="-j3"
ACCEPT_KEYWORDS="~x86"
EMERGE_DEFAULT_OPTS="--ask --verbose"

And here is the output from the command

Code:

ubuntu / # emerge portage

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

Calculating dependencies... done!
[ebuild     U ] sys-apps/portage-2.1.7.16 [2.1.6.13] USE="-build -doc -epydoc -python3% (-selinux)" LINGUAS="-pl" 0 kB

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

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

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-apps/portage-2.1.7.16
openpty failed: 'out of pty devices'
 * portage-2.1.7.16.patch.bz2 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * portage-2.1.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking portage-2.1.7.16.patch.bz2 to /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Unpacking portage-2.1.7.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Source unpacked in /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Preparing source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
 * Applying portage-2.1.7.16.patch ...                                    [ ok ]
 * Setting portage.VERSION to 2.1.7.16 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-apps/portage-2.1.7.16

>>> Install portage-2.1.7.16 into /var/tmp/portage/sys-apps/portage-2.1.7.16/image/ category sys-apps
patching file make.conf
rm: cannot remove directory `/var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7/bin/ebuild-helpers/3': Directory not empty
/usr/lib/portage/bin/ebuild-helpers/doexe: at least one argument needed
 * 
 * ERROR: sys-apps/portage-2.1.7.16 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_install
 *             environment, line 3337:  Called die
 * The specific snippet of code:
 *           doexe $(find . -mindepth 1 -maxdepth 1 -type f ! -type l) || die "doexe failed";
 *  The die message:
 *   doexe 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/portage-2.1.7.16/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.1.7.16/temp/environment'.
 * 

>>> Failed to emerge sys-apps/portage-2.1.7.16, Log file:

>>>  '/var/tmp/portage/sys-apps/portage-2.1.7.16/temp/build.log'

 * Messages for package sys-apps/portage-2.1.7.16:

 * 
 * ERROR: sys-apps/portage-2.1.7.16 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_install
 *             environment, line 3337:  Called die
 * The specific snippet of code:
 *           doexe $(find . -mindepth 1 -maxdepth 1 -type f ! -type l) || die "doexe failed";
 *  The die message:
 *   doexe 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/portage-2.1.7.16/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.1.7.16/temp/environment'.

And here is the var file
Ohh it so huge:/ I hope that information i post above will be enough to slove the problem if not then i will post the var file. I'm doing emerge portage because command emerge --sync suggested it

Greetings,
Artur
P.S Mods- I choose to post it here because I don't think that is hard problem for sb who have a little experience with linux and for sure this is newbie question

markush · 12-27-2009, 01:46 PM

Quote:

Originally Posted by artur13

... and for sure this is newbie question

no, it isn't.

Hello artur13 and wellcome to LQ,

I don't understand where you are in the process of installing Gentoo. Please describe where on which step in the Handbook you are.

I see that your make.conf lacks any USE-flags.

Markus

artur13 · 12-27-2009, 03:24 PM

I am here

Code:

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6

Exactly 6.b. Configuring Portage. So far I am not familiar with USE flags but are they necessary to happily end installation process?
Thx for replay
Greetings
Artur

markush · 12-27-2009, 04:47 PM

Hello,

no, the USE-flags are not necessary but very useful. For example if you don't need support for ipv6 you may set

Code:

USE="-ipv6"

I'd also recommend to set the language in make.conf, I'm using

Code:

LINGUAS="de"

for Germany. Even if you only need english support, you should set "-nls" in the USE-flags (nls = national-language-support). This keeps the system smaller.

Ok, to your first question: your portage-version should be recent enough so that you do not have to emerge it at first. Provided you have successfully chrooted into the Gentoo-partition, you should run

Code:

emerge --sync

which will update the portage tree. Then you can do the configurations like described in the handbook. I'd recommend at least to take a look at the USE-flags and also make entries for VIDEO_CARD and INPUT_DEVICES.

Good luck

Markus

artur13 · 12-27-2009, 04:55 PM

Ok tomorrow I will try to get familiar myself with USE flags. I done emerge --sync and it was written that is higly suggested to run emerge portage first before any extra packages will be install. So may I ignore that and go on with documentation?
Greetings,
Artur,

markush · 12-27-2009, 05:03 PM

Well, I'd recommend to configure the system until

Code:

emerge system

and rebuilding the kernel.
Afterwards you may update the system and see if portage is updated correctly. I think it would be difficult to find a failure in an ebuild (or to find out if it is a failure in an ebuild or a configurationproblem) for a new Gentoo user. By the way, I'm running Gentoo amd64 and my portageversion is 2.1.6.13 and the latest available for my system. So it may not be a problem to use this version on your i686 system.

Markus

artur13 · 12-27-2009, 05:16 PM

So this error cannot be fixed easy way? I don't have kernel so far but emerge system is used to update system right? And this command does more less the same that emerge --newuse --update --deep world

markush · 12-27-2009, 05:28 PM

I don't know if this error can be fixed in an easy way. But I don't think that the version of portage is as important that one has to fix this problem at first. Maybe also that someone reads this thread who has an idea how to fix this error.

Well, emerge system emerges the ebuilds (builds and installs) the packages for the current portage-tree (which is up to date so far). The --newuse --update --deep options will perform an update. Normally on a new system both commands should have the same effect.

Markus

artur13 · 12-28-2009, 09:34 AM

A partition about 10GB will be enough for gentoo?

~sHyLoCk~ · 12-28-2009, 09:39 AM

Quote:

Originally Posted by artur13

A partition about 10GB will be enough for gentoo?

No way.

artur13 · 12-28-2009, 09:54 AM

How big partition have to be than?
Greetings
Artur

~sHyLoCk~ · 12-28-2009, 09:59 AM

Well just an example: If you compile open office it takes up more than 8 gigs of space, although there's a binary for Ooo, but assuming you want to compile many apps and would also like to save cached source packages I'd say around 20gigs minimum. this is no hard and fast rule, just a personal experience from my gentoo days. I would rather wait for a Gentoo user to come here and comment.

artur13 · 12-28-2009, 10:12 AM

So I can do 10gb for root and 10 gb for /usr?(This is the place where emerge put all files?)
Greetings
Artur

markush · 12-28-2009, 11:13 AM

Hello artur13,

I'd recommend to use one big partition for all and only /home on an extra partition.
Here is the output of df -h on my system:

Code:

Dateisystem          Größe Benut  Verf Ben% Eingehängt auf
/dev/sda1              30G   13G   16G  44% /
udev                   10M  220K  9,8M   3% /dev
/dev/sda5              20G   14G  5,7G  70% /home
/dev/sda6              60G   19G   38G  34% /usr/local/public
/dev/sda7              50G   24G   23G  52% /usr/local/music
/dev/sdb5              99G  649M   93G   1% /usr/local/backup
shm                   1,9G     0  1,9G   0% /dev/shm

This is a normal Gentoo-Desktop machine with Open Office and KDE4 (which I don't use because I'm running fvwm).
I'd further recommend to use ccache and set the size to 3GB (this resides in the /var directory).

Markus

markush · 12-29-2009, 08:32 AM

Hello Artur,

in the Gentoo-section of LQ someone had a similar issue with the installation and solved it. Look at this link:
http://www.linuxquestions.org/questi...-works-778461/

Markus