public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: sridhar_adusumilli@my-deja.com
To: help-gcc@gnu.org
Subject: GCC complains that getwc macro redefined
Date: Wed, 08 Dec 1999 00:40:00 -0000	[thread overview]
Message-ID: <82l52h$osa$1@nnrp1.deja.com> (raw)

Hi,
When I compile (gcc -c) the following code
#include <curses.h>
void fn (void){}

on a Sun Ultra5 Running Solaris2.7. I get warning that getwc etc.macros
are redefined.

I am using precompiled binaries of gcc version 2.95.2. Upon looking at
the preprocessor output, I noticed that I can get rid of these warnings
with -D_MSE_INT_H. I find no documentation on MSE_INT_H.
 Can you pl. help?

Thanks for your time.
Sridhar
sridhar.adusumilli@wtl.be


Sent via Deja.com http://www.deja.com/
Before you buy.

WARNING: multiple messages have this Message-ID

From: sridhar_adusumilli@my-deja.com
To: help-gcc@gnu.org
Subject: GCC complains that getwc macro redefined
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <82l52h$osa$1@nnrp1.deja.com> (raw)
Message-ID: <19991231222400.6ziAQ8V8OV4SSjqXlo5S30R5nloe3CzB1JRr-6w5T-Q@z> (raw)

Hi,
When I compile (gcc -c) the following code
#include <curses.h>
void fn (void){}

on a Sun Ultra5 Running Solaris2.7. I get warning that getwc etc.macros
are redefined.

I am using precompiled binaries of gcc version 2.95.2. Upon looking at
the preprocessor output, I noticed that I can get rid of these warnings
with -D_MSE_INT_H. I find no documentation on MSE_INT_H.
 Can you pl. help?

Thanks for your time.
Sridhar
sridhar.adusumilli@wtl.be


Sent via Deja.com http://www.deja.com/
Before you buy.

             reply	other threads:[~1999-12-08  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-08  0:40 sridhar_adusumilli [this message]
1999-12-31 22:24 ` sridhar_adusumilli

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='82l52h$osa$1@nnrp1.deja.com' \
    --to=sridhar_adusumilli@my-deja.com \
    --cc=help-gcc@gnu.org \
    /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).