lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: install on shared host without root access?


From: Vijith Assar
Subject: Re: install on shared host without root access?
Date: Mon, 5 Jul 2010 19:25:01 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Hmm, I feel like you missed some key points in my last message.

> Why do you insist to start at root ("/")?

Just as a troubleshooting measure, which, as I stated, worked as a way to 
locate the launch script from the MediaWiki extension. The solution was a
relative URL which of course did not start at root.

> I guess you need the absolute path to your lilypond installation - and  
> that won't be at root!

As I said, I tried it with numerous URLs, some relative and some absolute,
some which start at root and some which do not.

> Further, you can't expect to run anything own in a "super cheap"  
> shared hosting environment, and this is not the place to discuss web  
> hosting details.

Ha, well, this line of reasoning seems inherently antithetical in a discussion
of free software, and also roughly comparable to the line I got from the host,
ie "You need to upgrade your plan in order to do this." According to Mike at
least, that is not true.

But none of this addresses my core issue (which is not a hosting question).

To restate:

1) The MediaWiki extension finds the script successfully (thanks to your
previous help).

2) The script consists of the default four lines:

#!/bin/sh
me=`basename $0`
export LD_LIBRARY_PATH="/lilypond/usr/lib"
exec "/lilypond/usr/bin/$me" "$@"

3) Running that script produces these error messages:

./../../lilypond/lilypond: line 4:
/[path to home directory]/wiki/images/tmp/usr/bin/lilypond:
No such file or directory

../../../lilypond/lilypond: line 4:
exec: /[path to home directory]/wiki/images/tmp/usr/bin/lilypond:
cannot execute:
No such file or directory

4) No edits I make to the launch script, including changing lines 3 and 4
to other relative or absolute addresses, seem to have any effect on the error
messages.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]