public inbox for
 help / color / mirror / Atom feed
From: Christopher Faylor <>
Subject: [ Re: tix fails to build for m68k-elf]
Date: Sat, 08 Mar 2003 20:17:00 -0000	[thread overview]
Message-ID: <> (raw)



----- Forwarded message from Jim Wilson <> -----

From: Jim Wilson <>
To: Peter Barada <>
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 -----

                 reply	other threads:[~2003-03-08 20:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).