From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2173 invoked by alias); 24 Jul 2008 05:26:26 -0000 Received: (qmail 2163 invoked by uid 22791); 24 Jul 2008 05:26:26 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.183) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 24 Jul 2008 05:25:58 +0000 Received: by py-out-1112.google.com with SMTP id w53so1530682pyg.25 for ; Wed, 23 Jul 2008 22:25:56 -0700 (PDT) Received: by 10.64.208.20 with SMTP id f20mr274079qbg.67.1216877155452; Wed, 23 Jul 2008 22:25:55 -0700 (PDT) Received: from ?192.168.0.101? ( [24.76.249.6]) by mx.google.com with ESMTPS id s35sm10742251qbs.13.2008.07.23.22.25.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jul 2008 22:25:54 -0700 (PDT) Message-ID: <48881261.3080504@users.sourceforge.net> Date: Thu, 24 Jul 2008 05:26:00 -0000 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: [RFC] 1.7 Packaging: Toolchain Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-07/txt/msg00115.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I would like to make some proposals as to setting up the development toolchain for 1.7: 1) binutils Thanks to cgf, we've got a current binutils available now; I'm not sure if binutils itself benefits from 1.7 (save the long path handling). There is one issue which, while not a showstopper, would be helpful to fix , which has yet to see a response from upstream. 2) gcc There are several issues to consider here: a) _GLIBCXX_USE_WCHAR_T Will std::wstring and friends be possible with cygwin-1.7? If not, is there anything that can be done to make it possible? b) 3.4 vs. 4.3 I see little reason to work on gcc-4.3 for cygwin-1.5 at this point. But this would be a great time to make the jump in release-2. Dave, I know you're working on 4.3, so could you give us a status report? Besides wstring, what is the story with shared gcc libraries (libgcc, libstdc++, etc.)? If either of these changes to gcc will be available (particularly 4.3 and/or shared libs), then we'll want that version of gcc available in release-2 ASAP. c) -mno-cygwin IMHO it's time for this insanity to end. Too many 3PPs abuse Cygwin as if it were MSYS, and new users just seem to get confused by it. I imagine it must make gcc that much harder to maintain as well. What we should do is treat mingw32 as any other cross-compiling target, by providing i686-pc-mingw32-* binutils and gcc, and move /usr/{include,lib}/mingw to /usr/i686-pc-mingw32/ (currently these are symlinks). It may not be a pressing issue itself, but while we're making changes anyway, isn't now the time? 3) libtool I've been using libtool-2.2 exclusively for three months now, and it's working pretty well. A few packages need minor patches to compensate, but these are usually fairly simple, and some patches are already available from Gentoo. As for the LT_OUTPUT in AC_PROG_LIBTOOL issue, as upstream rejected the patch, we could do without it if we don't have to worry about supporting libtool-1.5 in release-2. So Chuck, would you agree with making 2.2 stable in release-2? 4) gettext BTW Chuck, any chance of a version bump? 0.15 is getting pretty stale already. 5) cygport cygport will need some changes for 1.7, and there's a few things that would greatly benefit from some slight API breakage. So my plan right now is to push 0.3.13 soon as stable, create an 0.3 branch for 1.5, and start working on a 1.7-only version of cygport in HEAD. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiIEmEACgkQpiWmPGlmQSMxxACdHMMTrARzqzniGy3lU0stUyfU qGoAnRmcY9kQGipt/6lkXN8jnbMO1TBZ =6fV+ -----END PGP SIGNATURE-----