From: Heribert Dahms <heribert_dahms@icon-scm.com>
To: "'librik@panix.com'" <librik@panix.com>, cygwin@cygwin.com
Subject: RE: 1.3.10: Bug: -undef does not work in cpp (gcc 2.95.3-5)
Date: Tue, 28 May 2002 03:36:00 -0000 [thread overview]
Message-ID: <BF35D9C143BCCC4EB63181B67C9320C83A9C6E@serv-075.icon-germany.local> (raw)
Hi David,
did you have a look into the specs file
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs ?
Bye, Heribert (heribert_dahms@icon-scm.com)
> -----Original Message-----
> From: librik@panix.com [SMTP:librik@panix.com]
> Sent: Monday, May 27, 2002 06:33
> To: cygwin@cygwin.com
> Subject: 1.3.10: Bug: -undef does not work in cpp (gcc 2.95.3-5)
>
[Heribert] [snip]
> cygwin$ cpp -v -undef
> Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs
>
[Heribert] [snip]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-05-27 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 3:36 Heribert Dahms [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-08 6:51 librik
2002-05-27 5:31 librik
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=BF35D9C143BCCC4EB63181B67C9320C83A9C6E@serv-075.icon-germany.local \
--to=heribert_dahms@icon-scm.com \
--cc=cygwin@cygwin.com \
--cc=librik@panix.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).