On Thu, 1 Jul 2010 09:27:26 +0200 Wolfgang Engelmann <[email protected]> wrote:
> Am Thursday 01 July 2010 03:21:21 schrieb Alan L Tyree: > > On Thu, 01 Jul 2010 08:47:23 +0800 > > > > "Louis A. Turk" <[email protected]> wrote: > > > On Tue, 2010-06-29 at 11:14 +0200, Wolfgang Engelmann wrote: > > > > Am Tuesday 22 June 2010 19:15:17 schrieb Julien Rioux: > > > > > On 22/06/2010 1:05 PM, Wolfgang Engelmann wrote: > > > > > > Am Tuesday 22 June 2010 18:50:24 schrieb Julien Rioux: > > > > > >> On 22/06/2010 12:12 PM, Wolfgang Engelmann wrote: > > > > > > > > > > > > but this gives me: > > > > > > wolfg...@wolfgang:~/lyx-devel$ autogen.sh > > > > > > bash: autogen.sh: command not found > > > > > > > > > > The ./ (dot slash) is important. It tells your shell to > > > > > execute the file from the current folder. If you get an error > > > > > again, make sure the file is present by doing > > > > > > > > > > ls > > > > > > > > > > which should list the files in the current folder. If you > > > > > copied the LyX source files correctly, you should see > > > > > autogen.sh in there. > > > > > > > > > > Here are build instructions again: > > > > > http://www.physics.utoronto.ca/~jrioux/resources/lyx/#devel > > > > > > > > Hello Julien, > > > > > > > > Thanks for providing your link. Could you kindly answer the > > > > following questions privately? > > > > > > > > 1-Do I have to run the ./autogen.sh in my /lyx-devel as root? I > > > > did this, but am afraid that was wrong. > > > > No, you should run ./autogen.sh as a normal user. > > I should have asked before, - anyway, I did run it already as root. > Can I undo this or would it mess up with the local install? To tell the truth, Wolfgang, I am not entirely sure. I just tried in on my own installation and suggest: make clean This does a lot of cleaning out of any previous makes, etc. Then do ./autogen etc. > > > > > > 2-how do I start the new lyx respectively how do I at what step > > > > tell, the new lyx should eg be called lyx2? > > > > If you used ./configure --with-version-suffix=2, then the installed > > executable will be lyx2. You should be able to run your original LyX > > just by typing lyx in a terminal, the new one by typing lyx2. > > > > If you launch LyX from a panel icon, then right click on the icon > > and choose "Properties". For the "Command" > > enter /usr/local/bin/lyx2. > > > > At the risk of being a boring old guy, I really recommend using GNU > > Stow to install compiled programs. This avoids any risk that the new > > version might trash some part of the version installed by your > > package manager. Also the risk that a new version installed by your > > package manager will accidentally trash some part of the compiled > > version. > > I had installed stow already. > > > > Instructions on using Stow to install are here: > > http://wiki.lyx.org/Tips/Compiling under the heading "Compiling and > > installing with GNU STOW". > --> > y...@yourmachine:~/local/lyx-1.6.5$ sudo make install > prefix=/usr/local/stow/lyx165 > y...@yourmachine:~/local/lyx-1.6.5$ cd /usr/local/stow > y...@yourmachine:/usr/local/stow$ sudo stow lyx165 > > To me this looks like I am installing lyx as root (sudo), which you > did not recommend. No, this is right. You compile LyX as a normal user, but then you install it into your system so that any user has access to it. Like most of us, you are probably the only user on your machine, but it seems to me to be good practice to install software like this so that all users have access. No harm, and just good practice. > > And would a > svn update > (root or user?) > run in my /local folder > give me the latest lyx as kind of lyx-2.x.x in a folder > in /local/lyx-2.x.x or whatever, Run that as normal user. It is just downloading a bunch of files. Everything else just makes the executables until you get to the "install" stage. That puts it in your "public" area so that other users have access. > in which I have to use the steps above > y...@yourmachine:~/local/lyx-2.x.x$ sudo make install > prefix=/usr/local/stow/lyx2.x.x > etc ... > ? > Yes: after you do the "svn update" you have a new set of source files that need to be compiled so that the executables are made. Then you need to "install" them into the public area of your machine. > Sorry for my confusion, but thankful for your patience Mate, we all had a steep learning curve on this!! Let us know how you get on and ask questions when you are not sure. Cheers, Alan > > Wolfgang -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206
