Yes, that's been a long standing problem. Sometimes it happens,
sometimes not. It's so unreliable, I wish someone would just revert
it; it doesn't make sense to frustrate users in this way.
Bill
On Oct 29, 2009, at 10:34 AM, Arne Goedeke wrote:
> Ive had that bug for ages now. I think it was mentioned on the list
> before. I usually work around that by putting a link into the
> include directory pointing to the lib/ dir. I think the link is
> correct in case pike
> has not been installed yet. note sure.
>
> arne
>
> On Wed, 28 Oct 2009, Yvan Vander Sanden wrote:
>
>> Hi. I'm using the latest pike snapshot, and think i found a small
>> error. While trying to install a module with:
>> sudo pike -x monger --install Public.Parser.JSON2
>> I stumbled across this error:
>> precompile: pike /usr/local/pike/7.8.359/include/pike/
>> precompile.pike json.cmod
>> /usr/local/pike/7.8.359/include/pike/precompile.pike:2:Couldn't
>> read include file
>> "/usr/local/pike/7.8.359/include/lib/modules/Tools.pmod/
>> Standalone.pmod/precompile.pike".
>> obviously this precompile file includes an error:
>> #! /usr/bin/env pike
>> #include "../lib/modules/Tools.pmod/Standalone.pmod/precompile.pike"
>> and it should be like this:
>> #include "../../lib/modules/Tools.pmod/Standalone.pmod/
>> precompile.pike"
>> Not exactly hard to figure out, but I tought I'd mention it anyway.
>> Regards,
>> yvan
>> --
>> Copyright only exists in the imagination of those who do not have
>> any.
>>
|