From: Alexandre Oliva <aoliva@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: GDB CVS won't build on OSF4.0's cc
Date: Wed, 06 Mar 2002 16:12:00 -0000 [thread overview]
Message-ID: <orpu2hqlq8.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Alexandre Oliva's message of "29 May 2001 08:12:47 -0300"
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On May 29, 2001, Alexandre Oliva <aoliva@redhat.com> wrote:
> Another problem showed up while building gdbtk. gdb/defs.h #includes
> <stdarg.h>, but tcl/generic/tclInt.h #includes <varargs.h>, because
> HAS_STDARG is not defined.
> It turns out that the va_start macro defined in varargs.h ends up
> overriding that of stdarg.h, so we call va_start with the wrong number
> of arguments.
> Since GDB assumes the existence of stdarg.h, I suppose this patch
> would be acceptable. Ok to install?
This one seems to have never been acknowledged. Ok for 5.2 and
mainline?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gdb-has-stdarg.patch --]
[-- Type: text/x-patch, Size: 513 bytes --]
Index: gdb/ChangeLog
from Alexandre Oliva <aoliva@redhat.com>
* defs.h (HAS_STDARG): Define it.
Index: gdb/defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.50
diff -u -p -r1.50 defs.h
--- gdb/defs.h 2001/05/15 00:03:36 1.50
+++ gdb/defs.h 2001/05/29 11:10:38
@@ -54,6 +54,7 @@
#include "ansidecl.h"
#include <stdarg.h> /* for va_list */
+#define HAS_STDARG 1 /* Avoid varargs.h in tcl. */
#include "libiberty.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
next prev parent reply other threads:[~2002-03-07 0:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 3:20 Alexandre Oliva
2001-05-29 3:42 ` Alexandre Oliva
2001-05-29 4:12 ` Alexandre Oliva
2002-03-06 16:12 ` Alexandre Oliva [this message]
2002-03-06 17:58 ` Andrew Cagney
2002-03-06 18:52 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-25 8:43 ` Alexandre Oliva
2001-06-06 13:20 ` Elena Zannoni
2001-06-09 16:14 ` Alexandre Oliva
[not found] ` <Pine.SUN.3.91.1010610111224.5638I-100000@is>
2001-06-10 14:25 ` Alexandre Oliva
2001-06-11 1:06 ` Eli Zaretskii
2001-06-11 1:33 ` Russ Allbery
2001-06-11 7:04 ` Andrew Cagney
2001-06-11 6:32 ` Elena Zannoni
2001-06-11 6:34 ` Elena Zannoni
2002-03-06 16:36 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-19 9:41 ` Elena Zannoni
2002-03-19 10:31 ` Alexandre Oliva
2002-03-19 10:48 ` Elena Zannoni
2002-03-19 18:23 ` Alexandre Oliva
2002-03-19 18:39 ` Andrew Cagney
2002-03-19 20:40 ` Elena Zannoni
2002-03-20 0:00 ` Alexandre Oliva
2002-03-20 7:08 ` Elena Zannoni
2002-03-19 23:43 ` Alexandre Oliva
2002-03-20 7:10 ` Elena Zannoni
2002-03-20 14:27 ` Alexandre Oliva
2002-03-25 8:49 ` Alexandre Oliva
2001-05-29 9:30 ` Kevin Buettner
2001-05-30 19:54 ` 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=orpu2hqlq8.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--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