On Fri, Apr 15, 2016 at 12:02:16PM +0200, Wolfgang Engelmann wrote: > > > Am 15.04.2016 um 11:22 schrieb Scott Kostyshak: > >On Fri, Apr 15, 2016 at 11:12:41AM +0200, Wolfgang Engelmann wrote: > >>Thanks, Scott. > >Hi Wolfgang, please bottom post (as asked for in our list netiquette > >[1]). > sorry! > >>Next question: I tried ./configure > >>with no success, although I am root. > >You should only need root privilege if you want to install. > > > >>root@wolfgang-Mr-Whisper-Ultra-SSD-II:/mnt/sdb/we/Lyx2-2/lyx-2.2.0rc1# > >>./configure > >>bash: ./configure: Keine Berechtigung > >> > >>What is wrong? > >>Am I in the wrong directory (the one where I unpyked the package)? > >>Wolfgang > >I would suggest the following: > >as a user (not root), download the tar ball to a directory you know you > >have access to. Extract it to another directory you have access to, for > >example ~/Desktop. Note that this is *not* the directory where LyX will > >be installed to. > > > >Then, cd to that directory (again, as user, no root). Now does > >./configure > >work? > > > >Scott > > > >[1] https://www.lyx.org/MailingLists#toc7 > I followed your advice, copied the tar to my Desktop and extracted it, > checked the access: > we@wolfgang-Mr-Whisper-Ultra-SSD-II:/mnt/sdb/we/Desktop$ ls -l > insgesamt 4 > drwxr-xr-x 11 we we 4096 Apr 12 03:31 lyx-2.2.0rc1 > and checked also configure: > ls -l configure > -rwxrwxrwx 1 we we 408602 Apr 12 03:31 configure > > but still have no access: > > we@wolfgang-Mr-Whisper-Ultra-SSD-II:/mnt/sdb/we/Desktop/lyx-2.2.0rc1$ > ./configure > bash: ./configure: Keine Berechtigung > > I am afraid I do something basic wrongly > I do not want to waste your time and will try tonight to solve it by asking > my son. > Thanks for your help and patience
You are not wasting my time. I would be very happy if you could compile because that would be another tester of LyX devel, so don't worry about that. I have no idea why you get that error though. You should have write access to that folder, the configure file itself is owned by you (we), and the exec bit is set. I am stumped. I would suggest trying to run a very simple executable: 1. create a file on your desktop called "hello" with the following contents: ----- #!/bin/bash echo "hello world" ----- then run chmod +x ./hello ./hello Does that work? Regardless of the above, what is the exit code after you run ./configure ? To find that out, run the following immediately after: echo $? So you would do ./configure echo $? Scott
signature.asc
Description: PGP signature
