Vm-dev February 2009

vm-dev@lists.squeakfoundation.org

23 participants
29 discussions

Building a 64-bit VM for FreeBSD
by Frank Shearar 14 Feb '09

14 Feb '09

Hi everyone, I'm trying to wrap my head around how to use VMMaker to generate source for a VM. I took a stock 3.9 (Squeak3.9-final-7067, to be precise) image on my Windows machine, installed VMMaker from SqueakMaps, and fired up the VMMakerTool. I checked out http://squeakvm.org/svn/squeak/trunk/platforms into a src directory, and pointed VMMakerTool at it. I told it "build all plugins internally" (because I want to Make It Work first). That generated some files. (In the unix subdirectory: interp.c, interp.h, sqNamedPrims.h. In unix/vm/intplugins/Foo/, a Foo.c, where Foo is each of the plugin names.) Then: cd ~/temp mkdir src cd src svn co http://squeakvm.org/svn/squeak/trunk/platforms I copied the various produced files on my Windows manually over to the new repository. Then: mkdir bld cd bld ../platforms/unix/config/configure make and everything started compiling. Everything went fine, until we started compiling sqUnixSecurity.c, when I got this: gcc -g -O2 -DLSB_FIRST=1 -DHAVE_CONFIG_H -DSQUEAK_BUILTIN_PLUGIN -I/usr/h ome/frank/temp/src/bld -I/usr/home/frank/temp/src/platforms/unix/vm -I/usr/h ome/frank/temp/src/platforms/Cross/vm -I/usr/home/frank/temp/src/platforms/u nix/src/vm -I/usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin -c -o sqUnixSecurity.o /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c In file included from /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:16: /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:4: error: conflicting types for 'ioDisableImageWrite' /usr/home/frank/temp/src/platforms/Cross/vm/sq.h:345: error: previous declaration of 'ioDisableImageWrite' was here /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:5: error: conflicting types for 'ioCanWriteImage' /usr/home/frank/temp/src/platforms/Cross/vm/sq.h:344: error: previous declaration of 'ioCanWriteImage' was here /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:28: error: conflicting types for 'ioCanRenameImage' /usr/home/frank/temp/src/platforms/Cross/vm/sq.h:343: error: previous declaration of 'ioCanRenameImage' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:67: error: conflicting types for 'ioCanCreatePathOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:20: error: previous declaration of 'ioCanCreatePathOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:74: error: conflicting types for 'ioCanListPathOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:24: error: previous declaration of 'ioCanListPathOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:81: error: conflicting types for 'ioCanDeletePathOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:22: error: previous declaration of 'ioCanDeletePathOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:91: error: conflicting types for 'ioCanOpenFileOfSizeWritable' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:26: error: previous declaration of 'ioCanOpenFileOfSizeWritable' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:98: error: conflicting types for 'ioCanOpenAsyncFileOfSizeWritable' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:25: error: previous declaration of 'ioCanOpenAsyncFileOfSizeWritable' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:104: error: conflicting types for 'ioCanDeleteFileOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:21: error: previous declaration of 'ioCanDeleteFileOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:110: error: conflicting types for 'ioCanRenameFileOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:27: error: previous declaration of 'ioCanRenameFileOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:117: error: conflicting types for 'ioCanGetFileTypeOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:23: error: previous declaration of 'ioCanGetFileTypeOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:123: error: conflicting types for 'ioCanSetFileTypeOfSize' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:29: error: previous declaration of 'ioCanSetFileTypeOfSize' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:132: error: conflicting types for 'ioDisableFileAccess' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:30: error: previous declaration of 'ioDisableFileAccess' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:139: error: conflicting types for 'ioHasFileAccess' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:31: error: previous declaration of 'ioHasFileAccess' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:174: error: conflicting types for 'ioCanCreateSocketOfType' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:16: error: previous declaration of 'ioCanCreateSocketOfType' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:180: error: conflicting types for 'ioCanConnectToPort' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:17: error: previous declaration of 'ioCanConnectToPort' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:186: error: conflicting types for 'ioCanListenOnPort' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:13: error: previous declaration of 'ioCanListenOnPort' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:192: error: conflicting types for 'ioDisableSocketAccess' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:18: error: previous declaration of 'ioDisableSocketAccess' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:199: error: conflicting types for 'ioHasSocketAccess' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:19: error: previous declaration of 'ioHasSocketAccess' was here /usr/home/frank/temp/src/platforms/unix/plugins/SecurityPlugin/sqUnixSecurit y.c:224: error: conflicting types for 'ioInitSecurity' /usr/home/frank/temp/src/platforms/Cross/plugins/SecurityPlugin/SecurityPlug in.h:12: error: previous declaration of 'ioInitSecurity' was here *** Error code 1 Stop in /usr/home/frank/temp/src/bld/SecurityPlugin. *** Error code 1 Stop in /usr/home/frank/temp/src/bld. I'm running gcc (GCC) 4.2.1 20070719 [FreeBSD]. How have I messed up, and do I need to give any further info? frank

