Gentoo/MIPS Cobalt: n32 Stages just a little closer to reality…
Hi All…
Yep, I dusted off my n32 chroot again this morning (it’s 1:22am as I type this), determined to talk some sense into Portage. I figured I’d give it one last time before I invested the time into trying out Paludis (which I may still do yet, I’m hearing lots of good things about it).
So, what’s been holding me up? Well, the issue has been this nagging bug that I couldn’t figure out. Cobalt doesn’t have any n32 stages, let alone NPTL n32 stages. For the most part, I was able to nick the settings out of default-linux/mips/2006.1/generic-be/n32/* copying this into the default-linux/mips/2006.1/cobalt/ directory, and replacing mips64 with mips64el in the CHOST variable.
This worked quite well, but there was still one nagging issue that cropped up when trying to compile various packages, particularly portage itself:
These are the packages that would be merged, in order: Calculating dependencies... done! Traceback (most recent call last): File "/usr/bin/emerge", line 3316, in ? mydepgraph.display(mydepgraph.altlist()) File "/usr/bin/emerge", line 1650, in display verboseadd += create_use_string(key.upper(), cur_iuse_map[key], cur_use_map[key], KeyError: 'elibc'
On further investigation, I noticed that on all the working environments, there was a USE-expand flag: elibc_glibc. This is susposedly set in the base profile, but for whatever reason, my sub-profile transplant seems to have lopped this flag off. Portage would see this, and b0rk when it didn’t know which libc to use. Thus, I tried something… I hacked around it by setting USE=”elibc_glibc” in /etc/make.conf then gave it another try. Sure enough, emerge –info now listed the illusive USE flag, and packages started compiling once more.
Right now, I’m rebuilding all the system packages in my chroot (which also has lib64 stuff floating in it). This will hopefully get me to the point of producing a first seed-stage for Catalyst, and will allow stagebuilds to be done for n32 at long last. As for n64? Well, time will tell… it’s certainly a possibility. I’d like to first discover why this USE flag is getting dropped… as setting it in make.conf is not an acceptable workaround IMHO, but it’s better than nothing.
I shall keep you all posted on my progress. ![]()

Leave a Reply