Re: PM: Re: Installation Problem --no exporting
Axel Heinrici wrote: >> What I suggested you do in http://tinyurl.co.uk/b4uu is to save the >> changes in a file makefile.diff in the top level src directory. >> Thereafter, use the 'patch' program to modify lib/Makefile.in: >> $ patch -p0 < makefile.diff >> > Hmm. Are we talking about the same URL? Me and me collegue both read > that page and we did not get what you are telling above. The url should expand to http://marc.theaimsgroup.com/?l=lyx-users&m=107031057322905&w=2 In my description, I meant "The patch is listed at the bottom of the text. Save it as "makefile.diff." Sorry for any confusion. > Anyway, changing lib/Makefile.in manually (emacs) worked. I am just > telling this here because I have the feeling that some other poeple > might run into the same problem. Glad you got all to work. -- Angus
Re: PM: Re: Installation Problem --no exporting
Hi On Wednesday 07 January 2004 10:50, Angus Leeming wrote: > My pleasure. Let's return this to the list. Okay, just thought the topic was getting a little away from general interest. But first of all, I now have lyx 1.3.3 working here on SuSE 8.1. It is also and printing and exporting. > > of the ./configure-make procedure. I don't understand what exactly > > is meant by "... lib/Makefile.in, that we generate automatically > > from lib/Makefile.am. ...". > > When is this _generated automatically_? After running the configure > > skript and after running make the file lib/Makefile.in in the > > tarball is still identical to the one in the extracted source tree. > > And so the make install fails again. > > Can you, please, deconvolute this fix a litte for me? > > Sure. > The source code is developed with the help of GNU automake, autoconf, > libtool etc, known collectively as the GNU autotools. These are used > to generate the configure script and Makefile.in files that you use > as the starting point when building lyx. > > Ie, the code that you get is one step removed from the code that is > in the cvs tree. (It is created by "make dist" actually.) Here exactly comes the problem. Neither make dist nor running autoconf and automake manually helped me anything after changing lib/Makefile.am (it tried before, of course). SuSE 8.1 has automake 1.7.6., so I get an error message telling me it is too recent (this version-terror will send me to sanitorium someday). > What I suggested you do in http://tinyurl.co.uk/b4uu is to save the > changes in a file makefile.diff in the top level src directory. > Thereafter, use the 'patch' program to modify lib/Makefile.in: > $ patch -p0 < makefile.diff > Hmm. Are we talking about the same URL? Me and me collegue both read that page and we did not get what you are telling above. Anyway, changing lib/Makefile.in manually (emacs) worked. I am just telling this here because I have the feeling that some other poeple might run into the same problem. Axel
Re: PM: Re: Installation Problem --no exporting
On Wednesday 07 January 2004 9:38 am, Axel Heinrici wrote: > Hi > > On Tuesday 06 January 2004 15:25, Angus Leeming wrote: > > There is a bug in the lyx-1.3.3 installation scripts. The fix is a > > bit convoluted, but is described in detail here: > > > > http://tinyurl.co.uk/b4uu > > Thanks first. My pleasure. Let's return this to the list. > Excuse me, but there is still a question. Since I am just about to learn > the basics about C, I don't know too much about the internals of > the ./configure-make procedure. I don't understand what exactly is > meant by "... lib/Makefile.in, that we generate automatically from > lib/Makefile.am. ...". > When is this _generated automatically_? After running the configure > skript and after running make the file lib/Makefile.in in the tarball > is still identical to the one in the extracted source tree. > And so the make install fails again. > Can you, please, deconvolute this fix a litte for me? Sure. The source code is developed with the help of GNU automake, autoconf, libtool etc, known collectively as the GNU autotools. These are used to generate the configure script and Makefile.in files that you use as the starting point when building lyx. Ie, the code that you get is one step removed from the code that is in the cvs tree. (It is created by "make dist" actually.) What I suggested you do in http://tinyurl.co.uk/b4uu is to save the changes in a file makefile.diff in the top level src directory. Thereafter, use the 'patch' program to modify lib/Makefile.in: $ patch -p0 < makefile.diff Now, when you run configure, the generated lib/Makefile should result in "make install" working as expected. Hope this helps, Angus
