Hi!
I'm trying to build a new vm from the cvs for debian linux. The problem is that the external plugins are missing the ".so" ending. Any idea how to solve this?
Martin
On Wed, Sep 29, 2004 at 09:38:05PM +0200, Martin Kuball wrote:
Hi!
I'm trying to build a new vm from the cvs for debian linux. The problem is that the external plugins are missing the ".so" ending. Any idea how to solve this?
The build process does a bunch of totally incomprehensible stuff with libtool. If you do "make install" it will probably take care of this for you. If you don't want to install your newly compiled VM, but want to figure out how to make the "*.so" files, try "make -n install" to see what the right commands are. Something like this will let you see what's going on:
$ man -n install 2>&1 | less
You can probably hack your way through it from there.
Dave
Hi!
autoconf is really nasty stuff. But I finally got it to work. The trick is to replace the ltmain.sh from cvs with the version from the local libtool installation. This is compatible with the libtool stuff that get's included into the configure script when autoconf is run. This can be automated by adding a line libtoolize --force --copy into the Makefile.
After that I had another problem. Building the squeak program failed with link errors. The reason seems to be that the following line in Makefile.in: $(LINK) $(squeak) $(SQLIBS) version.o $(LIBS) [plibs] vm/vm.a has the vm.a twice. First in SQLIBS and additionally at the end. Well, the new libtool removes the first occurance from the input to gcc. Having vm/vm.a as last archive does not seem to work. If you remove the vm.a in Makefile.in, libtool will keep the one in SQLIB and everything is fine.
By the way, the ltconfig script in unix/config does not seem to be used. Maybe it should be removed.
Martin
Am Thursday 30 September 2004 01:33 schrieb David T. Lewis:
On Wed, Sep 29, 2004 at 09:38:05PM +0200, Martin Kuball wrote:
Hi!
I'm trying to build a new vm from the cvs for debian linux. The problem is that the external plugins are missing the ".so" ending. Any idea how to solve this?
The build process does a bunch of totally incomprehensible stuff with libtool. If you do "make install" it will probably take care of this for you. If you don't want to install your newly compiled VM, but want to figure out how to make the "*.so" files, try "make -n install" to see what the right commands are. Something like this will let you see what's going on:
$ man -n install 2>&1 | less
You can probably hack your way through it from there.
Dave
I finally solved my issue with utf8 locale and not beeing able to use multibyte characters. I tweaked some methods in sqUnixX11.c and added a new flag to set the encoding for the key events.
Now I wonder if and how I can put this into the repository. Is there an official way as with the changes to the image?
Martin
Am Friday 01 October 2004 18:21 schrieb Martin Kuball:
Hi!
autoconf is really nasty stuff. But I finally got it to work. The trick is to replace the ltmain.sh from cvs with the version from the local libtool installation. This is compatible with the libtool stuff that get's included into the configure script when autoconf is run. This can be automated by adding a line libtoolize --force --copy into the Makefile.
After that I had another problem. Building the squeak program failed with link errors. The reason seems to be that the following line in Makefile.in: $(LINK) $(squeak) $(SQLIBS) version.o $(LIBS) [plibs] vm/vm.a has the vm.a twice. First in SQLIBS and additionally at the end. Well, the new libtool removes the first occurance from the input to gcc. Having vm/vm.a as last archive does not seem to work. If you remove the vm.a in Makefile.in, libtool will keep the one in SQLIB and everything is fine.
By the way, the ltconfig script in unix/config does not seem to be used. Maybe it should be removed.
Martin
Am Thursday 30 September 2004 01:33 schrieb David T. Lewis:
On Wed, Sep 29, 2004 at 09:38:05PM +0200, Martin Kuball wrote:
Hi!
I'm trying to build a new vm from the cvs for debian linux. The problem is that the external plugins are missing the ".so" ending. Any idea how to solve this?
The build process does a bunch of totally incomprehensible stuff with libtool. If you do "make install" it will probably take care of this for you. If you don't want to install your newly compiled VM, but want to figure out how to make the "*.so" files, try "make -n install" to see what the right commands are. Something like this will let you see what's going on:
$ man -n install 2>&1 | less
You can probably hack your way through it from there.
Dave
Am 05.10.2004 um 12:07 schrieb Martin Kuball:
I finally solved my issue with utf8 locale and not beeing able to use multibyte characters. I tweaked some methods in sqUnixX11.c and added a new flag to set the encoding for the key events.
Now I wonder if and how I can put this into the repository. Is there an official way as with the changes to the image?
Martin
You can send it to this list, preferrably with a [FIX][VM][UNIX] tag. This might already be sufficient, but adding a CC: to Ian (official VM maintainer) and Ned (has been maintaining a branch on the CVS repository) wouldn't hurt.
- Bert -
"David T. Lewis" lewis@mail.msen.com wrote:
The build process does a bunch of totally incomprehensible stuff with libtool.
I've noticed that you tend to end up with real .so's in some subdirectory like ".lib" or ".libs".. So you might poke around there.
And of course, it is always an option to read the docs for libtool. :) It seems that Ian is the only one to have made it through so far.
-Lex
squeak-dev@lists.squeakfoundation.org