From: kevinm@ieg.com.br
To: cygwin@cygwin.com
Subject: Re: failed to compile cygwin <<Scan Mail hat keinen Virus gefunden>>
Date: Tue, 30 Oct 2001 12:57:00 -0000 [thread overview]
Message-ID: <3bdf0529.1a1e.0@ieg.com.br> (raw)
My make also choked on cygwin/cygheap.cc with "implicit declaration of function
int memset(...)"
The problem is that the include path in winsup/Makefile.common starts with
-I. -I/usr/src/.../winsup/cygwin, but the <string.h> include file in winsup/cygwin/string.h
starts with:
#ifndef _CYGWIN_STRING_H
#define _CYGWIN_STRING_H
#include_next <string.h>
So the only string.h that is getting included is the local one (in winsup/cygwin/string.h),
which does not include the memset prototype.
I "solved" the problem by changing the cygwin/string.h file:
#include_next <string.h>
#ifndef _CYGWIN_STRING_H
#define _CYGWIN_STRING_H
This ensures that the next string.h that gets included will be the system one,
and not cygwin/string.h
I'm a complete newbie to cygwin so I don't know if this is the "correct" solution
...
Kevin
http://www.ieg.com.br
--
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:[~2001-10-30 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 12:57 kevinm [this message]
[not found] ` <2903380712.20011030235925@familiehaase.de>
2001-10-30 16:55 ` Kevin Mackie
[not found] ` <50913115540.20011031024140@familiehaase.de>
2001-10-31 3:48 ` failed to compile cygwin Kevin Mackie
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 9:24 failed to compile cygwin <<Scan Mail hat keinen Virus gefunden>> felix.schaller
2001-10-29 13:11 ` Gerrit P. Haase
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=3bdf0529.1a1e.0@ieg.com.br \
--to=kevinm@ieg.com.br \
--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).