I have a problem compiling the Nettle module on my newly installed debian linux. It looks like nettle_config.h is based on machine.h.in instead of nettle_config.h.in. This of course has the effect that the Nettle module is empty even though configure finds all dependencies and declare Nettle....yes. Suggestions?
Symptoms are similar to what I had some week ago. I didn't have enough clue about the pike build system to figure it out. (I also use debian).
/ Niels Möller (vässar rödpennan)
Previous text:
2004-02-17 06:18: Subject: Nettle on debian
I have a problem compiling the Nettle module on my newly installed debian linux. It looks like nettle_config.h is based on machine.h.in instead of nettle_config.h.in. This of course has the effect that the Nettle module is empty even though configure finds all dependencies and declare Nettle....yes. Suggestions?
/ Martin Nilsson (saturator)
It looks like YAAP (yet another autosomething problem). Pike runs autoheader -Wno-obsolete --prepend-include=/path/to/Pike/7.5/src and autoheader 2.59 uses the configure.in in src as template file, even if you add an explicit template file to autoheader. Party. It might be that the arguments are lost in translation by the wrapper script that selects the right autofoo based on magic, but my bet is that the autoheader developers are morons.
Why do we need --prepend-include in the first place?
/ Martin Nilsson (saturator)
Previous text:
2004-02-17 10:06: Subject: Nettle on debian
Symptoms are similar to what I had some week ago. I didn't have enough clue about the pike build system to figure it out. (I also use debian).
/ Niels Möller (vässar rödpennan)
--prepend-include is the new name for --localdir. It points out the directory where aclocal.m4 is.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-02-19 11:30: Subject: Nettle on debian
It looks like YAAP (yet another autosomething problem). Pike runs autoheader -Wno-obsolete --prepend-include=/path/to/Pike/7.5/src and autoheader 2.59 uses the configure.in in src as template file, even if you add an explicit template file to autoheader. Party. It might be that the arguments are lost in translation by the wrapper script that selects the right autofoo based on magic, but my bet is that the autoheader developers are morons.
Why do we need --prepend-include in the first place?
/ Martin Nilsson (saturator)
It looks like YAAP (yet another autosomething problem). Pike runs autoheader -Wno-obsolete --prepend-include=/path/to/Pike/7.5/src and autoheader 2.59 uses the configure.in in src as template file
Ooops. Send a bug report?
Party. It might be that the arguments are lost in translation by the wrapper script that selects the right autofoo based on magic
Are you talking about the debian wrapperscript? That's at least not the case for me, I have my own autoconf-2.59 installed in /usr/local.
/ Niels Möller (vässar rödpennan)
Previous text:
2004-02-19 11:30: Subject: Nettle on debian
It looks like YAAP (yet another autosomething problem). Pike runs autoheader -Wno-obsolete --prepend-include=/path/to/Pike/7.5/src and autoheader 2.59 uses the configure.in in src as template file, even if you add an explicit template file to autoheader. Party. It might be that the arguments are lost in translation by the wrapper script that selects the right autofoo based on magic, but my bet is that the autoheader developers are morons.
Why do we need --prepend-include in the first place?
/ Martin Nilsson (saturator)
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum -
Martin Nilsson (saturator) ＠ Pike (-) developers forum
-
Niels M�ller (v�ssar r�dpennan) ＠ Pike (-) developers forum