GCC 4.4.x 4.5.x NOT merged due to collisions with gcc-4.x

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

[changing subject as it's not 1 version specific]
Hi all,

I'm really confused here.. and a few days of searching the net didn't give me any good results for this. I was wondering if anyone can help.. I'm on a relatively clean installation of Gentoo on amd64, and during a typical day of upgrading my apps, it now is failing to emerge sys-devel/gcc-4.4.3-r2 due to it colliding with sys-devel/gcc-4.3.4.. The advice it suggested is to remove the offending app that's colliding, but how can I remove gcc and expect to compile the other gcc version? (or anything for that matter)?

Compiling gcc is successful.. It's just the installation part that's failing. I tried emerging without gcj, that didn't help. This is what I get..

Sadako · Posted: Mon Jun 21, 2010 4:18 pm Post subject:

Something is seriously screwed up here...

Those detected file collisions, they should all be installed under /usr/lib[32,64]/gcc/x86_64-pc-linux-gnu/4.4.4/, not directly in /usr/lib, same goes for the files for 4.3.4, which indicates that your installed gcc 4.3.4 is "broken" too (although should be fine for emerging other packages).

All the "command not found" warnings for -print-multi-lib, --print-multi-directory and -m32, these are flags which are supposed to be passed to gcc directly, my guess is something like `$CC -print-multi-lib foo` is being executed, but "CC" (or whatever variable name used, not relevant) isn't actually defined for some reason, which would result in an attempt to execute the first argument/flag.

tbh, I really have no idea why this has happened, but you could repost your emerge --info, adding the --verbose flag, may reveal something.
_________________
"You have to invite me in"

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Damn... I don't see how this could end up like this =/ I followed the book for years on this system, kept it simple and reduced mods to a minimum and emerging gcc worked till now

I guess if we can't find the problem then I could find a hard solution =/

Thanks for the help so far. Actually, although this is a one-app collision, do you think it's worth filing a bug report?

Sadako · Posted: Mon Jun 21, 2010 4:56 pm Post subject:

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Thanks.

I thought -march would be set by default?

I'll keep this thread updated when I can.

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Hopeless,

I'll be honest; Since it's a one-app collision, and probably due to a misconfiguratin, I wasn't sure the devs would be happy with me filing a bug..

Instead I dug a bit deeper onto what I can do and found a solution that worked.

For anyone that encounters this again,

Go to http://tinderbox.dev.gentoo.org/default-linux/amd64/sys-devel/

I downloaded the gcc binary version I wanted to update to (might as well..) gcc-4.3.4.tbz2

Copy it into /usr/portage/packages/sys-devel/ (create that sys-devel/ folder as it most probably won't exist)

remove the gcc I currently have installed: emerge -C gcc
Ignore the warnings it gives you...

Install the binary version package only:
cd /usr/portage/packages/sys-devel/
emerge --usepkgonly gcc-4.3.4.tbz2

That did the trick. Once installed, if you eix sys-devel/gcc, you'll notice the {tbz} mark telling you it's a binary package.

Now all you have to do is just delete the binary .tbz2 you downloaded and re-emerge GCC from source, and presto!

emerge gcc

finally, when done, the {tbz} should go away, and you can continue emerging -e system if you want seeing as you just upgraded GCC[/list]

Sadako · Posted: Sun Jun 27, 2010 1:29 pm Post subject:

Nice workaround.

However, after installing the binary gcc package, did you use that to emerge gcc normally, and then check that it's files are installed under /usr/lib64/gcc/x86_64-pc-linux-gnu rather than /usr/lib64 directly?

If they're still installed in /usr/lib, then you haven't really solved the issue, and will hit the problem again if you attempt to install two versions of gcc on your system at once (which should be a none issue).

However, if you're happy with it, then I guess there's no real harm, other than not being capable of installing two gcc versions at once (which very few people actually need or make use of in the first place), there probably aren't any ill affects, it just shouldn't happen is all, and it would just bug me if I couldn't figure out why it does...
_________________
"You have to invite me in"

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Damn... you're right. They're still in /usr/lib64/

I'll follow up with a bug report then, and will keep the thread updated.

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Hi all,

Just to update,

/usr/lib/ is simlinked to /usr/lib64.

I just checked today to see if this problem will come up again at some point and noticed I now have 4.4.5 installed now ! It's also now in

/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/

I'm not entirely sure how this got fixed, but I have a feeling that my instructions above might have done the trick.

Hope this helps.

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

Bah... This is happening again today with 4.5.3-r1 and I've lost hope

I can't figure out why it's happening exactly.

I've created a bug report, hopefully the devs will be able to look into it more deeply.

splurben

I'm having this problem on more than one amd64 Gentoo systems. I'm seeing some unresolved bug reports and this thread isn't solved.

Does anyone know what's going on with this?

my emerge --info: http://pastebin.com/ZK3ss81S

emerge-log: http://rehost.splurben.com/gforum_2012-01-29/var_tmp_portage_sys-devel_gcc-4.5.3-r2_work_build_gcc-build-logs.tar.bz2

Kirk
_________________
--=>Like... Goodness had nothing to do with it.<=--

115552 · Tux's lil' helper Joined: 09 Aug 2005 Posts: 108

This one isn't resolved yet, but sod's law struck again.. Just after I filed the bug report, I followed my previous steps of upgrading to see if that worked, and for the life of me i ca't reproduce the problem anymore.. So I guess I'll have to wait until another upgrade comes along that will break it again.

My advice is to go to the bug report I filed in my previous post, and follow up there. You can carry on from where I started by giving them examples and information.

DaggyStyle · Watchman Joined: 22 Mar 2006 Posts: 5916

what is the output of emerge -atv gcc?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

splurben · Posted: Fri Feb 03, 2012 2:31 am Post subject: output of emerge -avt

DaggyStyle · Watchman Joined: 22 Mar 2006 Posts: 5916

splurben · Posted: Sun Feb 05, 2012 5:32 am Post subject: output of eix

splurben · Posted: Sun Feb 05, 2012 6:22 am Post subject: [SOLVED] Removed MULTISLOT

Collisions were eradicated by removing multislot USE flag. Dare I ask why?
_________________
--=>Like... Goodness had nothing to do with it.<=--

rhill · Posted: Sun Feb 05, 2012 7:14 pm Post subject:

multislot is broken by design. don't use it.
_________________
by design, by neglect
for a fact or just for effect

splurben · Posted: Mon Feb 06, 2012 12:21 am Post subject: MULTISLOT is broken by design

Is MULTISLOT meant to be deprecated in all cases or just for GCC?
_________________
--=>Like... Goodness had nothing to do with it.<=--