error building from "master" checkout

2011-04-07 Thread Marco Maggi 
Withcheckoutfrom   master(commit
4db853d747ac115f799c93e2de93f5159ad84109) I get this error:

[...]
  SNARF  posix.doc
  SNARF  net_db.doc
  SNARF  socket.doc
  SNARF  regex-posix.doc
  GENguile-procedures.texi
Throw without catch before boot:
Throw to key stack-overflow with args (#f "Stack overflow" #f #f)Aborting.
/bin/sh: line 1: 14231 Broken pipe cat alist.doc arbiters.doc 
array-handle.doc array-map.doc arrays.doc async.doc backtrace.doc boolean.doc 
bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc 
debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc error.doc 
eval.doc evalext.doc expand.doc extensions.doc feature.doc fluids.doc 
foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc generalized-arrays.doc 
generalized-vectors.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc 
hooks.doc i18n.doc init.doc ioext.doc keywords.doc list.doc load.doc macros.doc 
mallocs.doc memoize.doc modules.doc numbers.doc objprop.doc options.doc 
pairs.doc ports.doc print.doc procprop.doc procs.doc promises.doc 
r6rs-ports.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc 
script.doc simpos.doc smob.doc sort.doc srcprop.doc srfi-1.doc srfi-4.doc 
srfi-13.doc srfi-14.doc srfi-60.doc stackchk.doc stacks.doc stime.doc 
strings.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc 
throw.doc trees.doc uniform.doc values.doc variable.doc vectors.doc version.doc 
vports.doc weaks.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc 
regex-posix.doc
 14232 Aborted | GUILE_AUTO_COMPILE=0 
../meta/uninstalled-env guile-tools snarf-check-and-output-texi > 
guile-procedures.texi
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory 
`/home/marco/src/devel/scheme/checkouts/guile/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/marco/src/devel/scheme/checkouts/guile/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/marco/src/devel/scheme/checkouts/guile'

Is it fine  for me to follow the "master"  branch to get the
"latest thought to be usable"?
-- 
Marco Maggi

Re: error building from "master" checkout

2011-04-07 Thread Andreas Rottmann 
Marco Maggi  writes:

> Withcheckoutfrom   master(commit
> 4db853d747ac115f799c93e2de93f5159ad84109) I get this error:
>
> [...]
>   SNARF  posix.doc
>   SNARF  net_db.doc
>   SNARF  socket.doc
>   SNARF  regex-posix.doc
>   GENguile-procedures.texi
> Throw without catch before boot:
> Throw to key stack-overflow with args (#f "Stack overflow" #f #f)Aborting.
> /bin/sh: line 1: 14231 Broken pipe cat alist.doc arbiters.doc 
> array-handle.doc array-map.doc arrays.doc async.doc backtrace.doc boolean.doc 
> bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc 
> debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc 
> error.doc eval.doc evalext.doc expand.doc extensions.doc feature.doc 
> fluids.doc foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc 
> generalized-arrays.doc generalized-vectors.doc goops.doc gsubr.doc 
> guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc 
> keywords.doc list.doc load.doc macros.doc mallocs.doc memoize.doc modules.doc 
> numbers.doc objprop.doc options.doc pairs.doc ports.doc print.doc 
> procprop.doc procs.doc promises.doc r6rs-ports.doc random.doc rdelim.doc 
> read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc 
> srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc srfi-60.doc 
> stackchk.doc stacks.doc stime.doc strings.doc strorder.doc strports.doc 
> struct.doc symbols.doc threads.doc throw.doc trees.doc uniform.doc values.doc 
> variable.doc vectors.doc version.doc vports.doc weaks.doc dynl.doc 
> filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc
>  14232 Aborted | GUILE_AUTO_COMPILE=0 
> ../meta/uninstalled-env guile-tools snarf-check-and-output-texi > 
> guile-procedures.texi
> make[3]: *** [guile-procedures.texi] Error 1
> make[3]: Leaving directory 
> `/home/marco/src/devel/scheme/checkouts/guile/libguile'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory 
> `/home/marco/src/devel/scheme/checkouts/guile/libguile'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/marco/src/devel/scheme/checkouts/guile'
>
Was this a clean build?  If you get strange build failures, it's often a
good idea to re-run the build after a "git clean -dxf" (note that this
will remove all files you may have put in you checkout, even if they are
not controlled by git).  Should the problem persist even when building
from a clean tree, please tell us so we can investigate.

> Is it fine for me to follow the "master" branch to get the "latest
> thought to be usable"?
>
ATM, most work is happening on stable-2.0, and master is only updated
sporadically.  Unless you want do work on Guile itself that's supposed
to go into 2.2 (only) eventually, I'd recommend using the stable-2.0
branch.  See also
.

Regards, Rotty
-- 
Andreas Rottmann --

Re: [Help-smalltalk] GNU Smalltalk 4.1 released!

2011-04-07 Thread Frank Church 
On 1 April 2011 10:24, Paolo Bonzini  wrote:

> GNU Smalltalk 4.1 has been released at
>
> * ftp://ftp.gnu.org/gnu/smalltalk/smalltalk-4.1.tar.gz
>  SHA1 checksum: 617072696c277320666f6f6c2773206865726521
> * ftp://ftp.gnu.org/gnu/smalltalk/smalltalk-4.1.tar.xz
>  SHA1 checksum: cd08a6638b5efb87198b47f7c0796e3993eb5157
>
> This release features a complete rewrite of the VM to run on top of GNU
> Guile, the official extension language for the GNU operating system.
>
> Of course, some features had to be sacrificed in order to make this radical
> change.  For example, sockets have been replaced by a new network
> abstraction, "socks", and the GTK bindings have been replaced by a port of
> the famous GUI toolkit "shoes".
>
> Those who would like to know more about the technology can of course ask
> here on the mailing list or on the #gnu-smalltalk channel on
> irc.freenode.net.
>
> Thanks to the Guile team for providing the foundation for the future of GNU
> Smalltalk!
>
> Paolo
>
> ___
> help-smalltalk mailing list
> help-smallt...@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-smalltalk
>


you almost got me here
-- 
Frank Church

===
http://devblog.brahmancreations.com

Re: error building from "master" checkout

2011-04-07 Thread Marco Maggi 
"Andreas Rottmann" wrote:
> Was this a clean build?

IIRC  it  was  right  after  a  "git clone"  and  a  run  of
autogen.sh.

>> Is it  fine for me to  follow the "master"  branch to get
>> the "latest thought to be usable"?
>
> ATM, most  work is happening on stable-2.0,  and master is
> only updated sporadically.

I am  interested in  the version which  will have  the first
usable R6RS; I will follow stable-2.0 for now, thanks.
-- 
Marco Maggi

Re: [Swig-user] swig guile2

2011-04-07 Thread Tristan Colgate 
I've reworked it so that it is a replacement for the existing guile
module and have made some headway on the test suite (much of it now
"passes", in that the test cases don't give errors/warnings, but I'd
like to rework it to actually run a few more tests rather than just
compile).

  The big gap at the moment is documentation, and the linkage options
(which I don't fully understand yet).

  I will keep you posted on my progress.

On 25 March 2011 20:14, William S Fulton  wrote:
> On 22/03/11 08:16, Tristan Colgate wrote:
>>
>> On 21 March 2011 20:32, William S Fulton  wrote:
>>
>>> Are you proposing a 2nd SWIG Guile module in addition to the current
>>> module?
>>
>>   The code as it stands is exactly that, a new module. I have worked
>> under the assumption that breaking the existing guile support was
>> taboo.
>>
>>> I am no guile user, so can't help on the Guile side. The guile SWIG
>>> module
>>> is suffering neglect and doesn't seem to work with modern versions of
>>> Guile
>>> - the test-suite fails for me. Only very rarely are there Guile queries
>>> on
>>> the SWIG mailing list, so suspect it isn't used much. Would it make sense
>>> to
>>> drop the older Guile interface altogether and just use Guile 2?
>>
>>   The existing guile module support the gh_ interface and the older
>> version of the SCM interface. It also doesn't work with guiles current
>> GC. It's entirely useless for the current version of guile. I had
>> assumed that since SWIG still ships it, enough people care about
>> legacy guile support to not want it broken.
>>
>>   I've only just started looking into getting the test-suite working
>> with my guile2 work, but I do intend on getting it to the point where
>> it all passes.
>>
> If it all passes, it will then be good enough to commit to trunk and to be
> included in future SWIG releases. Please discuss on swig-devel if you get to
> this stage.
>
>>   For me personally, the old guile module is no longer useful.
>> However, guile 2.0 is not widely deployed in distributions yet and
>> that may take some time.
>>
>>> BTW, there
>>> is the swig -scm option for guile 1.6+. So there seems to be GH and SCM
>>> and
>>> now guile 2 API... does that sound right that there are so many C
>>> interfaces
>>> or is your Guile 2 interface just SCM?
>>
>>   The -scm support works by mapping the old SCM interface to the GH
>> interface.. Almost all the scm_ calls used by the existing guile
>> module are deprecated. I tried implementing and -scm2 option within
>> the existing module but it was more awkward than I could bare.
>>
>>   I'm not sure that there is going to be enormous support for this
>> within the guile community either really. Guile 2 ships with a new FFI
>> and using that is, obviosuly, of more interest to them. I've struggled
>> wrapping legacy APIs with it though and SWIG really is rather good.
>>
> Well if you get the new version up to scratch perhaps SWIG could just
> support Guile 2 and later unless someone really objects. The older Guile
> would then require earlier versions of SWIG.
>
> William
>



-- 
Tristan Colgate-McFarlane

  "You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"