X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Grant Edwards Subject: Re: setup 2.573.2.3 configure fails libgpg-error/libgcrypt Date: Tue, 13 Jan 2009 23:03:04 +0000 (UTC) Lines: 43 Message-ID: References: <2ca21dcc0901131429s3ef295e1r1146d761aed7d22c AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: slrn/pre0.9.9-102 (Linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2009-01-13, Grant Edwards wrote: > On 2009-01-13, Dave Korn wrote: > >> Looking in the snapshot tarball, it seems that configure.in >> does indeed have the original (unpatched or reverted) code, so >> why doesn't it have the gpg-error-config-fake script as well? >> I went digging in the source directory where I originally >> built the tarball that's currently on the cygwin website, and >> the file is there in the sources, but it's not in the >> generated tarball! > > I know that feeling... > >> It turns out that adding files to the sources doesn't >> automatically cause them to end up in the source tarball; you >> need to list them explicitly. That happens for you if they're >> C or C++ source or header files, but not for shell scripts. >> Argh, my bad! Thanks for spotting it. > > [...] > >> You can download a copy from the sourceware CVS repository via >> the web interface here: >> >> http://cygwin.com/cgi-bin/cvsweb.cgi/~checkout~/setup/gpg-error-config-fake?cvsroot=cygwin-apps >> >> and drop it in with the rest of the sources. > > I grabbed a copy out of CVS, and it built fine and is working. Just for the sake of documenting what didn't work, I also tried deleting the usage of the "fake" config utility from the configure script, and that failed because it then used the cygwin system's already-installed gpg-error libraries. Those are "Cygwin" libraries and what's required are "Mingw" libraries, so the final linking step failed. That's pretty much what I had expected since setup.exe isn't a Cygwin application. -- Grant Edwards grante Yow! I'm encased in the at lining of a pure pork visi.com sausage!! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/