public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com, insight@sources.redhat.com
Subject: Re: GDB CVS won't build on OSF4.0's cc
Date: Wed, 06 Mar 2002 18:52:00 -0000	[thread overview]
Message-ID: <or4rjtqebz.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Andrew Cagney's message of "Wed, 06 Mar 2002 20:57:59 -0500"

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Mar  6, 2002, Andrew Cagney <ac131313@cygnus.com> wrote:

> I don't know that this belongs in defs.h (definitly not without a big
> comment explaining the history :-).  As you note, gdb doesn't include
> tclInt.h, only GDBTK.  I suspect gdbtk/generic/gdbtk.h or autoconf is
> better?

It would be a silly use of autoconf, since gdb just assumes stdarg.h
is there.  As for its not including tclInt.h, it's true that gdb
itself does not, but some of the gdbtk files include tk, itcl and tix
headers that end up including tclInt.h.  Unfortunately, they include
gdbtk.h only after including such headers, so adding a define in
gdbtk.h would be too late.

I agree we should try to keep gdbtk as separate from gdb as possible,
but I thought this define would be ok, since gdb's configure already
has code to look for tcl/tk.  Anyway, here's an alternate patch that I
dislike a bit on the grounds that it doesn't make sure the problem
won't show up again in the future, and it won't trigger any warnings
should gdb proper ever drop the assumption that stdarg.h is present
(unlikely, but... :-)

Ok to install?  Verified to build with OSF4.0's cc.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gdb-has-stdarg.patch --]
[-- Type: text/x-patch, Size: 1988 bytes --]

Index: gdb/gdbtk/ChangeLog
from  Alexandre Oliva  <aoliva@redhat.com>

	* generic/gdbtk.c (HAS_STDARG): Define.
	* generic/gdbtk-cmds.c (HAS_STDARG): Likewise.
	* generic/gdbtk-hooks.c (HAS_STDARG): Likewise.

Index: gdb/gdbtk/generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.52
diff -u -p -r1.52 gdbtk-cmds.c
--- gdb/gdbtk/generic/gdbtk-cmds.c 2002/02/11 03:21:55 1.52
+++ gdb/gdbtk/generic/gdbtk-cmds.c 2002/03/07 02:47:19
@@ -35,6 +35,10 @@
 #include "top.h"
 #include "annotate.h"
 
+/* tcl header files includes varargs.h unless HAS_STDARG is defined,
+   but gdb uses stdarg.h, so make sure HAS_STDARG is defined.  */
+#define HAS_STDARG 1
+
 #include <tix.h>
 #include <itcl.h>
 
Index: gdb/gdbtk/generic/gdbtk-hooks.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-hooks.c,v
retrieving revision 1.21
diff -u -p -r1.21 gdbtk-hooks.c
--- gdb/gdbtk/generic/gdbtk-hooks.c 2002/02/14 07:25:22 1.21
+++ gdb/gdbtk/generic/gdbtk-hooks.c 2002/03/07 02:47:20
@@ -37,6 +37,10 @@
 #include <windows.h>
 #endif
 
+/* tcl header files includes varargs.h unless HAS_STDARG is defined,
+   but gdb uses stdarg.h, so make sure HAS_STDARG is defined.  */
+#define HAS_STDARG 1
+
 #include <itcl.h>
 #include <tix.h>
 #include "guitcl.h"
Index: gdb/gdbtk/generic/gdbtk.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk.c,v
retrieving revision 1.26
diff -u -p -r1.26 gdbtk.c
--- gdb/gdbtk/generic/gdbtk.c 2002/02/07 21:56:07 1.26
+++ gdb/gdbtk/generic/gdbtk.c 2002/03/07 02:47:20
@@ -38,6 +38,10 @@
 #include <windows.h>
 #endif
 
+/* tcl header files includes varargs.h unless HAS_STDARG is defined,
+   but gdb uses stdarg.h, so make sure HAS_STDARG is defined.  */
+#define HAS_STDARG 1
+
 #include <tix.h>
 #include <itcl.h>
 #include <itk.h>

[-- Attachment #3: Type: text/plain, Size: 289 bytes --]


-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  reply	other threads:[~2002-03-07  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <org0dofodw.fsf@guarana.lsd.ic.unicamp.br>
     [not found] ` <or3d9ofncw.fsf@guarana.lsd.ic.unicamp.br>
     [not found]   ` <ory9rge7dc.fsf@guarana.lsd.ic.unicamp.br>
     [not found]     ` <orpu2hqlq8.fsf@free.redhat.lsd.ic.unicamp.br>
2002-03-06 17:58       ` Andrew Cagney
2002-03-06 18:52         ` Alexandre Oliva [this message]
2002-03-13 11:19           ` Alexandre Oliva
2002-03-25  8:43           ` Alexandre Oliva

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=or4rjtqebz.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).