building a unix vm with src32

David T. Lewis lewis at
Wed May 3 00:01:09 UTC 2006


I think I've seen these symptoms in the past.

Try symlinking your ./src32 to ./src, then re-run platforms/unix/config/configure
and make.

Perhaps there is some difference of opinion between VMMaker conventions
and something in the unix configuration scripts. Sorry, I never took
the time to find the root cause, but linking the "src32" name that VMM
expects to the "src" name that configure expects seems to make it go away.


p.s. Ian recently mentioned the possibility of enhancing the support code
such that only one ./src would be required for building 32 bit and 64 bit
VMs, at which point this sort of problem should disappear for good.

On Tue, May 02, 2006 at 10:43:05PM +0200, Martin Kuball wrote:
> Hi!
> I'm trying to build a unix vm on 64 bit AMD (system is debian sid) for 
> use with 32 bit images. I'm using the current svn trunk and build 
> with the src32 directory. Things go well until the link step:
> gcc -g -O2 -DLSB_FIRST=1 -o squeak disabledPlugins.o 
> version.o -Wl,--export-dynamic  vm/vm.a B2DPlugin/B2DPlugin.a 
> BitBltPlugin/BitBltPlugin.a FilePlugin/FilePlugin.a 
> SocketPlugin/SocketPlugin.a -lutil -ldl -lm -lnsl 
> vm/vm.a -Wl,--rpath -Wl,/usr/lib
> vm/vm.a(sqVirtualMachine.o): In function 
> `sqGetInterpreterProxy':/home/kuball/SMT/vm-svn/trunk/platforms/Cross/vm/sqVirtualMachine.c:202: 
> undefined reference to `obsoleteDontUseThisFetchWordofObject'
> :/home/kuball/SMT/vm-svn/trunk/platforms/Cross/vm/sqVirtualMachine.c:333: 
> undefined reference to `fetchLong32ofObject'
> :/home/kuball/SMT/vm-svn/trunk/platforms/Cross/vm/sqVirtualMachine.c:334: 
> undefined reference to `getThisSessionID'
> :/home/kuball/SMT/vm-svn/trunk/platforms/Cross/vm/sqVirtualMachine.c:335: 
> undefined reference to `ioFilenamefromStringofLengthresolveAliases'
> :/home/kuball/SMT/vm-svn/trunk/platforms/Cross/vm/sqVirtualMachine.c:336: 
> undefined reference to `vmEndianness'
> As you can see some methods are missing from interp.c. Can anybody 
> help me fixing this problem?
> Martin

More information about the Vm-dev mailing list