errors or warnings.
My problem was as you said. I built from the source folder rather than a
new folder.
I learnt something new.
Thank you Chuck!
Sarah
--
View this message in context:
http://old.nabble.com/Cygwin-and-Windows-Paths-Leaking-Through-tp31711163p31711938.html
Sent from the Cygwin
On 5/26/2011 4:17 PM, sweinberger wrote:
>
>
> 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 binu
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 n
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 combin
r directory line 2: ./emulparams/elf32bmip.sh
make[4]: *** [eelf32ebmip.c] Error 1
make[4]: Leaving directory `/usr/local/binutils-2.21/ld'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/local/binutils-2.21/ld'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/us
5 matches
Mail list logo
