[Xquartz-dev] X11 2.2.0_rc1
Peter O'Gorman
peter at pogma.com
Fri Mar 28 11:56:31 PDT 2008
Jeremy Huddleston wrote:
>> I do not think removal of xmkmf at this time is advisable, due to this
>> autoconf limitation :(
>
> 1) Installing the 2.2.0 release over an existing install will not delete
> xmkmf and imake.
> 2) This is a developer issue, not an end-user issue.
> * I realize that this is not quite that clear-cut. End-users use
> fink which compiles code.
> 3) This has an easy workaround and a fix
> * I have also forwarded this issue internally, so it is known by the
> group maintaining autoconf for Apple as well.
>
> I will not be re-adding xmkmf and imake as a workaround for this issue.
> The real fix is to autoconf.
It will take several years for all autoconf using projects to update to
a fixed autoconf.
However, Fink and MacPorts can add packages for both xmkmf and imake
(even a fake one that simply generates enough of a Makefile for the
autoconf test would do - perhaps have this installed somewhere in the
path as fakexmkmf:
#! /bin/sh
echo 'INCROOT=/usr/X11/include' > Makefile
echo 'USRLIBDIR=/usr/X11/lib' >> Makefile
echo 'LIBDIR=/usr/X11/lib/X11' >> Makefile
cat Imakefile >> Makefile
Then ./configure XMKMF=$(which xmkmf || echo fakexmkmf) should work.
I understand your point of view,
Peter
--
Peter O'Gorman
http://pogma.com
More information about the Xquartz-dev
mailing list