From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1906 invoked by alias); 9 Feb 2015 20:59:24 -0000 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 Received: (qmail 1894 invoked by uid 89); 9 Feb 2015 20:59:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: out1-smtp.messagingengine.com Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 09 Feb 2015 20:59:22 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D739F20D9D for ; Mon, 9 Feb 2015 15:59:20 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 09 Feb 2015 15:59:20 -0500 Received: from [192.168.1.102] (unknown [86.179.113.106]) by mail.messagingengine.com (Postfix) with ESMTPA id 6B0BD680133; Mon, 9 Feb 2015 15:59:20 -0500 (EST) Message-ID: <54D91FA4.8060302@dronecode.org.uk> Date: Mon, 09 Feb 2015 20:59:00 -0000 From: Jon TURNEY User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: cygwin-apps@cygwin.com CC: Achim Gratz Subject: Re: [HEADSUP] Moving setup sources to git References: <20150209162434.GD5633@calimero.vinschen.de> <87386evpen.fsf@Rainer.invalid> In-Reply-To: <87386evpen.fsf@Rainer.invalid> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-02/txt/msg00120.txt.bz2 On 09/02/2015 19:46, Achim Gratz wrote: > Frank Fesevur writes: >> README says I need various mingw libs. But if IIRC mingw is not >> recommended anymore. I have installed mingw64 and the mingw64 variants >> of those libs. But there is no mingw64 variant of liblzma. I've >> installed all 5 packages containing "liblzma", but configure seems to >> be unable to find it. >> >> Do I still need the original mingw to compile setup or is the README outdated? > > I still carry the README patch below locally since it was not accepted > the last time around and it will likely need a few changes to be > up-to-date with today's reality. For instance libgetopt++ is now > included in the tree, while I'd have preferred if it was a subtree or > submodule, which is more closely in line with the state it had in CVS. > > --8<---------------cut here---------------start------------->8--- > ------------------------------------ README ------------------------------------ > index b1586de..0499c6c 100644 > @@ -3,33 +3,39 @@ for the Cygwin net releases. > > HOW TO BUILD: > ------------- > Setup should build out-of-the-box on any Cygwin environment that has all the > required packages installed: > - - mingw-gcc-g++ > - make > - - mingw-bzip2 > - - mingw-libgcrypt-devel > - - mingw-liblzma-devel > - - mingw-zlib > - - and all packages that are dependencies of the above, i.e. gcc-mingw-core, > - mingw-runtime, binutils, w*api, etc. > + - mingw64-gcc-g++ > + - mingw64-bzip2 > + - mingw64-libgcrypt > + - mingw64-xz > + - mingw64-zlib > + - and all packages that are dependencies of the above I'm not sure these are actually package names since they are missing the arch? > - upx (optional) > > The following additional packages are required if building from CVS, not from > a source tarball, or if you want to make changes to the build system. > - recent autoconf > - recent automake > - recent libtool > - flex > - bison > > +Additionally, libgetopt++ (also available from the cygwin-apps CVS at > +sourceware.org) must be available directly as a subdirectory > +libgetopt++ within the setup source directory. It should be > +automatically populated by CVS, but if you are using tools like > +CVSgrab, you may need to fetch this yourself. > + This doesn't make sense anymore. > Build commands: > 1) Configure using this option > $ /path/to/setup/bootstrap.sh > - This will automatically rebuild configure files and run configure in the > - current directory. > + This will automatically rebuild configure files and run configure > + in the current directory. The current directory must be outside > + the source tree. This isn't true.