> On Tue, Jan 14, 2020, 6:34 AM Peter Anglea <mailto:pe...@peteranglea.com>> wrote:
> I think I got it fixed… recording this here for anyone else who stumbles upon
> the same issue as I did.
>
> I downloaded an RPM containing libcrypt.so.1, extracted the file, and put
. So if there’s a more obvious fix, I’d love to hear about it.
> On Jan 11, 2020, at 12:07 PM, Peter Anglea wrote:
>
> I’ve been running LilyPond on AWS Lambda for some time now, but recently have
> been forced to upgrade my runtime from Node 8.x to Node 12.x due to Node 8.x
I’ve been running LilyPond on AWS Lambda for some time now, but recently have
been forced to upgrade my runtime from Node 8.x to Node 12.x due to Node 8.x
becoming deprecated. However, in my testing, LilyPond does not work in either
the Node 10.x or Node 12.x runtimes. I get the following
I’m trying to use the -e (--evaluate) option to define a hash, not just a
single variable. For instance
lilypond -e ‘((define myhash (make-hash-table))(hashq-set! myhash ‘foo
“bar”))’ file.ly
The above doesn’t work. I think, obviously, it’s breaking at the single quote –
‘foo.
I’ve
