<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 14-02-12 05:50 PM, Gaetan Nadon
wrote:<br>
</div>
<blockquote cite="mid:52FBFAD3.3050805@videotron.ca" type="cite">
<pre wrap="">+AM_INIT_AUTOMAKE([foreign dist-bzip2 subdir-objects])
<span class="moz-txt-citetags">> </span></pre>
</blockquote>
This is not a new feature in 1.14, but it has never been used so
far. All 250 X modules have the same line. <br>
<br>
If you want to propose this, as it changes all of xserver, you would
have to test all 98 makefiles in xserver. Some of them are fairly
complex and I doubt the change would be easy.<br>
<br>
I don't have personal experience with subdir-objects feature, I'll
have a go at it. It's hard to believe that $(top_srcdir) would not
work anymore. There are most likely other changes to do in the
makefiles, other than just turning on the feature.<br>
<br>
Ok here is a good explanation, as someone already reported this:<br>
<br>
<a class="moz-txt-link-freetext" href="https://bugs.freedesktop.org/show_bug.cgi?id=69874">https://bugs.freedesktop.org/show_bug.cgi?id=69874</a><br>
<blockquote>New in 1.14:<br>
...<br>
<br>
- The next major Automake version (2.0) will unconditionally
activate<br>
the 'subdir-objects' option. In order to smooth out the
transition,<br>
we now give a warning (in the category 'unsupported') whenever
a<br>
source file is present in a subdirectory but the
'subdir-object' is<br>
not enabled. For example, the following usage will trigger
such a<br>
warning:<br>
<br>
bin_PROGRAMS = sub/foo<br>
sub_foo_SOURCES = sub/main.c sub/bar.c<br>
<br>
Long story short, we can ignore it until 2.0 is out, or
unconditionally set it in configure.ac. The latter one may be
preffered in order for us to test and make sure that mesa builds
correctly, otherwise we'll be badly surprised as automake 2.0
comes out (think bleeding edge distros/packagers reporting a dozen
of bugs)<br>
<br>
</blockquote>
Looks like we will have to do something about it, but it can't be
blasting ../../../ by the millions :-)<br>
<br>
<br>
<br>
<blockquote>
</blockquote>
</body>
</html>