From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Problem w/ gcc: sensitive to path it was invoked on...
Date: Wed, 15 Jan 2014 21:28:00 -0000 [thread overview]
Message-ID: <52D6FD6F.9000907@tlinx.org> (raw)
In-Reply-To: <loom.20140115T093618-321@post.gmane.org>
Mark Geisert wrote:
> Linda Walsh writes:
> > Can't believe doesn't work for anyone.
> >
> > For me, I've tried multiple c progs (simple ones),
>
> You don't supply any example that shows your attempt and the resulting error
> message(s). So maybe it (whatever *it* is) is working for everybody else?
----
Um...*simple*...like:
law.Bliss> uname -a
CYGWIN_NT-6.1 Athenae 1.7.27(0.271/5/3) 2013-12-09 11:54 x86_64 Cygwin
law.Bliss> cd bin
law.Bliss/bin> cat hello.c
main() {
printf("Hello World\n");
}
law.Bliss/bin> gcc -o hello hello.c
gcc: error: spawn: No such file or directory
====
> 1> Path: C:\Users\law.Bliss\bin\lib
> 2> C:\usr\sbin
> 3> C:\bin
> 4> C:\sbin
> 5> .
> 6> C:\prog64\vim\gvim.exe
> 7> C:\bin
> 8> C:\sbin
> -----
>
> There was some discussion recently, last month I think, about the relative
> position of /bin and /usr/bin in PATH mattering in a way it didn't use to.
> I can't find the discussion or I'd link to it. But in any case you might
> try substituting /usr/bin for /bin in your PATH setup.
----
...hmmm...this is ugly...
law.Bliss/bin> PATH=/usr/bin:$PATH
law.Bliss/bin> gcc -o hello hello.c
hello.c: In function 'main':
hello.c:2:1: warning: incompatible implicit declaration of built-in function
'printf' [enabled by default]
printf("Hello World\n");
^
law.Bliss/bin> hello
Hello World
gcc is sensitive to the path it was invoked on?... gcc bug?
--
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
next prev parent reply other threads:[~2014-01-15 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 7:34 Problem w/ gcc: error: spawn: No such file or directory; cygcheck.out attached Linda Walsh
2014-01-15 8:45 ` Mark Geisert
2014-01-15 21:28 ` Linda Walsh [this message]
2014-01-15 21:44 ` Problem w/ gcc: sensitive to path it was invoked on Larry Hall (Cygwin)
2014-01-15 22:15 ` Problem w/ gcc: error: spawn: No such file or directory; cygcheck.out attached 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=52D6FD6F.9000907@tlinx.org \
--to=cygwin@tlinx.org \
--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).