Hello Mark,
Mark H Weaver writes:
> Mike Gran writes:
>>> The reason I am still arguing this point is because I have looked
>>> seriously at what I would need to do to (A) fix our i18n problems and
>>> (B) make the code efficient. I very much want to fix these things,
>>> but the pain of tryin
Neil Jerram schreef op za 05-03-2011 om 19:47 [+]:
> In principle, how should Guile 2.0 be cross-compiled?
We're using GUB -- http://lilypond.org/gub and are
sucessfully cross-building guile-2.0. You may want
to look at some patches
https://github.com/janneke/gub/tree/guile-2.0/patches
Good news: with guile stable-2.0 (958173e4), the module-lookup for-each
problem running from compiled cache
http://lists.gnu.org/archive/html/guile-devel/2011-02/msg00213.html
Yay!
Bad news: schikkers-list still does not run, showing a similar problem.
The problem is the same for a fresh and
> From:Ludovic Courtès
> > I know of two categories of bugs. One has to do with case conversions
> > and case-insensitive comparisons, which must be done on entire strings
> > but are currently done for each character. Here are some examples:
> >
> > (string-upcase "Straße") => "STRAß
Hi,
Mike Gran writes:
>> From:Ludovic Courtès
>
>> > I know of two categories of bugs. One has to do with case conversions
>> > and case-insensitive comparisons, which must be done on entire strings
>> > but are currently done for each character. Here are some examples:
>> >
>> > (string-up
I got the error below building today's stable-2.0.
It seems that ensure-writable-dir in compile.scm can
be raced.
Greetings,
Jan.
guile-tools compile -Wunbound-variable -Warity-mismatch -Wformat -o
"oop/goops/composite-slot.go"
"/home/janneke/vc/gub/target/tools/src/guile-2.0.0.1/modul
