On Wed, Jul 05, 2006 at 05:04:00PM +0000, Duncan wrote:
> Have you run fix_libtool_files.sh recently? I'm asking because I see the
>
I always forget to run that, but I did, and still no gmp.
> Also, revdep-rebuild. Have you run it recently? (Run it with -p first,
Yep. No help.
> of course.) What about emerge --depclean (again, with -p first)?
Nothing looked like it was related in any way.
> Do you routinely run your emerge --update with the --deep (-D) switch?
Always.
> How much of your system has been recompiled with gcc-4.1.x?
Umm...not much. If I could ever get gmp compiled, then I could get around to
compiling a good chunk of the rest...
However, I have built/rebuilt/rebuilt again gcc, glibc, and binutils with gcc
4.1.1.
> of my system that's still compiled with gcc-3.4.x. If you haven't done an
> emerge --emptytree world since gcc-4.1.1 was unmasked and weren't running
> the masked 4.x versions as I was, perhaps that's the difference between it
> working fine here and not there?
>
Ick, that's (almost) the same as a reinstall...but I think I will end up doing
that.
> Another possible difference... I run very little 32-bit at all, and in
> fact have considered switching to the no-multilib profiles. (About the
...
> out of the way to somewhere the compile can't find them, and see if the
> problem "magically" disappears. It's worth a shot, anyway.
And oh yeah, I tried emerge'ing with -sandbox. Same deal.
About all I have 32bit-wise is enough to get a flash plugin for firefox-bin. I
have thought that multilib was a bit messy though, and I might try dumping it
since most of my 32bit stuff only works in a chroot'd system (ISE, wine, etc).
But as for this exact problem, I don't really see anything that is safe to
delete/move/hide that is definitely 32bit only that could be making problems.
> The system cleanliness thing is a good thing to check anyway, even if it
> doesn't fix this particular issue, so that's good to try first. The
...
> configure input, that could be the culprit. In fact, I've seen it happen
> more than once in my own troubleshooting, so be sure and check that.
>
Building by hand works.
> Are you familiar with the ebuild command? If not, man ebuild and bone up
> on the various stages (fetch/unpack/compile/install/qmerge, in that order)
...
> configure and make manually but without the ebuild switches. Also note
> the "elibtoolize" at the end of the unpack step. Perhaps that's the issue.
>
Doing it in stages with ebuild fails during compile at the same place.
However, I can do ebuild unpack, and then run configure the same way as ebuild
does, and then run make by hand and it also works.
I suppose it'd be good to get everything compiled/broken with gcc 4.1.1, so I'm
just going to give up and start an emerge -ep world tonight and see what
happens...
Thanks for the help though.
Kyle
--
[email protected] mailing list
