to, 2013-10-03 kello 19:08 -0400, Gaetan Nadon kirjoitti: > On 13-10-03 03:00 AM, Martin-Éric Racine wrote: > > ke, 2013-10-02 kello 20:16 -0400, Gaetan Nadon kirjoitti: > >> On 13-10-02 06:48 PM, Martin-Éric Racine wrote: > >>> ke, 2013-10-02 kello 14:36 -0400, Gaetan Nadon kirjoitti: > >>>> On 13-10-02 10:54 AM, Martin-Éric Racine wrote: > >>>>>> You cannot have an empty m4 dir under git control. Some project put a > >>>>>> dummy README file but I prefer putting a .gitignore there containing > >>>>>> the libtool stuff to ignore: > >>>>>> > >>>>>> libtool > >>>>>> libtool.m4 > >>>>>> ltmain.sh > >>>>>> lt~obsolete.m4 > >>>>>> ltoptions.m4 > >>>>>> ltsugar.m4 > >>>>>> ltversion.m4 > >>>>> I agree, since those are copied at libtool run time. > >>> Committed and pushed upstream. > >>> > >>> Since we were on the case of AC_CONFIG_MACRO_DIR([m4]), I figured that I > >>> might as well implement AC_CONFIG_AUX_DIR([build-aux]) as in this patch. > >>> Does it make sense to you? > >> I thought about this quite a while ago for the xorg modules. I came to > >> the conclusion that it would provide no benefits. The files that would > >> be placed in build-aux are just a small subset of the overall files in > >> the root dir. It looks like no one else has seen a benefit either. There > >> are over 200 modules in xorg, and none of them ever had it., or perhaps > >> just one. > >> > >> We basically use the root dir as a build-aux dir. Anything else goes in > >> subdirs with a Makefile.am. > > Sure enough, just as I thought that it would be safe to push this, I > > noticed that our build macros for maintainer-clean are hard-wired for > > removing autoconf stuff in (.) rather than use AC_CONFIG_AUX_DIR. *sigh* > BTW, the default value for of AC_CONFIG_AUX_DIR is ".".
Right, except that here we have configured a non-default value, which didn't propagate as it should have. This suggests a hard-coded value exists in one of the macro – or can you spot anything I forgot to implement this? Martin-Éric _______________________________________________ Xorg-driver-geode mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-geode
