[Vm-dev] StackUnixDebugConfig gcc3x-interp.c .. conflicting types

Ben Coman btc at openinworld.com
Mon Dec 14 18:35:52 UTC 2015


(Sorry, I posted too soon. Updated...)

I'm trying to generate a debug VM from
https://github.com/pharo-project/pharo-vm.git.  I've backtracked to
try without the rump toolchain, using standard Debian 8 buildtools.

This works fine....
    ./pharo generator.image eval 'StackUnixConfig generateWithSources'
    cd pharo-vm/build
    bash build.sh   # essentially...   cmake . ; make

but this...
   StackUnixDebugConfig generateWithSources
   cd pharo-vm/build
   bash build.sh
produces "conflicting types" errors...

/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:8708:1:
error: conflicting types for ‘isNegativeIntegerValueOf’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:8761:1:
error: conflicting types for ‘magnitude64BitIntegerForneg’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:8817:1:
error: conflicting types for ‘magnitude64BitValueOf’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:20911:1:
error: conflicting types for ‘addressIsInPage’
...
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:45843:1:
error: conflicting types for ‘pruneStackstackp’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:46004:1:
error: conflicting types for ‘oopisGreaterThanOrEqualTo’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:46016:1:
error: conflicting types for ‘oopisGreaterThanOrEqualToandLessThan’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:46029:1:
error: conflicting types for ‘oopisGreaterThanandLessThan’
/home/ben/Repos/cogunikernel/pharo-vm/src/vm/gcc3x-interp.c:46042:1:
error: conflicting types for ‘oopisLessThan’


I am guessing that after the gnuifying step when interp.c gets
replaced with gcc3x-interp.c, something else causes interp.c to be
included again, but I'm yet to track that down.

I've banged my head on this for a couple of hours. Now looking for some hints...
btw, is trying this with the StackInterpreter first the best approach?

cheers -ben


More information about the Vm-dev mailing list