3 13

Interrupted system call?
by Andreas Raab 12 Feb '09

12 Feb '09

Folks - I've seen references to that particular error in the Unix VM in other discussions. We have this problem right now in a slightly different context (an external library call reports that error) and I am wondering if someone can explain to me what causes this error and whether there is a way to "fix" the Unix VM not to cause it. Thanks for any insights! Cheers, - Andreas

4 7

patch: improved signal handling (for discussion)
by Andrew Gaylard 11 Feb '09

11 Feb '09

Following on from my last message, here's the first pass at a patch to replace signal() calls with sigaction(). As you can tell, it's against the 3.10-4 tree. I'd appreciate any feedback. Some notes: - in UnixOSProcessPlugin.c, we replace signal() with sigaction(). This is the pattern we use. - in aio.c, I introduced a tiny function, aioShimHandler, to call forceInterruptCheck. This was to work around a compiler warning (the function prototypes differed). It also helped with printf debugging. - in aio.c, it's not clear to my why SIGPIPE is ignored. Can anyone explain it? I've updated this code. - in aio.c, aioFini never used to clear the SIGIO handler. Why is this? I've done it now, with no obvious ill effects, but that doesn't count for a lot when dealing with signals. - in sqUnixMain.c, I've added a default handler for HUP, USR1, USR2, and TERM. The default action for these signals is to terminate the VM. This way, they just complain a little to stderr, unless a handler has been set in smalltalk. Now, if a signal arrives before the smalltalk is ready, they just ignore it. Actually, it would be better to block / queue signals, which would then be delivered when the handler is installed. Hmmm. - Andrew

2 1

patch: improved signal handling (for discussion)
by Andrew Gaylard 11 Feb '09

11 Feb '09

