Description of problem: I'm having trouble with getting gcc/gcc-c++ to work because of architecture mixup between packages: gcc-c++ 4.8.2 x86_64 depends on gcc 4.8.2 i586 I think both should be the same architecture (x86_64 is this case) for gcc to work correctly. See URL for screenshot. Reproducible: Steps to Reproduce:
what is the output of "urpmi --debug gcc-c++" ?
Sorry, but I needed gcc to be working asap, so I disabled 32bit repositories and successfully installed x86_64 versions of both gcc-c++ and gcc. Now that everything is fixed, I can't really reproduce the problem.
It does not depend on a 32bit gcc, it simply depends on "gcc[== 4.8.2-3.mga4]" wich is satisfied with both 32bit and 64bit gcc, and for some reason urpmi decided to pull in the 32bit. but we neally need a urpmi --debug report to track down why it happend
CC: (none) => thierry.vignaud, tmb
I think it's a rpmdrake specific bug, hence I prefer to have a debug environment. Even if gcc's installed, it can still be useful. Please send the requested file.
Since the problem is fixed now, urpmi doesn't show anything unusual, all dependencies are x86_64 right now. I don't remember exactly how I got into this weird state, so I can't reproduce it. Maybe I just installed gcc i586 first by mistake, and then gcc-c++ x86_64 after that... I only remember that gcc couldn't compile anything, and after some attempts to fix it by uninstalling/installing again, it somehow ended in this strange situation. Since I can't reproduce it, feel free to close this.
Please just run the following commands: yes n|urpmi --auto-select --bug bug12336 tar cfa bug12336{.tar.xz,} Then send me the bug12336.tar.xz, I might still be able to understood what happened.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => nicVersion: Cauldron => 4Resolution: (none) => OLD