On Sat 11 Jun 2016 at 21:32:09 (+), Mike wrote:
> Update: I have tried to build the latest tar on my system, but I got the
> following errors - interestingly all to do with symlinks:
>
> 70: extrac07.at:27 extracting symlinks to a read-only dir
> extract extract07 read-only symlink
On Sat 11 Jun 2016 at 12:47:40 (+), Mike wrote:
> > > > When you run LP, it will ask gs to convert the file. However, which
> > > > version of gs runs, LP's or the system's? Will it be happy running
> > > > with LD_LIBRARY_PATH="/home1/myusername/lilypond/usr/lib"?
> > >
> > > No, same error I
Hi Mike,
I am following this thread with ever increasing dismay. In order to help, I
made a virtul machine here running Centos 6.7 and installed lilypond
2.18.2. Everything works fine. No issues at all.
Having worked as a professional IT software developer, sysadmin, and
enterprise architect for
> I suspect that you are not using GNU tar while lilypond's tarball gets
> created with GNU tar.
Thanks Werner. Actually I am using GNU tar (1.23) and I was trying to
upgrade to the latest GNU tar (1.29).
Cheers
___
lilypond-user mailing list
lilypo
> Update: I have tried to build the latest tar on my system, but I got the
> following errors - interestingly all to do with symlinks:
>
> 70: extrac07.at:27 extracting symlinks to a read-only dir
> extract extract07 read-only symlink
> 76: extrac13.at:26 extract over symlinks
>
Update: I have tried to build the latest tar on my system, but I got the
following errors - interestingly all to do with symlinks:
70: extrac07.at:27 extracting symlinks to a read-only dir
extract extract07 read-only symlink
76: extrac13.at:26 extract over symlinks
extract
> > > When you run LP, it will ask gs to convert the file. However, which
> > > version of gs runs, LP's or the system's? Will it be happy running
> > > with LD_LIBRARY_PATH="/home1/myusername/lilypond/usr/lib"?
> >
> > No, same error I'm afraid.
>
> "No" isn't an answer to "which version of gs r
On Thu 09 Jun 2016 at 07:34:46 (+), Mike wrote:
> > When you run LP, it will ask gs to convert the file. However, which
> > version of gs runs, LP's or the system's? Will it be happy running
> > with LD_LIBRARY_PATH="/home1/myusername/lilypond/usr/lib"?
>
> No, same error I'm afraid.
"No" isn
> When you run LP, it will ask gs to convert the file. However, which
> version of gs runs, LP's or the system's? Will it be happy running
> with LD_LIBRARY_PATH="/home1/myusername/lilypond/usr/lib"?
No, same error I'm afraid.
> Do I know if LP's symlinks are set up correctly? Not really.
>
> Do
On Sun 05 Jun 2016 at 20:59:17 (+), Mike wrote:
> > This sort of error is usually a good sign that you're trying to run a
> > locally installed LP with the Linux Distribution versions of, eg,
> > GhostScript or Python; not a good idea.
> >
> > Your full output of the installation process (in t
> IIRC it's a compatibility issue. I think the LilyPond wrapper script
(usually ~/bin/lilypond) has to set
> the right path to the local Lilypond gs.
> Basically, if LilyPond invokes the system gs it's often the wrong version.
The wrapper looks good to me:
#!/bin/sh
me=`basename $0`
export LD_L
Am 5. Juni 2016 22:59:17 MESZ, schrieb Mike :
>> This sort of error is usually a good sign that you're trying to run a
>> locally installed LP with the Linux Distribution versions of, eg,
>> GhostScript or Python; not a good idea.
>>
>> Your full output of the installation process (in the other
> This sort of error is usually a good sign that you're trying to run a
> locally installed LP with the Linux Distribution versions of, eg,
> GhostScript or Python; not a good idea.
>
> Your full output of the installation process (in the other subthread)
> is useful, difficult to understand, and
> Interesting that you had to descend a level to see those links.
>
> My suggestion is that you reinstall with the script just as I showed,
> using a unique, non-existing prefix. The obvious prefix is
> lilypond-2.18.2-1 which includes the version number. I'm *guessing*
> that you've tried to inst
why /home1/myusername?
Normally linux uses /home/myusername
without a one.
Am 05.06.2016 16:43, schrieb David Wright:
Just a quick note before I go off to do real work...
On Sun 05 Jun 2016 at 07:49:41 (+), Mike wrote:
> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix l
Just a quick note before I go off to do real work...
On Sun 05 Jun 2016 at 07:49:41 (+), Mike wrote:
> > > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix lilypond
> >
> > I can't understand this. It looks like root's prompt, not a user's.
>
> It's just my user's prom
On Sun 05 Jun 2016 at 09:54:35 (+), Mike wrote:
> > I'll try a hello world now.
>
> Uhm... Hello world is having trouble with ps->pdf, so far as I can see.
> Again, executing that command manually worked fine, and the resulting PDF
> looks good.
> Should I start a new thread?
>
> Thanks
>
>
> I'll try a hello world now.
Uhm... Hello world is having trouble with ps->pdf, so far as I can see.
Again, executing that command manually worked fine, and the resulting PDF
looks good.
Should I start a new thread?
Thanks
[~/tmp/lily]# lilypond test.ly
GNU LilyPond 2.18.2
Processing `test.ly'
OK, linking manually seemed to work! Weird huh? Seems like I can create
symlinks, but not from within the install script.
Is there a conclusive test to thoroughly verify my install?
I'll try a hello world now.
Thanks again.
[~]# lilypond -v
GNU LilyPond 2.18.2
Copyright (c) 1996--2012 by
Han-We
> For example, we have:
>
> libtiff.so -> libtiff.so.5.2.0 (in the same directory).
>
> To this extent, lilypond is self contained.
Nice one, thanks. OK I'm trying to sort out these links manually, so far so
good!
[~/lilypond/usr/lib]# ln -s libgs.so.8.70 libgs.so
[~/lilypond/usr/lib]# ls -l li
Mike writes:
> I see. Well this is the prompt I found, I didn't override it.
>
> [~]# id
> uid=1292(myusername) gid=1288(myusername) groups=1288(myusername)
The ids are standard fare. So they just set up the prompt against
convention for you. Which is a bad idea exactly because of triggering
s
I see. Well this is the prompt I found, I didn't override it.
[~]# id
uid=1292(myusername) gid=1288(myusername) groups=1288(myusername)
[~]# uname -a
Linux host137.hostmonster.com 3.12.52-20160119.106.ELK6.x86_64 #1 SMP Tue
Jan 19 16:53:32 CST 2016 x86_64 x86_64 x86_64 GNU/Linux
[~]#
Thanks all f
Mike writes:
>> >> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix
> lilypond
>> >>
>> >> I can't understand this. It looks like root's prompt, not a user's.
>> >
>> > It's just my user's prompt. It shows that I'm in my home dir.
>>
>> Are you sure? The `#' sign usua
Hi Mike,
id
will tell you who you are presently.
The $ and # prompt conventions are just that, but they are universally
accepted conventions. It would be highly unusual for a UNIX system to be
set up for a normal user prompt to be #. That in itself is indicative of
the possibility that your Host
2016-06-05 10:54 GMT+02:00 Mike :
>> >> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix
> lilypond
>> >>
>> >> I can't understand this. It looks like root's prompt, not a user's.
>> >
>> > It's just my user's prompt. It shows that I'm in my home dir.
>>
>> Are you sure?
Hi Mike,
The lilypond installation uses symlinks in its /usr/lib area to link to
versions of shared libraries in the same directory, not in /usr on the
system.
For example, we have:
libtiff.so -> libtiff.so.5.2.0 (in the same directory).
To this extent, lilypond is self contained.
Are you able
> >> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix
lilypond
> >>
> >> I can't understand this. It looks like root's prompt, not a user's.
> >
> > It's just my user's prompt. It shows that I'm in my home dir.
>
> Are you sure? The `#' sign usually indicates a super-us
Hi Mike,
It would be helpful if we could know the type of linux system you are on,
which distribution and version I could not see that in this thread.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lil
>> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix lilypond
>>
>> I can't understand this. It looks like root's prompt, not a user's.
>
> It's just my user's prompt. It shows that I'm in my home dir.
Are you sure? The `#' sign usually indicates a super-user shell,
whil
> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix lilypond
>
> I can't understand this. It looks like root's prompt, not a user's.
It's just my user's prompt. It shows that I'm in my home dir.
> Please post all the output. It ought to be about 40 lines at most.
> If the
On Sat 04 Jun 2016 at 20:30:08 (+), Mike wrote:
> > First cd to your home directory. Then issue the command:
> >
> > bash path/to/lilypond-2.19.42-1.linux-x86.sh --prefix lilypond-2.19.42.1
>
> Thank you so much for trying to help, but unfortunately I'm getting the same
> errors, after execut
> First cd to your home directory. Then issue the command:
>
> bash path/to/lilypond-2.19.42-1.linux-x86.sh --prefix lilypond-2.19.42.1
Thank you so much for trying to help, but unfortunately I'm getting the same
errors, after executing this in my home dir:
[~]# bash lilypond_install/lilypond-2.
On Sat 04 Jun 2016 at 18:38:33 (+), Mike wrote:
>
> tar: ./usr/lib/libltdl.so: Cannot create symlink to `libltdl.so.7.2.0':
> Permission denied
>
> If it weren't for that "./", I would have interpreted the above as trying to
> create a symlink in /usr/lib (where I cannot do it) linking into
>
> Is this a Samba mount or NFS or something? Maybe you just cannot create
> symbolic links?
Thanks for helping.
It is not a Samba mount or NFS, to my knowledge. I am definitely not using
it from Windows or anything, I'm just logging in via puTTY.
I am able to create symbolic links, but I think th
Mike writes:
>> I would try running the install script *without* the --prefix option. It
>> should then install just fine in your home directory where you should
>> have write permissions.
>
> Thanks! Unfortunately it didn't work.
> After uninstalling, I have changed to my home dir and issued
>
>
> I would try running the install script *without* the --prefix option. It
> should then install just fine in your home directory where you should
> have write permissions.
Thanks! Unfortunately it didn't work.
After uninstalling, I have changed to my home dir and issued
$lilypond_install/lilypon
Am 04.06.2016 um 19:28 schrieb Mike:
> Hi there, sorry I'm not too versed in Linux. I'm having trouble installing
> Lilypond on a Hostmonster account. The host is shared, and I am not root, so
> I don't have complete freedom.
> I downloaded lilypond-2.18.2-1.linux-64.sh in
> /home1/myaccountname/li
Hi there, sorry I'm not too versed in Linux. I'm having trouble installing
Lilypond on a Hostmonster account. The host is shared, and I am not root, so
I don't have complete freedom.
I downloaded lilypond-2.18.2-1.linux-64.sh in
/home1/myaccountname/lilypond_install, made it executable and then iss
38 matches
Mail list logo
