From: Corinna Vinschen <vinschen@redhat.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org, mingw-patches@lists.sourceforge.net,
cygwin-patches@cygwin.com
Subject: Re: [RFC] Simplify MinGW canadian crosses
Date: Thu, 31 Aug 2006 11:34:00 -0000 [thread overview]
Message-ID: <20060830131552.GN20467@calimero.vinschen.de> (raw)
In-Reply-To: <20060829114107.GA17951@calimero.vinschen.de>
On Aug 29 13:41, Corinna Vinschen wrote:
> ChangeLogs:
> ===========
>
> Top-Level:
>
> * configure.in: Never build newlib for a Mingw host.
> Never build newlib as Mingw target library.
> Test the existence of winsup/cygwin for building a Cygwin newlib,
> rather than just winsup.
> Add winsup/mingw and winsup/w32api paths to FLAGS_FOR_TARGET if
> building a Mingw target.
> * configure: Regenerate.
>
> libiberty:
>
> * configure.ac: Add case for Mingw as host.
> * configure: Regenerate.
>
> winsup:
>
> * Makefile.in: Make installation of CYGWIN_LICENSE configurable.
> * acinclude.m4: Add GCC_NO_EXECUTABLES from config/no-executables.m4.
> * aclocal.m4: Regenerate.
> * configure.in: Add GCC_NO_EXECUTABLES call. Add configuration for
> INSTALL_LICENSE. Make cygwin subdirectory optional. Add sanity
> check for cygwin resp. mingw subdirectories dependent of the target.
> * configure: Regenerate.
>
> winsup/mingw:
>
> * Makefile.in: Add with_cross_host to allow more granular checks.
> Set installation directories accordingly. Override CC setting only
> if building a Cygwin target.
> * aclocal.m4: Regenerate from ../acinclude.m4.
> * configure.in: Move AC_CANONICAL_SYSTEM check up. Add
> GCC_NO_EXECUTABLES. Substitute with_cross_host in depending files.
> Test AC_ALLOCA only if building on a native system.
> * configure: Regenerate.
>
> winsup/w32api:
>
> * configure.in: Substitute with_cross_host in depending files.
> * configure: Regenerate.
> * lib/Makefile.in: Add with_cross_host to allow more granular checks.
> Set installation directories accordingly.
> * lib/ddk/Makefile.in: Ditto.
> * lib/directx/Makefile.in: Ditto.
I applied these patches to the sourceware repository. I have no
checkin privileges to gcc and mingw, so, could somebody having
these rights apply the appropriate patches there?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
next prev parent reply other threads:[~2006-08-30 13:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 13:04 Corinna Vinschen
2006-08-29 13:06 ` Daniel Jacobowitz
2006-08-29 15:32 ` DJ Delorie
2006-08-29 15:35 ` Daniel Jacobowitz
2006-08-29 15:38 ` DJ Delorie
2006-08-29 15:44 ` Daniel Jacobowitz
2006-08-29 16:00 ` DJ Delorie
2006-08-29 15:47 ` Corinna Vinschen
2006-08-29 16:04 ` Daniel Jacobowitz
2006-08-29 16:09 ` Corinna Vinschen
2006-08-29 16:53 ` Daniel Jacobowitz
2006-08-29 17:51 ` Corinna Vinschen
2006-08-29 16:08 ` Christopher Faylor
2006-08-29 16:49 ` Corinna Vinschen
2006-08-29 17:01 ` Daniel Jacobowitz
2006-08-29 17:04 ` Corinna Vinschen
2006-08-29 18:35 ` Christopher Faylor
2006-08-30 9:16 ` Christopher Faylor
2006-08-30 12:33 ` Corinna Vinschen
2006-08-29 15:24 ` DJ Delorie
2006-08-31 11:34 ` Corinna Vinschen [this message]
2006-08-31 12:09 ` Danny Smith
2006-08-30 20:32 Danny Smith
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=20060830131552.GN20467@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=binutils@sourceware.org \
--cc=cygwin-patches@cygwin.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mingw-patches@lists.sourceforge.net \
/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