Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Fri, 26 Apr 2002 12:08:06 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: setup changes to build standalone
Message-ID: <20020426160806.GA8584@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <FC169E059D1A0442A04C40F86D9BA7600C5F04 AT itdomain003 DOT itdomain DOT net DOT au> <3CC8D3A1 DOT 7070605 AT ece DOT gatech DOT edu> <3CC947F0 DOT E40FCB4A AT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3CC947F0.E40FCB4A@yahoo.com>
User-Agent: Mutt/1.3.23.1i

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
>translations.

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.
Hmm:

    Subject: Help!!!!!!!!!!!!


    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
-mno-cygwin.

cgf