(
>
> I've tried running automake manually, with the verbose option:
[...]
> automake: reading /usr/share/automake-1.9/am/program.am
> test/Makefile.am: required file `gnuscripts/compile' not found
> automake: reading /usr/share/automake-1.9/am/compile.am
[...]
>
&
/Makefile.am
automake: reading /usr/share/automake-1.9/am/configure.am
automake: reading /usr/share/automake-1.9/am/progs.am
automake: reading /usr/share/automake-1.9/am/program.am
test/Makefile.am: required file `gnuscripts/compile' not found
automake: reading /usr/share/automake-1.9/am/compile
On Wed, Dec 30, 2009 at 21:59, Adam Mercer wrote:
>> Note that for library dependencies that apply to all programs in a
>> makefile you can use the "global" LDADD variable, which may allow you to
>> remove most if not all of those per-target *_LDADD settings.
>
> That's something I've been meanin
On Wed, Dec 30, 2009 at 21:37, Ralf Wildenhues wrote:
Ralf
> The rules generated by Automake may or may not need to use the -c and -o
> options at the same time. This depends upon a few internal details:
> whether the subdir-objects option is used, whether objects need to be
> renamed due to pe
Hi Adam,
* Adam Mercer wrote on Wed, Dec 30, 2009 at 11:57:27AM CET:
> On one of my projects I'm running into an issue, only on certain
> platforms, where the compile script isn't available. e.g. on CentOS 5
>
> $ autoreconf
> test/Makefile.am: required file `gnus
Hi
On one of my projects I'm running into an issue, only on certain
platforms, where the compile script isn't available. e.g. on CentOS 5
$ autoreconf
test/Makefile.am: required file `gnuscripts/compile' not found
autoreconf: automake failed with exit status: 1
$
yet I have oth