(And here's the patch attached. Sorry.)

1 0

Solaris vs. iconv: workaround
by Andrew Gaylard 06 Feb '09

06 Feb '09

I've been experiencing Squeak on Solaris printing iconv_open: Invalid argument a zillion times over. Looking at the mailing list archives, this has been a problem on and off for a long time. I first tried compiling with --disable-iconv, which fixed the error, but then some of the plugins complained that they couldn't convert strings. So I decided against that. I've managed to work around it by as follows: su - cd /usr/lib/iconv cp mac%alt.so MACINTOSH%UTF-8.so cp alt%mac.so UTF-8%MACINTOSH.so This seems to shut up all the messages. But I'm nervous, since I suspect that "alt" probably isn't the whole of UTF8... Andrew

1 0

newDelta >0 failed in sqUnixMemory
by Damien Cassou 04 Feb '09

04 Feb '09

Hi, with a recent stock pharo image and a new VM compiled from svn on Linux, I always get squeak: /tmp/squeak-svn/platforms/unix/vm/sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0' failed. Aborted This does not happen on Squeak 3.9 nor 3.10. This did not happen yesterday when I was on Ubuntu Hardy. Now, I'm on Intrepid, GCC 4.3.2 and it crashes after 3 seconds of work on any Pharo image. You may want to know that to compile the vm, I was obliged to change sqUnixFBDevMousePS2.c to make use of the 'write(2)' return value because my compiler didn't want to compile if write(2) return value was unused. -- Damien Cassou http://damiencassou.seasidehosting.st

4 15

[Fix] Avoid recent gcc error messages about unused write(2) return value
by Damien Cassou 03 Feb '09

03 Feb '09

See attachment. [Fix] Avoid recent gcc error messages about unused write(2) return value -- Damien Cassou http://damiencassou.seasidehosting.st

4 6

Re: [Pharo-project] Plugin organization
by David T. Lewis 02 Feb '09

02 Feb '09

On Wed, Jan 21, 2009 at 02:05:46PM +0100, Michael Rueger wrote: m Hi all, > > What I would like to propose is that we organize all plugins in Pharo in > to a Plugin category. > So we would then have "Plugin-Curl", "Plugin-Locale" etc. Or > alternatively "Plugin-Network-Curl", "Plugin-System-Locale" etc. > > That would also allow to simply load all plugins into a VMMaker image by > using a package "Plugin". > > What do you guys think? +1 on a common naming convention for this. I would also like to suggest something to distinguish VM plugins from other kinds of "plugins". The reason is that the word "Plugin" is used to describe the web browser plugin, and maybe other things in the future. If we say "VmPlugin" or "VMConstruction-Plugin-* then the difference is clear. I checked an older Squeak image to remind myself of the original naming convention, which was: VMConstruction-Interpreter VMConstruction-Translation VMConstruction-Plugins VMConstruction-B3DSimulation VMConstruction-TestPlugins VMConstruction-Applescript Some older plugins that are maintained outside of the VMMaker package already use this package naming convention, hence: VMConstruction-Plugins-OSProcessPlugin VMConstruction-Plugins-XDisplayControlPlugin VMConstruction-Plugins-AioPlugin This still looks perfectly good to me, so how about just using "VMConstruction-Plugins-*" rather than "Plugins-*"? Michael Rueger proposed Plugin-* and Tests-*, so guess that this would be: VMConstruction-Plugins VMConstruction-Tests or is it "Tests-VMConstruction-Plugins" ?? I am not sure. (cc to vm-dev list) Dave

3 5

Squeak-VM to PowerPC/Linux
by pascal.vollmer＠nexgo.de 01 Feb '09

01 Feb '09

Hi, I prepare a port of the Squeak-VM to a PowerPC/Linux-embedded system. I investigate ../platforms/unix/config/configure.ac in Squeak-3.10-4.src.tar.gz as given on http://www.squeakvm.org/unix/ . Is there anyone around who already did the same job? And if so, did you ./configure or was there a need to change configure.ac and to run autoconf? Can anyone tell me which version of autoconf is usually used with the above configure.ac? At the moment running ./configure did not work for me (see Note 1) and changing configure.ac with a new run of autoconf goes more like a guess than like a logical process (see Note 2). Kind regards Pascal Note 1. cd buildPPCLx ../platforms/unix/config/configure --prefix=/home/pascalv/smalltalk/squeak/Squeak-VM/Squeak-3.10-4/PPCLx --build=i686-pc-linux-gnu --host=powerpc-603e-linux-gnu yields: using built-in src directory /home/pascalv/smalltalk/squeak/Squeak-VM/Squeak-3.10-4/platforms/unix/src checking sanity of generated src directory... okay checking build system type... i686-pc-linux-gnu checking host system type... powerpc-603e-linux-gnu (..) checking "size of int"... configure: error: cannot run test program while cross compiling See `config.log' for more details. Note 2. pascalv@linux:~/smalltalk/squeak/Squeak-VM/Squeak-3.10-4/platforms/unix/config> autoconf -V autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. autoconf --warnings=cross --output=configure configure-PPCLx.ac followed by config like above yields: the generation of all makefiles but a config.log with several errors in conftest.c and conftest.cc. Pascal Vollmer Email: pascal.vollmer(a)ieee.org Erwischt! Bei Arcor sehen Sie die besten Promi-Bilder riesengroß und in Top-Qualität. Hier finden Sie die schönsten Schnappschüsse auf dem roten Teppich, lernen die Frauen des Womanizers Boris Becker kennen und schauen den Royals ins Wohnzimmer. Viel Spaß auf Ihrer virtuellen Reise durch die Welt der Stars und Sternchen: http://vip.arcor.de.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev February 2009