This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [PATCH] Fix mingw32 bootstrap regression.
- From: Danny Smith <dannysmith at clear dot net dot nz>
- To: 'Carlos O'Donell' <carlos at codesourcery dot com>
- Cc: 'Bob Rossi' <bob_rossi at cox dot net>, gcc-patches at gcc dot gnu dot org, 'Mark Mitchell' <mark at codesourcery dot com>, cgf at gcc dot gnu dot org
- Date: Sat, 23 Dec 2006 11:50:57 +1300
- Subject: RE: [PATCH] Fix mingw32 bootstrap regression.
> On Fri, Dec 22, 2006 at 09:15:57PM +1300, Danny Smith wrote:
> > This way:
> > bash, sed, configure, make, expect, dejagnu, etc are cygwin tools
> > (cygwin1.dll-dependent).
> > The build gcc, binutils are from mingw (msvcrt.dll-dependent).
> > I've done it this way since well before msys.
>
> You run a native bootstrap using these tools?
Yes.
mingw binaries precede cygwin binaries in PATH (unless I actually logon
to cygwin).
mount table contains:
c:\cygwin\lib on /usr/lib type system (binm
c:\cygwin\usr on /usr type system (binmode)
c:\cygwin\bin on /bin type system (binmode)
c:\cygwin\bin on /usr/bin type system (binm
c:\cygwin on / type system (binmode)
c:\mingw on /mingw type system (binmode)
c:\developex on /developex type system (binmode
mingw binaries live in /mingw/bin
cygwin binaries live in /cygwin/bin
development sources and builds are all rooted in /developex
Thus native pathnames of all native components are same as cygwin
pathname
I have never needed to use msys. The cygwin tools have been more
reliable.
Danny
>
> Cheers,
> Carlos.