#### Making dynamic: post_modules/Bz2 #### Making dynamic: post_modules/COM #### Making dynamic: post_modules/CritBit /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh precompile.pike --api=4 >"/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c" "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod" || { rm "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c"; exit 1; } precompile: pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /usr/bin/pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/master.pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=Q) /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh: line 202: 6078 Segmentation fault $RUNPIKE $SCRIPT "$@" 1>&5
The "Unsupported API version" sounds suspicious. I was/am using Debian-testing Pike7.8 to bootstrap. Anything obvious I'm missing?
I've run into the "Unsupported API version" problem. Usually it means that the pike you're using to do the precompiling is too old or too new. CritBit was added in November, so it probably requires a new pike (which it seems to figure out, eventually). So, I don't think it's related to your segfault.
Bill
On Wed, 28 Mar 2012, Stephen R. van den Berg wrote:
#### Making dynamic: post_modules/CritBit /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh precompile.pike --api=4 >"/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c" "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod" || { rm "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c"; exit 1; } precompile: pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /usr/bin/pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/master.pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=Q) /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh: line 202: 6078 Segmentation fault $RUNPIKE $SCRIPT "$@" 1>&5
The "Unsupported API version" sounds suspicious. I was/am using Debian-testing Pike7.8 to bootstrap. Anything obvious I'm missing?
#### Making dynamic: post_modules/CritBit /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh precompile.pike --api=4 >"/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c" "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod" || { rm "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c"; exit 1; } precompile: pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /usr/bin/pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ) Unsupported API version: 4 (max: 3) precompile: /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/master.pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=Q) /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh: line 202: 6078 Segmentation fault $RUNPIKE $SCRIPT "$@" 1>&5
The "Unsupported API version" sounds suspicious.
It's actually as designed. The intent is to force old precompilers (which would generate broken code) to fail, so that the precompile script can change to a different method (which as you can see, it does). Your actual problem is that your newly built pike dumps core. This is most likely due to your version of gcc being too smart and breaking the machine-code support (are you compiling --with-abi=32?).
Try compiling --without-machine-code.
I was/am using Debian-testing Pike7.8 to bootstrap. Anything obvious I'm missing?
Not really, I haven't had time to get the 32-bit x86 machine-code support to work with recent gcc.
Stephen.
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Try compiling --without-machine-code.
I was/am using Debian-testing Pike7.8 to bootstrap. Anything obvious I'm missing?
Not really, I haven't had time to get the 32-bit x86 machine-code support to work with recent gcc.
Well, I actually guessed this already, trying a recompile as we speak.
Stephen R. van den Berg wrote:
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Try compiling --without-machine-code.
I was/am using Debian-testing Pike7.8 to bootstrap. Anything obvious I'm missing?
Not really, I haven't had time to get the 32-bit x86 machine-code support to work with recent gcc.
Well, I actually guessed this already, trying a recompile as we speak.
That was it, works now.
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Not really, I haven't had time to get the 32-bit x86 machine-code support to work with recent gcc.
Well, I actually guessed this already, trying a recompile as we speak.
I've now had a look at the 32-bit x86 machine-code generator in Pike 7.9, and it should now hopefully work with recent gcc. I changed calling convention to the SysVr4 standard ABI for IA32 and implemented the OPCODE_INLINE_RETURN method. This should make it more resistant to C compiler changes.
Please test.
/grubba
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Not really, I haven't had time to get the 32-bit x86 machine-code support to work with recent gcc.
Well, I actually guessed this already, trying a recompile as we speak.
I've now had a look at the 32-bit x86 machine-code generator in Pike 7.9, and it should now hopefully work with recent gcc. I changed calling convention to the SysVr4 standard ABI for IA32 and implemented the OPCODE_INLINE_RETURN method. This should make it more resistant to C compiler changes.
Please test.
Seems to work fine so far.
pike-devel@lists.lysator.liu.se