gtoaster emerge error

lego · n00b Joined: 28 Jun 2003 Posts: 3 Location: Portugal

I've been trying to emerge gtoaster for a couple of days,and i get a 'too many open files' error every time it builds.

I've removed temp bz2's, changed CFLAGS to -02, etc, but it seems to endlessly repeat the same command until the system open files limit is exceeded???

If you know of a quick fix please help me. If needed i can try to build it again and post the complete error screen in here.

Thx a lot

simonbh · n00b Joined: 24 Sep 2002 Posts: 28

I alsa am having that problem, and submitted a bug for it:

https://bugs.gentoo.org/show_bug.cgi?id=26651

slarti` · Retired Dev Joined: 20 Sep 2003 Posts: 376 Location: UK

I'm getting the same problem as well. I've tried similar things to what you have done, also tried emerging beta5 as well as beta6. No luck

_________________
Gentoo/AMD64, shell-tools, net-mail, vim, recruiters
IRC: slarti @ irc.freenode.net
Devspace

U4EA · n00b Joined: 13 Oct 2003 Posts: 11

Same here as well, flips into an infinite loop.

I'm at my work computer, I'll try and post more information when I head home.

slarti` · Retired Dev Joined: 20 Sep 2003 Posts: 376 Location: UK

Similar problem when emerging gnomba for me. Does anyone else with the probs compiling gtoaster get the same sort of problem?
_________________
Gentoo/AMD64, shell-tools, net-mail, vim, recruiters
IRC: slarti @ irc.freenode.net
Devspace

frippz · Guru Joined: 22 Aug 2002 Posts: 460 Location: Sweden

So if I understand the bugreport right, we who use the 2.6-kernel either have to switch to a 2.4-kernel (wich I refuse to do since I need the SATA-support for my disk) or make an emerge -e world (wich never works for me since it stops a portage and then starts over in an infite emerge loop).

slarti` · Retired Dev Joined: 20 Sep 2003 Posts: 376 Location: UK

Well, I just had a fresh system this morning after wiping windows.

I only ever emerge development-sources. Nothing else.

I tried emerging gtoaster and it still looped.
_________________
Gentoo/AMD64, shell-tools, net-mail, vim, recruiters
IRC: slarti @ irc.freenode.net
Devspace

darksaidin · Apprentice Joined: 04 Oct 2003 Posts: 150

I have a clean 2.6 system on a HDD that has never even seen a 2.4 kernel. I am clearly compiling against the right 2.6 headers.

Why has the bug been set to resolved? It is clearly not.

frippz · Guru Joined: 22 Aug 2002 Posts: 460 Location: Sweden

I agree. My system is also running purely on a 2.6-kernel.
There can't be any traces of old kernel headers then, right?

darksaidin · Apprentice Joined: 04 Oct 2003 Posts: 150

Maybe it's an attempt to get into the "most-bugs-resolved" top 10

asiobob · Posted: Sun Dec 14, 2003 1:35 pm Post subject:

bah
I hae this problem as well,
fresh gentoo install, 2.6test11

drb · Posted: Mon Dec 22, 2003 5:09 pm Post subject:

Same problem here on both of my systems, one running development-sources-2.6.0, the other running gentoo-sources-2.4.20-r9.

I don't think that this problem is kernel related.
_________________
Darrell Bellerive
VA7TO

crackotter · n00b Joined: 23 Dec 2003 Posts: 17

I still have the problem on my side. Fresh laptop install with the dev-sources. How come the bug-id was closed?

-The Otter

asiobob · Posted: Tue Dec 23, 2003 10:29 pm Post subject:

I ended up installing K3B

Murf · n00b Joined: 28 Oct 2003 Posts: 19

I'm getting the same exact error myself...do we need to open another bug report????

Running 2.6.0 gentoo sources. Just loops for eternit....

asiobob · Posted: Thu Dec 25, 2003 8:26 am Post subject:

last time I checked (a while back) the bug report was closed on the grounds it wasn't a bug, might be worth opening again, sure looks like a bug to me

charlesg3 · n00b Joined: 04 Dec 2003 Posts: 14 Location: Boulder, Co

has anyone found a resolution to this problem?

Oatmeal · n00b Joined: 17 Dec 2003 Posts: 46

blubber · Posted: Fri Jan 09, 2004 11:44 am Post subject: Solution

Hi all, I had the same problem, but I solved it by booting from the live cd, chrooting and then emerging gtoaster. I've build two binary packes for everyone who doesn't want to chroot

. They can be found here:
Athlon
i586

I've build a generic i586 package and an athlon packed. Just copy the appropriate package to ${PKGDIR}/All/gtoaster-1.0_beta6.tbz2. And emerge -K gtoaster.
You only need the one package that is suitable for your system, and you need to rename it to gtoaster-1.0_beta6.tbz2. If you did not change portage's defaults then ${PKGDIR} = /usr/portage/packages.

Dr_Claw · n00b Joined: 26 Dec 2003 Posts: 8 Location: en_GB

Hey all,

Yet another person here who had the same problem - Gtoaster gets stuck in a loop when trying to compile. Using kernel 2.6.1-gentoo here on my laptop.

Solved it (well, worked around it) by simply rebooting into my old kernel (2.4.20-gentoo-r9), emerged it without any problems, booted back into 2.6 and it seems to load and work without a problem. How strange. There's obviously a problem somewhere, but if you have a 2.4 kernel lying around in your /boot, it's fairly easy to work around it for now, with the only expense being that of sacrificing your uptime...

kwetz · Posted: Mon Jan 12, 2004 12:55 am Post subject:

Thanks for a way around the loop till it pukes problem with 2.6 kernels. I'll download a copy of the live CD ( on a windows machine GASP ) and build myself a 686 copy .

RE Hi all, I had the same problem, but I solved it by booting from the live cd, chrooting and then emerging gtoaster.

boonwee · n00b Joined: 11 Jan 2004 Posts: 32

i encountered the same error when emerging gtoaster. then i searched and saw this thread.

i bootup with the livecd, chrooted and emerge gtoaster without any problems.

raker · Posted: Sat Jan 24, 2004 5:04 am Post subject: more info...

the configure script doesn't understand what a 2.6 kernel is, therefore the looping... i have tried fixing it a couple times... cleaning up a multitude of other strange things as well... but still no luck. re-autoconf,automake, etc... modifying the .in files... blah...

BTW, those of you will 2.6 kernels... are still compiling against 2.4 headers UNLESS you physically copied or linked your /usr/include/linux and /usr/include/{asm,asm-generic} to the 2.6 kernel...

sys-kernel/linux-headers pushes modified 2.4 kernel headers into /usr/include/asm and /usr/include/linux otherwise