From: Mumit Khan <khan@xraylith.wisc.edu>
To: egcs@cygnus.com
Subject: Re: egcs on cygwin32 i586
Date: Thu, 11 Dec 1997 07:47:00 -0000 [thread overview]
Message-ID: <9712111545.AA03270@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <n1330277874.51694@macmail.psy.uva.nl>
You should pose these questions to gnu-win32 newsgroup, since that's where
all the gnu-win32 users hang out.
> I have gnuwin32 b18 installed. Downloaded Mumit's win32 egcs1.0 pre-build
> binaries. untarred them over gnuwin in the dir c:/gnuwin32/b18. This seems to
> be the apropriate place. Installed coolview (libcygwin.a and cygnus.dll) and
> all seens to be OK.
You should use *my* libcygwin.a, even if you use Sergey's cygwin.dll.
> all but one thing: the default include path is incorrect: unable to find
> stdio.h etc. So I hacked the makefile of my app to search the specific dirs
> for these files. Now the compilation goes fine. But the linking doesn't. It
> just stops. Well actually it just doesn't.
>
> so 2 questions: How do I change de default include-dir?
See the FAQ for cygwin32 ( http://www.cygnus.com/misc/gnu-win32/ ).
Basically you have to set the C_INCLUDE_PATH, C_PLUS_INCLUDE_PATH, etc.
I've uploaded a sample SETENV.BAT file in my ftp area that should work
for you. Where you found the gnuwin32-egcs-1.00.tar.gz file.
for future reference, when you report problems, you should include at
least the following:
1. You current environment settings.
2. output of the compiler with -v option:
% gcc -v test.c
3. also the linking step:
% gcc -o ntat.exe -v main.o
Mumit
next prev parent reply other threads:[~1997-12-11 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 3:50 op Span
1997-12-11 7:47 ` Mumit Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-10 1:42 op Span
1997-12-10 7:31 ` Mumit Khan
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=9712111545.AA03270@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=egcs@cygnus.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).