* Ralf Wildenhues wrote on Wed, Jul 16, 2008 at 11:39:00PM CEST:
> > Is there a proper automake way of installing startup scripts?
>
> Try
> init_d_dir = $(sysconfdir)/rc.d/init.d
> init_d_dir_SCRIPTS = blah
The last line should've been
init_d_SCRIPTS = blah
Sorry about that.
Cheers,
R
Hello Vikram,
* Vikram Ambrose wrote on Wed, Jul 16, 2008 at 10:38:04PM CEST:
> install:
That should've been install-exec-local.
>install -D -m 755 $(sysconfdir)/rc.d/init.d/blah
>
> uninstall:
>rm $(sysconfdir)/rc.d/init.d/blah
>
> Is there a proper automake way of installing startup sc
Currently I have to add my own rule
install:
install -D -m 755 $(sysconfdir)/rc.d/init.d/blah
uninstall:
rm $(sysconfdir)/rc.d/init.d/blah
Is there a proper automake way of installing startup scripts?
Vikram.
* Bob Friesenhahn wrote on Wed, Jul 16, 2008 at 05:01:28PM CEST:
> On Wed, 16 Jul 2008, Ralf Wildenhues wrote:
>>> execution. Is this within the realm of possibility for future Automake?
>>
>> No idea. How are you doing it now?
>
> I am not doing it now, but an example of its successful use is in
On Wed, 16 Jul 2008, Ralf Wildenhues wrote:
execution. Is this within the realm of possibility for future Automake?
No idea. How are you doing it now?
I am not doing it now, but an example of its successful use is in the
GCC build when built via 'make profiledbootstrap'. For the last
sev
Hi,
Herbert Euler <[EMAIL PROTECTED]> writes:
> I encountered a problem using version.texi with GNU make: after
> changing the version of my project in configure.in GNU make has to be
> executed twice to get the correct version number in the info document.
> I had sent a mail to the bug-make mail
