From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com, Don Libes <libes@nist.gov>
Subject: Re: expect won't build with Tru64 cc
Date: Wed, 06 Mar 2002 18:25:00 -0000 [thread overview]
Message-ID: <oradtlqfkx.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Andrew Cagney's message of "Wed, 06 Mar 2002 20:40:45 -0500"
On Mar 6, 2002, Andrew Cagney <ac131313@cygnus.com> wrote:
>> Using the following C compiler on alphaev6-dec-osf4.0f
>> % cc -V | head -1
>> DEC C V5.9-010 on Digital UNIX V4.0 (Rev. 1229)
>> GDB won't build (both CVS and mainline). One of the reasons is that
>> expect contains an ill-formed C construct that the DEC C compiler
>> rejects (actually, it warns about it, but the #define fails to take
>> effect). This patch fixes the problem. I don't know whether this is
>> already fixed in expect upstream, so I'm Cc:ing Don Libes.
>> GDB/expect maintainers, ok to install in mainline and 5.2 branch?
> Just so I'm sure I'm not seeing anything, the problem is that the
> ``#'' isn't at the start of the line?
Yup.
> If that is the case then yes, fine. If it really is the case then I
> think I'm going to have to add this to the coding standard/ARI for
> GDB, it is just too wierd. (I've a fuzzy memory of seeing this before).
GCC warns about it when given some flags. I'm not sure ISO C already
supports preprocessor directives with the `#' preceded by whitespace,
but I'm pretty sure a number of K&R compilers don't.
--
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
prev parent reply other threads:[~2002-03-07 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 16:00 Alexandre Oliva
2002-03-06 17:41 ` Andrew Cagney
2002-03-06 18:25 ` Alexandre Oliva [this message]
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=oradtlqfkx.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=libes@nist.gov \
/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