Preparing for automake 1.14

Jeremy Huddleston Sequoia jeremyhu at freedesktop.org
Mon Jan 14 14:57:58 PST 2013


On Jan 14, 2013, at 1:46 PM, Gaetan Nadon <memsize at videotron.ca> wrote:

> On 13-01-14 11:07 AM, Alan Coopersmith wrote:
>> On 01/13/13 11:52 PM, Jeremy Huddleston Sequoia wrote:
>>> While it's good to prepare for 1.14, we're still not working with 1.13 yet.  libX11 is failing with:
>>> 
>>> nls/Makefile.am:41: error: using '$(srcdir)' in TESTS is currently broken: '$(srcdir)/compose-check.pl'
>>> (see http://tinderbox.x.org/builds/2013-01-14-0001/logs/libX11/#configure)
>>> 
>>> and I'm not really sure what to do about that… any thoughts?
>> Didn't someone send a patch for that recently?   Unfortunately, I don't see it
>> on patchwork.
>> 
> Perhaps this would be the one:
> 
> http://patches.openembedded.org/patch/41927/
> 
> It simply disables the tests altogether.

Yeah, that's what I was going to do locally, but it would be nice to figure out a way to do it "correctly"

> In
> http://www.gnu.org/software/automake/manual/automake.html#Scripts_002dbased-Testsuites:
> 
>    Test programs that need data files should look for them in
>    *|srcdir|* (which is both a make variable and an environment
>    variable made available to the tests), so that they work when
>    building in a separate directory (see Build Directories
>    <http://www.gnu.org/software/automake/manual/autoconf.html#Build-Directories>),
>    and in particular for the |distcheck| rule (see Checking the
>    Distribution
>    <http://www.gnu.org/software/automake/manual/automake.html#Checking-the-Distribution>).
> 
> 
> Could it be that the perl script returns an error?

The perl script is never run.  The error is from running automake (from autoreconf from autogen.sh)

See: http://tinderbox.x.org/builds/2013-01-14-0001/logs/libX11/#configure

> Does it complete
> successfully when run manually? Any of the other 32 or so tools in the
> tool chain has also been upgraded (if this error occurs on a system
> where a wholesale upgrade has been done? Anyone else has reproduced the
> problem or claims success?




More information about the xorg-devel mailing list