Re: [Sablevm-developer] Config File Parsing (Done)

[Etienne M. G. <eg...@j-...>]

Brent Fulgham wrote:
> Thanks for your comments.  I have checked in an update that (a) moves
> much of the file reading code into our own "getLine" function that
> should be somewhat functionally equivalent to the GNU version, and
> (b) removes the debugging output for the optional config files.

Thanks.

> By the way, should the configuration default to "/usr/etc"?  That
> doesn't seem standard, at least for Linux systems.

No.  If I understand well, it is assumed that when somebody downloads a
source package, he will want to install it in the /usr/local directory,
because the package is obviously not part of the "distribution" (or it
would have already been available as a binary package in /usr).

When you build a local package, you do not want it to interfere with
"official" packages.  For this reason,

./configure
make install

puts everything under /usr/local.

Now, when you build a binary package, for inclusion in an official
distribution, you simply use some configure options to put files in the
right directory, according to the policy of your distribution.

./configure --prefix=/ --sysconfdir=/etc ...

I haven't built any binary package for a distribution, yet (except for a
Debian kernel package), so I do not know how people usually go about it,
but I am pretty sure that they do something similar.  Maybe you know
more than me about that;-)

> 
> I tried out your test cases, and I'm happy to report that the code
> does read and store your 3095-byte test string.  Unfortunately, it
> seems to cause a segfault later on when the JVM attempts to stat that
> non-existent directory...

Have you tested giving sablevm an appropriate boot-class-path and
boot-library-path?

It works for me, without segfaulting...

> Well, I don't seem to be able to manipulate the bugs in the database,
> so I can't "close" anything.  However, I'm not sure if you want
> to handle all such activities yourself.

OK.  So, you'll get admin privilege.  I do really want sablevm
developers to be able to "close" (and manage) the bugs.

I'll let you close the bugs, testing your new privileges:-)

Etienne
-- 
----------------------------------------------------------------------
Etienne M. Gagnon, M.Sc.                     e-mail: eg...@j-...
Author of SableCC:                 http://www.sable.mcgill.ca/sablecc/
and SableVM:                                   http://www.sablevm.org/
----------------------------------------------------------------------