From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix compilation of tui/tui.c
Date: Sat, 28 Feb 2004 15:48:00 -0000 [thread overview]
Message-ID: <200402281547.i1SFlv87012449@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <4040B1D7.4090805@gnu.org> (message from Andrew Cagney on Sat, 28 Feb 2004 10:20:55 -0500)
Date: Sat, 28 Feb 2004 10:20:55 -0500
From: Andrew Cagney <cagney@gnu.org>
> Ouch. We have serious portability problems with the TUI. We should
> either disable it again before the 6.1 release, or be prepared to
> release 6.1.1 if any build problems come up. I'm sure we'll see build
> problems on many systems that we don't regularly test.
>
> Anyway, I committed the attached such that FreeBSD (and probably the
> other BSD's work again/.
It works on my bsd system (how do you think I was testing it)?
I didn't check on OpenBSD or NetBSD, but I supposed they would suffer
from the same problems as my FreeBSD-system.
What portability problem.
The TUI code is including header files and using library functions
that we've never used before in GDB. We've already seen the fall-out
from this on HP-UX and Solaris, and now on FreeBSD. I'm just afraid
that more of these problems will surface when somebody tries to build
GDB other platforms.
Is there a reason for changing "" to <>, it breaks some of GDB's
scripts.
I changed because we seem to use <> everywhere else in GDB for the
readline includes, e.g. event-top.c, completer.c. I think it's good
to be consistent; you get less surprises that way.
Mark
next prev parent reply other threads:[~2004-02-28 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 15:03 Mark Kettenis
2004-02-28 15:20 ` Andrew Cagney
2004-02-28 15:48 ` Mark Kettenis [this message]
2004-02-28 16:59 ` Andrew Cagney
2004-02-29 6:10 ` Eli Zaretskii
2004-02-29 14:57 ` Andrew Cagney
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200402281547.i1SFlv87012449@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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