On Mon, 2013-12-09 at 15:56 +0100, David Kastrup wrote: > Richard Shann <rich...@rshann.plus.com> writes: > > > I thought I would test out the binary that is on denemo.org and > > downloaded it in a virtual machine running a vanilla Debian stable O/S, > > the result: it will not even start. The executables ~/usr/bin/denemo and > > ~/usr/bin/lilypond are present and have the right permissions but > > attempting to execute them from the bash prompt results in a baffling > > "No such file or directory" message: > > > > ls -l denemo > > -rwxr-xr-x 1 rshanngub rshanngub 1479840 Nov 25 23:00 denemo > > rshanngub@debianGUB:~/denemo/usr/bin$ ./denemo > > bash: ./denemo: No such file or directory > > rshanngub@debianGUB:~/denemo/usr/bin$ > > > > and then the same thing for lilypond: > > > > ls -l lilypond > > -rwxr-xr-x 1 rshanngub rshanngub 4377128 Nov 25 23:00 lilypond > > rshanngub@debianGUB:~/denemo/usr/bin$ ./lilypond > > bash: ./lilypond: No such file or directory > > That's typical if > a) the file is an executable script > b) it has a #! comment in its first characters > c) the named executable in the #! comment does not exist
hmm, well they are Elf binary executables (I checked), and when I create a small test script with a bad #! I get a much more helpful "bad interpreter" error message when I try to execute it. The scripts (as with LilyPond that do start #! /bin/sh) are in ~/bin and they give the bizarre messages: 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< denemo /home/rshann/bin/denemo: 41: /home/rshann/bin/denemo: cannot create : Directory nonexistent /home/rshann/bin/denemo: 45: /home/rshann/bin/denemo: /home/rshann/denemo/usr/bin/gtk-query-immodules-2.0: not found /home/rshann/bin/denemo: 49: exec: /home/rshann/denemo/usr/bin/denemo: not found 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< These seem of a piece with the attempts to get the executables to launch directly - it is as if the command line interpreter is not a normal shell. I see that it is a link to /bin/dash and indeed running the script using bash instead I get a different error message. 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< /bin/bash bin/denemo bin/denemo: line 41: $GDK_PIXBUF_MODULE_FILE: ambiguous redirect bin/denemo: line 49: /home/rshann/denemo/usr/bin/denemo: No such file or directory 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< I've never tried delving into this stuff before, as I assumed it was just my development environment interfering with the normal user experience. > > >> Do you have any users actually having success with the binary package > >> on Ubuntu? If not, telling people that the "ancient" versions > >> delivered with the system itself are not to be used is creating a > >> rather large barrier of entry. > > > > As I say, I am told that it is a Ubuntu system that it gets tested on, > > but if would help if we got more feedback from users. I occasionally > > get visits from people with apple macs and the mac versions have > > worked on their machines and I test windows versions on two or three > > machines with various flavors of their o/ses. A GNU/Linux binary you > > would have thought would be easier than either of those to get working > > ... (As I wrote this I recalled that I have a small partition with > > Ubuntu 12.04 installed, I rebooted and went through the same process > > as with Debian Stable and got the same, bizarre result). I think we > > need to warn people that they may well need to built it :( > > It may also help to put the binary directory into PATH proper, like with > export PATH="$PATH:$HOME/denemo/usr/bin" > (don't use ~/denomo/... since that does not work reliably.) Putting the path to the denemo and lilypond executables still does not make them execute from the command line: 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< /bin/which denemo /home/rshann/denemo/usr/bin/denemo rshann@DebianBox:~$ denemo bash: /home/rshann/denemo/usr/bin/denemo: No such file or directory 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< this was done in my development environment, but now I'm fairly sure that is not relevant. It appears to be the actual Elf executables that cause the bizarre "No such file or directory" message, there is no symbol "main" to stop them on, which would indicate that they are not proper executables at all... some sort of trouble with the linker or libtool I guess. But then why does it ever work (or do people quietly go off and build from sources and not mention the problem?). Richard _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
