public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Cc: timclarke147@gmail.com
Subject: Re: gcc 32 bit compiler does not like files outside of c:\cygwin
Date: Fri, 16 Mar 2018 21:52:00 -0000	[thread overview]
Message-ID: <ddfc6cb1f046ba9f22f805e9df45d741@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <9cd3644d-4a84-3c80-c717-254b99125b02@gmail.com>

On Fri, 16 Mar 2018 16:45:11, Tim Clarke wrote:
> Sorry, posted this from my other non-regsitered email address!!
> 
> Following my previous post advising that the gcc 32 compiler was
> exiting immediately (return code 1) without doing anything, I have
> now established what is happening.
> The behaviour exhibited is contrary to that exhibited by gcc 64 bit,
> which works fine.
> 
> When entering the cygwin console and typing:
> cd d:/c
> the screen displays
> /cydrive/d/c
> 
> gcc  sourcefile.c
> does nothing and 'echo $?'  displays  1
> 
> However
> cd /usr/src
> gcc sourcefile.c   works  ok
> 
> So, it would appear that, for some reason, the 32bit compiler
> falls over when accessing files outside of the main c:\cygwin
> hierarchy !

Please, do not make us guess (what is wrong with your system).

    https://cygwin.com/problems.html

    "Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment
    in your report. Please do not compress or otherwise encode the output. Just
    attach it as a straight text file so that it can be easily viewed."

@@ uname -a
CYGWIN_NT-6.1-WOW Seven 2.10.1(0.325/5/3)  i686 Cygwin

@@ gcc --version
gcc (GCC) 6.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@@ cd d:/Abyss
@@ pwd
/drv/d/Abyss

@@ vi srcfil.c
@@ gcc srcfil.c
@@ ./a
Hello, world
@@ mount
E:/Cygwin/bin on /usr/bin type ntfs (binary,auto)
E:/Cygwin/lib on /usr/lib type ntfs (binary,auto)
E:/Cygwin on / type ntfs (binary,auto)
C: on /drv/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /drv/d type ntfs (binary,posix=0,user,noumount,auto)
E: on /drv/e type ntfs (binary,posix=0,user,noumount,auto)
X: on /drv/x type ntfs (binary,posix=0,user,noumount,auto)

Henri


--
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:[~2018-03-16 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 17:45 Tim Clarke
2018-03-16 21:52 ` Houder [this message]

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=ddfc6cb1f046ba9f22f805e9df45d741@smtp-cloud7.xs4all.net \
    --to=houder@xs4all.nl \
    --cc=cygwin@cygwin.com \
    --cc=timclarke147@gmail.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).