dynamic_module_makefile+specs, aclocal.m4, precompile* and the headers must _all_ go in separate directories. It doesn't seem there is a simple hack to work around it. aclocal.m4 (as Martin already said) would have to be a) cleaned up from the non-pike cruft, b) put in /usr/share/misc -

Would it help it it was called something other than "aclocal.m4"? It's an internal file to the pike build system, so it's frankly only Pikes business what it contains.

autoconf would find it there.

autoconf is not _supposed_ to find it, except when pointed to it by the build system. The rules are internal and not useful in a stand-alone configure script.

Can you give some kind of motivation at to what benefit your "rules" bring to the user? They seem pretty pointless and anal to me.

No, the system is nowhere near flexible. It would be so much easier to simply provide a pike.m4 file...

I'd say Debian is much less flexible than the build system is.

/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)

Previous text:

2004-01-26 20:45: Subject: Re: Pike @ Debian

---

On Mon, Jan 26, 2004 at 08:31:05PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled:

...

If master()->include_prefix points to the directory where the include files, dynamic_module_makefile, aclocal.m4 file, precompile.{pike,sh} files and specs file are, pike -x module should work yes. This is exactly what include_prefix is there for, and the only thing it is used for.

OK, so it won't work for Debian. It's not flexible enough. dynamic_module_makefile+specs, aclocal.m4, precompile* and the headers must _all_ go in separate directories. It doesn't seem there is a simple hack to work around it. aclocal.m4 (as Martin already said) would have to be a) cleaned up from the non-pike cruft, b) put in /usr/share/misc - autoconf would find it there. The precompile scripts should either go in /usr/bin (they would have to be renamed to pike-precompile* then) or in /usr/lib/pike/PIKEVER/bin, the dynamic_module_makefile and the specs file should most probably go in /usr/share/pike/PIKEVER/include No, the system is nowhere near flexible. It would be so much easier to simply provide a pike.m4 file...

marek

/ Brevbäraren