[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lyx-users
Subject:    Re: ANNOUNCE: LyX version 2.2.0 (rc1): solved
From:       Scott Kostyshak <skostysh () lyx ! org>
Date:       2016-04-18 0:30:39
Message-ID: 20160418003039.bjzbwjfsc5ccnhwr () cotopaxi
[Download RAW message or body]


On Sun, Apr 17, 2016 at 08:12:17PM +0200, Wolfgang Engelmann wrote:
> Thanks, Scott,
> for the explanation of the echo $
> 
> As to the compilation of the new lyx version, setting the exec flag on the
> sdb solved the issue and I am in the process of compiling it. I am extremely
> thankful for all who helped me.
> Wolfgang

Glad you got it figured out. Don't hesitate to ask about any future
issues that come up.

By the way, please bottom post. It is one of the few things we ask for
(see https://www.lyx.org/MailingLists#toc7).

Scott
> 
> 
> 
> On 16.04.2016 20:11, Scott Kostyshak wrote:
> > On Sat, Apr 16, 2016 at 10:35:23AM +0200, Wolfgang Engelmann wrote:
> > > Am 15.04.2016 um 21:39 schrieb Scott Kostyshak:
> > > > 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 $?
> > > we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Desktop/lyx-2.2.0rc1$  ./configure
> > > bash: ./configure: Keine Berechtigung
> > > we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Desktop/lyx-2.2.0rc1$  echo $
> > > $
> > > Not sure I did this properly
> > I was not clear that the question mark is part of the command. So the
> > command is:
> > echo $?
> > 
> > You do not need to do this since we already know what the problem is,
> > but it is very useful to know so I'll explain it a little. when a
> > process (think "program" if you want) exits, an exit code is produced.
> > If that exit code is 0, then the process ran successfully. If it is not
> > zero, then there was an error. The exact exit code can be used to figure
> > out what exactly went wrong. For example,
> > 
> > $ doesnotexist
> > doesnotexist: command not found
> > $ echo $?
> > 127
> > 
> > In this case the error message was good enough, but just to make sure,
> > if you run 'man bash', you find that
> > 
> > "If that function is not defined, the shell prints an error message and
> > returns an exit status of 127."
> > 
> > So the exit code is a way for the program (or shell or kernel) to
> > indicate why a process did not run correctly.
> > 
> > the exit code that you get after your ./configure command might have
> > been documented to mean "the mount permissions do not allow executables
> > to run" or something like that.
> > 
> > In general, whenever you run commands and you want to be more confident
> > (otherwise how do you know nothing went wrong? You cannot always depend
> > on error messages) that nothing went wrong, just do
> > 
> > echo $?
> > 
> > and look for a 0.
> > 
> > Scott
> 

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]