From: "Mike Lerwill" <mlist@ml-solutions.co.uk>
To: "Cygwin@Cygwin. Com" <cygwin@cygwin.com>
Subject: Difference between 2.95.3 and 3.1.1-2
Date: Mon, 15 Jul 2002 08:29:00 -0000 [thread overview]
Message-ID: <FGELLPDBIBNCBLEECDELOEDCGJAA.mlist@ml-solutions.co.uk> (raw)
Hi,
I have been using cygwin for a while to build a h8 cross toolchain
with a great deal of success.
Testing the experimental 3.1.1-2 shows a difference in that 2.95-3
includes /usr/include/win32api as the last search path and 3.1.1-2
does not. This causes problems with compilation of readline (kill.c)
and gcc (cppfiles.c) which want to include windows.h
While it is easy to work around this I would like to know if this is
a deliberate change or not.
Thanks and keep up the good work
Mike
--
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/
reply other threads:[~2002-07-15 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=FGELLPDBIBNCBLEECDELOEDCGJAA.mlist@ml-solutions.co.uk \
--to=mlist@ml-solutions.co.uk \
--cc=cygwin@cygwin.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).