How is that relevant to the discussion? Show me a single place where the pexts, php4 or caudium C Pike modules need the Pike interpreter to compile and link.
There's more than one way to do it. pike -x module is one way, used by some pike modules, and it is one way that is recommended by the pike developers. It is expected to work on all pike installations, and it works fine when installing pike with the standard ./configure && make && make install. Marcus complained that pike -x module was broken in the current debian package. That's what the discussion is about, as far as I can tell.
If you can build some modules without using pike -x module, that's fine too, but not really relevant to modules that do use pike -x module.
/ Niels Möller (vässar rödpennan)
Previous text:
2004-01-26 21:51: Subject: Re: Pike @ Debian
On Mon, Jan 26, 2004 at 09:35:08PM +0100, Per Hedbor () @ Pike (-) developers forum scribbled:
Well, debian is way less flexible. And you seem to be intentionally
The difference is that it's pike one installs in Debian and not Debian in Pike.
minsunderstandning things in texts we write.
yep, as always. You should have gotten used to that.
Pike modules are internal to the pike build process.
How is that relevant to the discussion? Show me a single place where the pexts, php4 or caudium C Pike modules need the Pike interpreter to compile and link.
marek
/ Brevbäraren
pike-devel@lists.lysator.liu.se