This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: I broke cygport
- From: "Yaakov S (Cygwin Ports)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-ports-general at lists dot sourceforge dot net, cygwin-apps at cygwin dot com
- Date: Tue, 17 Oct 2006 23:50:29 -0500
- Subject: Re: I broke cygport
- References: <20a807210610170515t3f314b03h738774646e890095@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vin Shelton wrote:
> Have you had a chance to look at my patch which allows over-riding the
> individual configure arguments in cygconf()? The patch is a
> definitely a brute force approach, but something like it is necessary
> to support XEmacs (or other packages that don't fully comply with
> autoconf conventions).
cygconf is intended only for autoconf-based configure scripts. I'm not
familiar with XEmacs, but I do know that autoconf-based configures will
just ignore unknown arguments, so I will guess that XEmacs' configure is
not autoconf-based.
Non-autoconf-based configure scripts should do something like:
lndirs
cd ${B}
./configure <args> || error "configure failed"
cygmake
Note that this is consistent with Portage; the current xemacs ebuild[1]
does not use econf either.
[1]
http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/app-editors/xemacs/xemacs-21.4.19.ebuild
> I will update the patch to the latest version of cygport if you want.
In general, all patches for cygport should be made against CVS HEAD, but
I don't think this needs a patch.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNbKVpiWmPGlmQSMRAtVVAKCb6iENVw1jvzKCVi/OTKAYvJK24ACbBKf3
mKabIE3D0eCb44O9KhBAuo0=
=QAXo
-----END PGP SIGNATURE-----