From: sweinberger <sarahmarci@jmr.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin and Windows Paths Leaking Through
Date: Thu, 26 May 2011 20:17:00 -0000 [thread overview]
Message-ID: <31711473.post@talk.nabble.com> (raw)
In-Reply-To: <4DDEB26B.1080509@cwilson.fastmail.fm>
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.
I did just that.
I downloaded binutils-2.21 and expanded everything into a new empty folder.
Here is where I downloaded everything to:
/usr/local/binutils-2.21.
/binutils-2.21 is a new folder.
I changed directories to that folder, executed the .configure line, in my
case,
./configure --target=mips-elf
and I then entered "make" (without the double quotes).
I got most of the way through, but keeled over in the ld subfolder with the
error message shown above.
The make file changed the active path to /usr/local/bin-utils-2.21/ld
The make file then executed:
LIB_PATH='' /bin/sh ./genscripts.sh "." "/usr/local/lib" "/usr/local"
"/usr/local" i686-pc-cygwin mips-unknown-elf mips-elf "elf32ebmip"
"/usr/local/lib /lib /usr/lib" no elf32ebmip "mips-elf"
You can type the above command line directly and get the same error, namely:
: No such file or directory line 2: ./emulparams/elf32bmip.sh
The shell script thinks that ./emulparams/elf32bmip.sh does not exist. From
its point of view it does not, because of Windows path / Cygwin path
differences. The shell script thinks of the path as C:/.../elf32bmip.sh for
whatever reason. The relative path does not matter.
Thanks,
Sarah
--
View this message in context: http://old.nabble.com/Cygwin-and-Windows-Paths-Leaking-Through-tp31711163p31711473.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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:[~2011-05-26 20:17 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
2011-05-26 20:17 ` sweinberger [this message]
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=31711473.post@talk.nabble.com \
--to=sarahmarci@jmr.com \
--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).