[gentoo-amd64] problems emerging tclx

[gentoo-amd64] problems emerging tclx

[Michael George]

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.

The error I get is:
            /var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/generic/tclXbsearch.cIn
file included from /usr/include/time.h:8,
                 from /usr/include/gentoo-multilib/amd64/sys/times.h:29,
                 from /usr/include/sys/times.h:8,
                 from
/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/unix/tclXunixPort.h:32,
                 from
/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/generic/tclExtdInt.h:27,
                 from
/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/generic/tclXbsearch.c:19:
/usr/include/gentoo-multilib/amd64/time.h:61: error: two or more data
types in declaration specifiers
/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/generic/tclXbsearch.c: In
function 'TclProcKeyCompare':
/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/generic/tclXbsearch.c:115:
warning: passing argument 2 of 'Tcl_Merge' from incompatible pointer
type
make[1]: *** [tclXbsearch..o] Error 1
make[1]: Leaving directory
`/var/tmp/portage/tclx-8.3.5/work/tclx8.3.5/tcl/unix'make: *** [TCLX]
Error 2

!!! ERROR: dev-tcltk/tclx-8.3.5 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  tclx-8.3.5.ebuild, line 65:   Called die

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?

-- 
-M

There are 10 kinds of people in this world:
	Those who can count in binary and those who cannot.
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems emerging tclx

[Duncan]

Michael George <george@mutualdata.com> posted
20061227111653.GA32181@brego.pewamo.office, 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

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems emerging tclx

[Michael George]

On Thu, Dec 28, 2006 at 01:00:00AM +0000, Duncan wrote:
> 
> 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.

You are right, I didn't search the gentoo bugs, but I shall in the
future.  I didn't know that Google wouldn't grab them...

> 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^)

Excellent information.  Thanks to all who answered my plea!

-- 
-M

There are 10 kinds of people in this world:
	Those who can count in binary and those who cannot.
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems emerging tclx

[Duncan]

Michael George <george@mutualdata.com> posted
20061228015743.GA6475@brego.pewamo.office, excerpted below, on  Wed, 27
Dec 2006 20:57:43 -0500:

> You are right, I didn't search the gentoo bugs, but I shall in the
> future.  I didn't know that Google wouldn't grab them...

It's not something one would expect, certainly, given that Google knows
how to index and can often supply from cache as HTML everything from PDF
to MS Word and Excel files.  However, each bugzilla installation,
certainly the big ones used by the various distributions and all the big
projects, tends to be somewhat customized, so Google would need to
customize it's bots for each one, and apparently the individual user
segments interested in each one are small enough Google hasn't found it
worth the trouble to do and maintain.

So it's an understandable mis-assumption.  Still, think about it.  How
many bugzilla results have you ever come across in your various Linux info
searches?  I've certainly not come across that many, if any.  It's just
that it doesn't occur to folks, since they are used to google indexing
virtually /everything/ on the web.  I knew I always used bugzilla for that
type of searches, not google, but I didn't realize why, until someone
happened to explain it in a post such as this one.

So anyway, now you (and possibly others on the list) know. =8^)  Google's
good for a lot of stuff, but not for looking up bugs filed in bugzilla. 
Neat thing about newsgroups/mailing-lists that way.  You ask a question,
or read one someone else has asked, and often get answers to questions you
didn't even know you had, in the process of getting the answer to the one.
=8^)  That's one reason I find them so much fun, as I never know what new
and useful thing I'm going to learn when I load up the messages. =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

-- 
gentoo-amd64@gentoo.org mailing list