libstdc++-v3-3.3.4 compile error on qube2

E-Werk

hi

i tried to install gentoo on the cobalt qube2 with the help of kumba and the "testing" thread
...thanks to all nerds working out things on that platform

i have colo booting and using the netboot kernel provided by kumba.
it is not netbooting !! the machine can come up by itself and also is starting ssh.
i then tried to emerge world and it started withe many packages
... but failed to compile the big ones like libstdc++,glibc and the kernel (mips sources 2.4.27)....
i skipfirst resumed the update till all possible packs where emerged and compiled ....
so i ended with 6 ebuilds that didnt make it

Astral · n00b Joined: 17 Nov 2003 Posts: 19 Location: Mo, USA

For the kernel patches, just make sure you have the correct keyword in your make.conf, here is mine taken from kumba's tutorial:

USE="-* cobalt apache mysql mips ssl"

That will then cause portage to emerge and apply all cobalt patches for the kernel. The -* turns everything off, then I turn on what I want.

Kumba · Posted: Fri Dec 24, 2004 9:25 am Post subject:

(Must've missed this thread)

libstdc++-v3 is no longer used on mips, but it's a known fact that 3.3.4 doesn't build w/ a 3.4.x compiler. I think a few have hit this on sparc under the sparc64/gcc34 profile too. Not much I can do to fix it, I never used libstdc++-v3.

Kernel wise, just make sure you're using the cobalt profile (/usr/portage/profiles/default-linux/mips/cobalt/2004.2), and have "cobalt" in USE in make.conf.

One day, we'll get the docs updated, either when I get over this writer's block, or we get a docs dev.

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

crahen · n00b Joined: 11 Jan 2004 Posts: 51

I'm seeing the same error trying to upgrade coreutils, gcc or glibc using a 3.3 compiler. Are there similar issues with that compiler as well?

Kumba · Posted: Fri Dec 24, 2004 9:42 am Post subject:

Put one way, gcc-3.3.x is just plain "yesterday". We've been using 3.4 on mips rather successfully for awhile now, and it's needed to run code on Origin/Octane systems (C++ code, that is). The last 3.3.x that I remember working well was 3.3.4, but I used that briefly on one machine before kicking it over to 3.4.

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

crahen · n00b Joined: 11 Jan 2004 Posts: 51

I understand 3.3 is out of date. My question is really about how to get myself kicked over to 3.4. I'm compiling on te Qube itself and not succeeding - are you cross compiling? How did you avoid this error?

Kumba · Posted: Fri Dec 24, 2004 11:08 pm Post subject:

Sounds a little like your binutils is shot. Hard to say, given that's an error I've not encountered, I can't concretely say for sure what the possible cause is.

What CFLAGS are you using, and are you using any additional flag settings, like LDFLAGS? If needed, I can post bin-packages of the running binutils/glibc/gcc on my raq2 that might have a better chance of working right than your build attempts.

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

crahen · n00b Joined: 11 Jan 2004 Posts: 51

CFLAGS="-O2"
USE="-* mips cobalt"

I've tried various other combinations but I can't get around that error.
It seems to me like it is something that needs a patch in the glibc and coreutils sources, ... data being defined in the wrong part of the binaries or something; I didnt look at the sources too closely

Redhatter · Posted: Sun Dec 26, 2004 7:32 am Post subject:

Is it worth perhaps trying a µClibc-based userland?

If binutils/gcc is giving troubles, it might be worth trying to re-emerge those first, and see if you can fix the broken userland, but otherwise, µClibc might just avoid some of the bugs (and bloat) that's in glibc.
_________________
Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...

Gentoo/MIPS Cobalt developer, Mozilla herd member.

crahen · n00b Joined: 11 Jan 2004 Posts: 51

I've already re-emerged binutils and gcc, but I still encounter that error. I'm pretty glibc needs a patch to fix it.

I'd give ulibc a shot, but I need to qube up and running and I've only got one - so I can't really expirement too much with it at the moment. I'm not sure how much actually will continue to work if I replace glibc.

Kumba · Posted: Wed Dec 29, 2004 2:26 am Post subject:

You'll need to start from scratch if you want to goto uClibc. One of our embedded devs I believe runs such a setup on the Cobalt hardware, but I'm not entirely sure. You might consider joining #gentoo-mips on irc.freenode.net for further help (where we hang around more). If you do join, try not to be too scared off by some of the devs, we can be a little harsh to people who ask the wrong "type" of question :)

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic