Rob Browning writes:
> Perhaps I could move it to the %guile-build-info libdir, i.e. here
> /usr/lib/x86_64-linux-gnu/guile/2.0/guile-procedures.txt and make sure
> documentation-files includes that in its search list.
If there are no substantial objections, I'll consider that for the next
uploa
Andy Wingo wrote:
>#!/bin/sh
>export FOO=bar
>exec guile $0 "$@"
>!#
That introduces all the complexity of using another language interpreter,
one I've chosen not to write my program in. I don't much fancy working
round a gotcha by importing another series of gotchas.
Fundamentally, it seems lik
On Tue 09 Aug 2016 14:15, Zefram writes:
> I wrote:
>>is my first time compiling a Guile myself. It's failing on a missing
>>library for which Debian supplies no package.
>
> Turns out there was a package. It was complaining about a lack of
> "bdw-gc", and Debian doesn't have anything of that n
On Mon 08 Aug 2016 23:02, Zefram writes:
> Andy Wingo wrote:
>>Serious question tho: what sort of back-compatibility can there be with
>>a Guile that only supports latin-1 strings?
>
> I'd expect that almost any program that runs on Guile 1.8 ought to be
> portable, with only minimal modification
I wrote:
>is my first time compiling a Guile myself. It's failing on a missing
>library for which Debian supplies no package.
Turns out there was a package. It was complaining about a lack of
"bdw-gc", and Debian doesn't have anything of that name, but it does
have it under the name "libgc". So
