Mail Archives: cygwin-apps/2002/04/26/12:13:37
On Fri, Apr 26, 2002 at 08:28:32AM -0400, Earnie Boyd wrote:
>This is good. IMO, there should be no binaries not dependent on
>cygwin1.dll in the /bin a.k.a. /usr/bin and that the /bin and /usr/bin
>directories be marked as --cygwin-executable. One reason for doing this
>is that it speeds the execution process for spawning by avoiding win32
Yeah, there are now two binaries in /usr/bin, et al that are non-cygwin:
strace and cygcheck. If you have /bin and /usr/bin mounted with -X, it should speed
up execution of programs in that directory but it will screw up operation
of strace.exe and cygcheck.exe.
I don't know how to fix that. Maybe there should be a /usr/ncbin or something.
I try to run the starce program like Larry Hlal said it and the cygwin
says "stcrae: No such file or dirctorY"!!!!!
Where I get this porgram?????
>> >>2) The above won't work in a cross build environment. You could say
>> >> CC='i686-pc-cygwin-gcc -mno-cygwin'..., I guess.
>> > for cross compiles:
>> > ../setup/configure --host=i686-pc-mingw32 --build-i686-pc-linux
>> > should do it (assuming a mingw32 cross compiler is present), or a
>> > combination using the CC string you have above with the mingw host will
>> > work too.
>> whatever happened to the idea of an official cygwin package, that
>> contained a true cygwin-host, mingw-target cross compiler? Didn't
>> somebody or other volunteer to provide that?
>Oh, I thought about it sometime ago, I've been busy with MSYS and have
>decided against my maintaining another package. Perhaps when Danny gets
>3.1 up he can provide a Cygwin hosted Mingw32 targeted set of binaries.
>I also remember a discussion on one of Cygwin's lists about using
>scripts and symlinks to emulate this and may be the smartest way to go
>about providing cross build emulation.
>> (Granted, we still need 'cygwin-gcc -mno-cygwin' for the "self-hosting"
>> feature of cygwin1.dll, but there's no real need to *require* cygwin-gcc
>> -mno-cygwin for setup.exe, now that setup has been moved out of the
>> winsup tree)
>Well, if you had a mingw32-gcc (cygwin hosted, mingw32 targeted) then
>you could use that instead of `gcc -mno-cygwin'.
This would complicate the cygwin build process. We will always need
- Raw text -