* [firstname.lastname@example.org: Re: tix fails to build for m68k-elf]
@ 2003-03-08 20:17 Christopher Faylor
0 siblings, 0 replies; only message in thread
From: Christopher Faylor @ 2003-03-08 20:17 UTC (permalink / raw)
----- Forwarded message from Jim Wilson <email@example.com> -----
From: Jim Wilson <firstname.lastname@example.org>
To: Peter Barada <email@example.com>
Subject: Re: tix fails to build for m68k-elf
Date: Fri, 07 Mar 2003 18:10:50 -0500
Peter Barada wrote:
>I thought that the tix directory was going to be removed....
This isn't a gcc problem, it is an insight/source-navigator problem.
There isn't anything a gcc maintainer can do about it except complain to
the insight/source-navigator maintainers.
Yes, someone will eventually fix this. Meanwhile, it isn't really a
serious problem. It is just a minor annoyance. Just delete or rename
the tix directory in your uberbaum tree and the problem goes away. This
assumes you have no interest in source-navigator, which is normally not
built as part of an uberbaum tree. This will allow insight (gdbtk) to
>If I remove it, the build continues until it bombs out in the rda
This is also not a gcc problem. It is an RDA problem. RDA doesn't seem
to be a full fledged project yet, so we should consider it a gdb
problem. This can be solved in a similar way, just move the offending
directory out of the way, and/or complain to the gdb maintainers.
I'd like to point out that the uberbaum tree, while very useful, has
always been unofficial and mostly undocumented. You can't expect anyone
to be responsive to problems with it.
----- End forwarded message -----
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-03-08 20:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-08 20:17 [firstname.lastname@example.org: Re: tix fails to build for m68k-elf] Christopher Faylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).