From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
Date: Thu, 11 Jul 2002 09:05:00 -0000 [thread overview]
Message-ID: <20020711152331.GA8291@redhat.com> (raw)
In-Reply-To: <20020711131751.76665.qmail@web21003.mail.yahoo.com>
On Thu, Jul 11, 2002 at 06:17:51AM -0700, Nicholas Wourms wrote:
>
>--- Christopher Faylor <cgf@redhat.com> wrote:
>[SNIP]
>
>Chris,
>
>When I do gcc -v, gcc prints out the following:
>
>Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.1.1/specs
>Configured with: /netrel/src/gcc-3.1.1-2/configure
>--enable-languages=c,c++,f77,java --enable-libgcj --enable-threads=posix
>--with-system-zlib --enable-nls --without-included-gettext
>--disable-shared --enable-interpreter --disable-sjlj-exceptions
>--disable-version-specific-runtime-libs --build=i686-pc-linux
>--host=i686-pc-cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr
>--exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib
>--includedir=/nonexistent/include --libexecdir=/usr/sbin :
> ^^^^^^^^^^^^^^^^^^^^
>(reconfigured)
>Thread model: posix
>gcc version 3.1.1 20020710 (prerelease)
>
>Shouldn't that be /usr/include? The only reason I ask is because I'm
>quite certain that this could cause troubl in configure scripts. Like
>I've noticed that if I don't explicitly pass CPPFLAGS="-I/usr/include" to
>my configure scripts, they'll miss the limits.h in /usr/include and use
>the one in /usr/lib/gcc-lib/...../include/ instead. This goes for some
>other header detection as well. I believe it is due to the compiler's
>internal search paths. Just thought I'd report that observation.
This is basically the same configure script that I have been using for
two years, so I doubt that it will cause problems.
The limits.h file in /usr/lib/gcc-lib/../include/ *is* the one that is
supposed to be used. It includes the /usr/include/limits.h file
automatically.
Are you saying that when I announced that the limits.h problem was
fixed, I was wrong? I specifically checked the -E output from a
program and saw that /usr/include/limits.h was pulled in specifically.
cgf
--
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 prev parent reply other threads:[~2002-07-11 15:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 2:19 Christopher Faylor
2002-07-11 3:47 ` Charles Wilson
2002-07-11 3:49 ` Charles Wilson
2002-07-11 6:47 ` Nicholas Wourms
2002-07-11 8:26 ` Charles Wilson
2002-07-11 20:26 ` Christopher Faylor
2002-07-11 20:50 ` Christopher Faylor
2002-07-11 10:19 ` Christopher Faylor
2002-07-11 11:56 ` Charles Wilson
2002-07-11 21:09 ` Christopher Faylor
2002-07-11 21:33 ` Unscrible--liangalei@CS.SJTU.EDU.CN liangalei
2002-07-11 23:59 ` Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Charles Wilson
2002-07-12 0:27 ` Christopher Faylor
2002-07-12 0:31 ` Charles Wilson
2002-07-12 1:32 ` Christopher Faylor
2002-07-12 2:54 ` Charles Wilson
2002-07-12 4:40 ` Christopher Faylor
2002-07-12 9:22 ` Charles Wilson
2002-07-12 18:46 ` Christopher Faylor
2002-07-12 7:27 ` Nicholas Wourms
2002-07-15 0:55 ` Charles Wilson
2002-07-15 1:09 ` Christopher Faylor
2002-07-15 8:02 ` Nicholas Wourms
2002-07-15 11:56 ` Charles Wilson
2002-07-15 12:36 ` Nicholas Wourms
2002-07-11 7:19 ` Nicholas Wourms
2002-07-11 9:05 ` Christopher Faylor [this message]
2002-07-11 14:26 ` Nicholas Wourms
2002-07-11 8:49 ` Pavel Tsekov
2002-07-12 2:38 ` Christopher Faylor
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=20020711152331.GA8291@redhat.com \
--to=cgf@redhat.com \
--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).