Parser.XML.Simple seems to be lost in Pike-git 8.1.
Looks fine to me.
Pike v8.1 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
Parser.XML.Simple()->parse("<x/>", lambda(mixed ...args){ werror("%O\n",args);} );
({ /* 5 elements */ "<>", "x", ([ ]), 0, ([ /* 1 element */ "location": 4 ]) }) (1) Result: ({ })
Martin Nilsson (Coppermist) @ Pike (-) developers forum wrote:
Looks fine to me.
Ah. Well, it appears to work in the compilation tree.
But once you do "make install", the installation crashes at 42.3% and shows something like this:
Installing Pike in /usr/local/pike/8.1.11, please wait...
Precompiling: |==================== | 42.3 % Dumping of some modules failed (not fatal) (0x00000001): "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/XML.pmod/Tree.pmod" "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/C.pmod" "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/CSV.pike" "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/Pike.pmod" "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/Python.pmod" "/usr/local/pike/8.1.11/lib/modules/Parser.pmod/RCS.pike"
I.e. it ends with: Pike installation completed successfully.
But that's a lie. Because running the installed pike, then shows that something is wrong in Parser.XML. More specifically, this is what I get:
Pike v8.1 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
Parser.XML.Simple;
/usr/local/pike/8.1.11/lib/modules/Parser.pmod/XML.pmod/Tree.pmod:1536:Illegal program pointer. /usr/local/pike/8.1.11/lib/modules/Parser.pmod/XML.pmod/NSTree.pmod.o:-: Warning: Decode failed: Cannot resolve "Parser.XML.Tree". /usr/local/pike/8.1.11/lib/modules/Parser.pmod/XML.pmod/NSTree.pmod:7:Illegal program pointer.
(And a lot more).
Stephen R. van den Berg wrote:
Martin Nilsson (Coppermist) @ Pike (-) developers forum wrote:
Looks fine to me.
Ah. Well, it appears to work in the compilation tree.
But once you do "make install", the installation crashes at 42.3% and shows something like this:
Nevermind. Somehow the source tree required a complete wipe and fresh checkout to get it right. It works now.
Nevermind. Somehow the source tree required a complete wipe and fresh checkout to get it right. It works now.
This might give you a false sense of security. The dumping process dumps the modules in an order based on how the directories are listed by the filesystem. If there is a bug which causes dumping to fail if the modules are dumped in a particular order, then wiping the tree and doing a fresh checkout may change the order in which the modules are listed, simply hiding the issue for the time being. Then it pops up later, typically on someones build slave in pikefarm where you can't easily debug it. It has happened before, it will happen again...
I think we should fix this somehow, but can't quite decide on whether the best solution would be to make the order less random, or _more_ random...
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum -
Martin Nilsson (Coppermist) ＠ Pike (-) developers forum
-
Stephen R. van den Berg