public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Cygwin and Windows Paths Leaking Through
Date: Thu, 26 May 2011 20:05:00 -0000	[thread overview]
Message-ID: <4DDEB26B.1080509@cwilson.fastmail.fm> (raw)
In-Reply-To: <31711163.post@talk.nabble.com>

On 5/26/2011 3:32 PM, sweinberger wrote:
> Cygwin is supposed to provide an isolated environment totally shielding
> applications that run on the inside from even knowing that a Windows
> anything exists. 

I don't know where you got that idea.  It's perfectly fine to use w32api
functions in combination with cygwin/posix ones -- how do you think
mintty works? -- although you do need to be careful mixing stuff like
posix select() and w32 WaitFor*().

> That dmake and now something in genscripts does not, means
> that the Cygwin wall has some holes.
> 
> gcc -DHAVE_CONFIG_H -I.  -I. -I. -I../bfd -I./../bfd -I./../include  -g -O2
> -DENABLE_PLUGINS -DLOCALEDIR="\"/usr/local/share/locale\""  -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT
> ldemul.o -MD -MP -MF .deps/ldemul.Tp
> o -c -o ldemul.o ldemul.c
          ^^^^^^^^^^^^^^^^^
Here's your problem: binutils and gcc don't support compiling "in the
source tree".  You need to create a separate, empty build directory
*outside* the src directory, and run configure/make in there.

Dunno about your dmake problems, someone else will have to address that.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-05-26 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 19:33 sweinberger
2011-05-26 20:05 ` Charles Wilson [this message]
2011-05-26 20:17   ` sweinberger
2011-05-26 20:24     ` Charles Wilson
2011-05-26 21:21       ` sweinberger
2011-06-01  0:09 ` allowed Linux characters (and windows substitutes) Linda Walsh

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=4DDEB26B.1080509@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --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).