Summary: | emerge error on net-print/gnome-cups-manager-0.31 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kurt Guenther <kurtg> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | andreas.kotowicz, cbm, Heinz.Hombergs, latexer, malmond, santiago, sparc |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
da patch!
da ebild with patch |
Description
Kurt Guenther
2005-09-28 10:35:28 UTC
Works fine here. What version of libgnomecups do you have? Could you try re-emerging libgnomecups? I got the same error's when compling gnome-cups-manager-0.31. The version of libgnomecups is 0.2.2, I'm running a ~86 system. Based on your suggestion, I tried re-emerging libgnomecups and had the same results emerging the gnome-cups-manager-0.31. I also have: net-print/libgnomecups-0.2.2 (In reply to comment #3) > Based on your suggestion, I tried re-emerging libgnomecups and had the same > results emerging the gnome-cups-manager-0.31. > > I also have: net-print/libgnomecups-0.2.2 Same scenario here. Same errors and versions. ~x86 System, AthlonXP I had the same problem - I found that switching my gcc version from i686-pc-linux-gnu-3.3.4 to i686-pc-linux-gnu-3.4.4 fixed the problem for me. Hope that helps. (In reply to comment #5) > I had the same problem - I found that switching my gcc version from > i686-pc-linux-gnu-3.3.4 to i686-pc-linux-gnu-3.4.4 fixed the problem for me. > Hope that helps. I am confirming - the same here: switched to 3.4.4 profile that totaly resolved the issue. switching to gcc 3.4.4 good for me too Same issue here with gcc-3.3.6. Running an x86 system with select ~x86, so no gcc-3.4 installed here. I did the same and switched to gcc 3.4.4 to successfully emerge this package. Let me spell it out for anybody (like me) who doesn't know how to switch gcc versions. Run: gcc-config -l to see the versions available. Look for the number that precedes gcc 3.4.4 (plain), and then run. gcc-config 3 substitute the correct number for 3. It should emerge without any issues. from http://bugzilla.gnome.org/show_bug.cgi?id=315384 Can this patch being tested (if pass -->) included? http://bugzilla.gnome.org/attachment.cgi?id=51929&action=view (In reply to comment #9) > I did the same and switched to gcc 3.4.4 to successfully emerge this package. > Let me spell it out for anybody (like me) who doesn't know how to switch gcc > versions. Run: > > gcc-config -l > > to see the versions available. Look for the number that precedes gcc 3.4.4 > (plain), and then run. > > gcc-config 3 > > substitute the correct number for 3. It should emerge without any issues. > > > (In reply to comment #9) > I did the same and switched to gcc 3.4.4 to successfully emerge this package. > Let me spell it out for anybody (like me) who doesn't know how to switch gcc > versions. Run: > > gcc-config -l > > to see the versions available. Look for the number that precedes gcc 3.4.4 > (plain), and then run. > > gcc-config 3 > > substitute the correct number for 3. It should emerge without any issues. > > > Indeed, the fix is immaculate. Domo. For some reason, imho, it does'nt seems logical or practical to build||have another gcc for a 496K little app ... 496K little app is gone ATM ;) comment #12: Could you test the patch in comment #10? I can't, because I'm on amd64, and therefore don't have a gcc 3.3.x I confirmed the patch fix this issue. dang, please apply the patch. Created attachment 73057 [details, diff]
da patch!
This is it!
Created attachment 73058 [details]
da ebild with patch
Needs formality on its header (and maybe add extraversion "-r1")
C ya!
Upstream has said no to the patch. We wont apply this downstream either. However, as gcc-3.4 has been stablized on most arches, this really is no longer a big issue. The remaining arches are hppa, ia64, ppc64 and sparc. Okay, added a warning to the ebuild. Depending on a gcc version is really bad, and as a result, marking as CANTFIX. *** Bug 125418 has been marked as a duplicate of this bug. *** |