Michael George <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Wed, 27 Dec 2006 06:16:53 -0500:
> I'm updating my system (amd64) to gcc4.1 and things are going rather > smoothly. One problem I'm having, though, is that tclx-8.3 will not > complete it's build. > > I can build it fine with gcc-3.4, but not 4.1. > I've searched the net and found a posting of the error, but it's in a > language I do not understand. > > Has anyone else run into this problem and found a solution? I don't have it merged here, but your net search apparently didn't include a Gentoo bug search. Note that google (and presumably other websearch engines) doesn't know how to index bugzilla pages very well, so you have to search them separately. Anyway, a quick search from http://bugs.gentoo.org on "ALL tclx", then skipping to the bottom of the list since the bugs are in numerical order and we are interested in something fairly new, yields a number of dups of this bug: http://bugs.gentoo.org/show_bug.cgi?id=133099 It doesn't say what I was looking for directly, but it mentions related emacspeak bug http://bugs.gentoo.org/show_bug.cgi?id=148854 which mentions (as you suspected) that the problem is a gcc-4.1 incompatibility. There's tclx-8.4-r1 in the tree as ~amd64 and already x86 stable, which compiles with gcc-4.1. However, certain packages that depend on tclx apparently don't have a stable version in portage that can handle tclx-8.4, so all those packages pretty much need to stabilize together, and if one or more of them have other amd64 issues... So, bottom line, tclx-8.4-r1 is currently keyworded ~amd64. It works with gcc-4.1, but since some stable versions of packages that depend on tclx aren't 8.4 compatible, be prepared to package.keyword any of them too, in ordered to get them working again after upgrading tclx. Or simply wait until everything is stabilized, staying with your gcc-3.4 built version until then. The choice is yours. =8^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
