lyx 1.0.4 core dumps on startup
Greetings, I compiled lyx 1.0.4 from the source tar file. After I ran make, I ran ./src/lyx as suggested in the INSTALL file. It gives me the message "Segmentation fault" and exits. So I cannot read the list of known bugs since the program will not start at all. Can you fix this? I am running RedHat Linux 6.0 on a i586. The compiler is egcs version 1.1.2, glibc version is 2.1.1, xforms 0.88. Need any other need information? Thanks, Bobby -- Bobby "the fox" de Vos [EMAIL PROTECTED] ECE - Georgia Tech http://www.devos.org/bobby
lyx does not start
Hi i have lyx-1.0.4.tar.gz, and compiled it as root with ./configure make make install without errors. When i run lyx it sais that i have no LyX directory and i said "yes". After thar an "Alert" window apperes: Error: Could not change to directory: /home/wolfgang/.lyx/ Succes The output of lyx was: LyX: Creating directory /home/wolfgang/.lyx/ and running configure... sh: option `-c' requires an argument lyx: SIGSEGV signal caught Sorry, you have found a bug in LyX. If possible, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Aborted Whats wrong?? Wolfgang
Re: lyx 1.0.4 core dumps on startup
On Sat, Oct 09, 1999 at 12:25:13AM -0400, Bobby de Vos wrote: Greetings, I compiled lyx 1.0.4 from the source tar file. After I ran make, I ran ./src/lyx as suggested in the INSTALL file. It gives me the message "Segmentation fault" and exits. So I cannot read the list of known bugs since the program will not start at all. Can you fix this? I am running RedHat Linux 6.0 on a i586. The compiler is egcs version 1.1.2, glibc version is 2.1.1, xforms 0.88. Need any other need information? Thanks, Bobby Can you run gdb on it and tell us where the crash happens? gdb src/lyx core At the gdb prompt, type "where". -- Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | | Robin Gregory (2/28/92)
install of cvs tree - autoconf/make problems
Dear Lyx developers, I checked out the latest cvs version. After a cd config the readme tells me not to try to run it manually, though the makefile it talks about is not distributed via cvs. I copied this makefile from my pre8 installation, and also moved the $topdir/configure.in to . plus $pre8/aclocal.m4 and $pre8/acconfig to find that autoconf then fails to find the macro defined in $topdir/acinclude.m4 When ignoring the "hands off" readme I don't get beyond configuring LyX version 1.1.1 WARNING: This is a development version. Expect bugs. checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking config.cache system type... same ./configure: line 695: syntax error near unexpected token `AM_INIT_AUTOMAKE(lyx, ' ./configure: line 695: `AM_INIT_AUTOMAKE(lyx, $VERSION)' while autoconf stopped complaining after renaming acinclude.m4 at aclocal.m4 Probably I'm just disqualifying myself to further cvs checkout lyx-_devel_ ... anyway Cheers, Steffen Steffen Moeller [EMAIL PROTECTED]
Re: Unit-Testing
Allan Rae [EMAIL PROTECTED] writes: | the new strand yet but I already have some doubts about the recent removal | of one of those tests. That test was completely bogus, since it demanded that a std::string cannont contain '\0', so the test had to go. Lgb
Re: install of cvs tree - autoconf/make problems
Steffen Moeller [EMAIL PROTECTED] writes: | I checked out the latest cvs version. | After a cd config the readme tells me not to try | to run it manually, though the makefile it | talks about is not distributed via cvs. Do a ./autogen.sh after the checkout. If that fails you are missing some programs needed to compile/create the devel version from cvs. Lgb
Re: Some compilation problems with latest cvs
John Weiss [EMAIL PROTECTED] writes: When I work on LyX I can at least say this: I am not doing this for the benefit of LyX users, I do it because it is fun. _And_ it is not fun writing inferiour C++ knowing that there is a better alternative. It is absolutely possible to do something to support compilers in the progress of moving to ANSI C++, but supporting compilers that don't even try is just plain stupid. | I am very much of the same opinion as Jean-Marc. One of the reasons | I'm even partially involved with LyX is that I only needed to download | two tar files: the source code itself and XForms. Once I had XForms, | all I needed were the source updates. | | When I download source to try out a new program, there are N things | that put me off: We are not speaking of any program, we are speaking of a program developed for fun on the sparetime of the developers. | - I need to download/install multiple libraries that I've never heard | of before and seem to have no use to me otherwise. Bogus point in this discussion. Besides if you want to use the program in question you are expected to have the correct libs. | - It uses the newest, trendiest version of one or more standard | libraries, without regard to how stable those libs are. I do not | appreciate being forced to put the stability of my existing apps at | risk for a new program. Bogus point in this discussion. | - It requires a cutting/bleeding edge compiler. If it's not yet in | widespread use, I see no point in upgrading something. | Furthermore, I may not have root access on certain platforms, thus | preventing me from even being able to upgrade the compiler. So how long did yo uwait until you began to write ANSI C? If admins to not update their C++ compilers to more uptodate ones they obviously does not want C++ programs to be developed or compiled on their systems. Should we only support platforms/users/developers that uses old non ANSI C++ compilers? Where is the C++ community going? Why is movement to ANSI C++ this slow? (read the above qouted answer for the answer to the last question) | I doubt I am the only one who feels this way. I do think that this feeling is misguided. Lgb PS. I am sorry but this discussion really puts me in a lousy mood, but I want it to be fun writing C++ and to me that means ANSI C++. We have a standard help push it.
Re: Some compilation problems with latest cvs
"Lars Gullik Bjønnes" wrote: PS. I am sorry but this discussion really puts me in a lousy mood, but I want it to be fun writing C++ and to me that means ANSI C++. We have a standard help push it. Bravo! My experience is that if it is not fun it either does not get done or gets done poorly. AFAIK LyX-.10 did most of what I needed to do. I upgraded regularly because without testing new and better versions can't make any real progress. I'm just greatful that I don't have to pay $ for the upgrades and, yes, it is fun watching things improve and trying to contribute. Garst
stdlists.inc from /layouts
stdlists.inc contains parameters for "itemize", including: Style Itemize .. ItemSep 0.2 TopSep0.2 BottomSep 0.2 ParSep0.2 ... Should I be able to use this to alter the parameters? I've already tried changing them and including the line: Input stdlists.inc in my article.layout file. But it has absolutely no effect. -- -lsm
Re: lyx 1.0.4 core dumps on startup
On Sat, Oct 09, 1999 at 07:03:38PM -0400, Bobby de Vos wrote: I think I may have found the problem. It only dumps core when I run as root, having run su - from a user account. lyx cannot open the display in this case. If lyx can open the display, ie I run su from a user account, or as a user, lyx runs fine. So maybe you want to see if the display is available, otherwise quit with a message like netscape does. thefox:~# netscape Error: Can't open display: Hmmm... That's strange. This is what happens for my Redhat 6.0 installation with xforms-0.88 and my lyx-1.0.4 RPM installed: [kayvan@satyr ~]$ su - Password: [root@satyr /root]# echo $DISPLAY [root@satyr /root]# lyx lyx: Can't open display LyX: unable to access X display, exiting [root@satyr /root]# So, I don't know what the problem with your setup is. -- Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | | Robin Gregory (2/28/92)
lyx 1.0.4 core dumps on startup
Greetings, I compiled lyx 1.0.4 from the source tar file. After I ran make, I ran ./src/lyx as suggested in the INSTALL file. It gives me the message "Segmentation fault" and exits. So I cannot read the list of known bugs since the program will not start at all. Can you fix this? I am running RedHat Linux 6.0 on a i586. The compiler is egcs version 1.1.2, glibc version is 2.1.1, xforms 0.88. Need any other need information? Thanks, Bobby -- Bobby "the fox" de Vos [EMAIL PROTECTED] ECE - Georgia Tech http://www.devos.org/bobby
lyx does not start
Hi i have lyx-1.0.4.tar.gz, and compiled it as root with ./configure && make && make install without errors. When i run lyx it sais that i have no LyX directory and i said "yes". After thar an "Alert" window apperes: Error: Could not change to directory: /home/wolfgang/.lyx/ Succes The output of lyx was: LyX: Creating directory /home/wolfgang/.lyx/ and running configure... sh: option `-c' requires an argument lyx: SIGSEGV signal caught Sorry, you have found a bug in LyX. If possible, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Aborted Whats wrong?? Wolfgang
Re: lyx 1.0.4 core dumps on startup
On Sat, Oct 09, 1999 at 12:25:13AM -0400, Bobby de Vos wrote: > Greetings, > > I compiled lyx 1.0.4 from the source tar file. After I ran make, I ran > ./src/lyx as suggested in the INSTALL file. It gives me the message > "Segmentation fault" and exits. So I cannot read the list of known > bugs since the program will not start at all. > > Can you fix this? > > I am running RedHat Linux 6.0 on a i586. The compiler is egcs version > 1.1.2, glibc version is 2.1.1, xforms 0.88. Need any other need > information? > > Thanks, > Bobby Can you run gdb on it and tell us where the crash happens? gdb src/lyx core At the gdb prompt, type "where". -- Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | | Robin Gregory (2/28/92)
install of cvs tree - autoconf/make problems
Dear Lyx developers, I checked out the latest cvs version. After a cd config the readme tells me not to try to run it manually, though the makefile it talks about is not distributed via cvs. I copied this makefile from my pre8 installation, and also moved the $topdir/configure.in to . plus $pre8/aclocal.m4 and $pre8/acconfig to find that autoconf then fails to find the macro defined in $topdir/acinclude.m4 When ignoring the "hands off" readme I don't get beyond configuring LyX version 1.1.1 WARNING: This is a development version. Expect bugs. checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking config.cache system type... same ./configure: line 695: syntax error near unexpected token `AM_INIT_AUTOMAKE(lyx, ' ./configure: line 695: `AM_INIT_AUTOMAKE(lyx, $VERSION)' while autoconf stopped complaining after renaming acinclude.m4 at aclocal.m4 Probably I'm just disqualifying myself to further cvs checkout lyx-_devel_ ... anyway Cheers, Steffen Steffen Moeller <[EMAIL PROTECTED]>
Re: Unit-Testing
Allan Rae <[EMAIL PROTECTED]> writes: | the new strand yet but I already have some doubts about the recent removal | of one of those tests. That test was completely bogus, since it demanded that a std::string cannont contain '\0', so the test had to go. Lgb
Re: install of cvs tree - autoconf/make problems
Steffen Moeller <[EMAIL PROTECTED]> writes: | I checked out the latest cvs version. | After a cd config the readme tells me not to try | to run it manually, though the makefile it | talks about is not distributed via cvs. Do a ./autogen.sh after the checkout. If that fails you are missing some programs needed to compile/create the devel version from cvs. Lgb
Re: Some compilation problems with latest cvs
John Weiss <[EMAIL PROTECTED]> writes: When I work on LyX I can at least say this: I am not doing this for the benefit of LyX users, I do it because it is fun. _And_ it is not fun writing inferiour C++ knowing that there is a better alternative. It is absolutely possible to do something to support compilers in the progress of moving to ANSI C++, but supporting compilers that don't even try is just plain stupid. | I am very much of the same opinion as Jean-Marc. One of the reasons | I'm even partially involved with LyX is that I only needed to download | two tar files: the source code itself and XForms. Once I had XForms, | all I needed were the source updates. | | When I download source to try out a new program, there are N things | that put me off: We are not speaking of any program, we are speaking of a program developed for fun on the sparetime of the developers. | - I need to download/install multiple libraries that I've never heard | of before and seem to have no use to me otherwise. Bogus point in this discussion. Besides if you want to use the program in question you are expected to have the correct libs. | - It uses the newest, trendiest version of one or more standard | libraries, without regard to how stable those libs are. I do not | appreciate being forced to put the stability of my existing apps at | risk for a new program. Bogus point in this discussion. | - It requires a cutting/bleeding edge compiler. If it's not yet in | widespread use, I see no point in upgrading something. | Furthermore, I may not have root access on certain platforms, thus | preventing me from even being able to upgrade the compiler. So how long did yo uwait until you began to write ANSI C? If admins to not update their C++ compilers to more uptodate ones they obviously does not want C++ programs to be developed or compiled on their systems. Should we only support platforms/users/developers that uses old non ANSI C++ compilers? Where is the C++ community going? Why is movement to ANSI C++ this slow? (read the above qouted answer for the answer to the last question) | I doubt I am the only one who feels this way. I do think that this feeling is misguided. Lgb PS. I am sorry but this discussion really puts me in a lousy mood, but I want it to be fun writing C++ and to me that means ANSI C++. We have a standard help push it.
Re: Some compilation problems with latest cvs
"Lars Gullik Bjønnes" wrote: >> > PS. I am sorry but this discussion really puts me in a lousy mood, but > I want it to be fun writing C++ and to me that means ANSI C++. We have > a standard help push it. Bravo! My experience is that if it is not fun it either does not get done or gets done poorly. AFAIK LyX-.10 did most of what I needed to do. I upgraded regularly because without testing new and better versions can't make any real progress. I'm just greatful that I don't have to pay $ for the upgrades and, yes, it is fun watching things improve and trying to contribute. Garst
stdlists.inc from /layouts
stdlists.inc contains parameters for "itemize", including: Style Itemize .. ItemSep 0.2 TopSep0.2 BottomSep 0.2 ParSep0.2 ... Should I be able to use this to alter the parameters? I've already tried changing them and including the line: Input stdlists.inc in my article.layout file. But it has absolutely no effect. -- -lsm
Re: lyx 1.0.4 core dumps on startup
On Sat, Oct 09, 1999 at 07:03:38PM -0400, Bobby de Vos wrote: > I think I may have found the problem. It only dumps core when I run as > root, having run su - from a user account. lyx cannot open the display > in this case. If lyx can open the display, ie I run su from a user > account, or as a user, lyx runs fine. So maybe you want to see if the > display is available, otherwise quit with a message like netscape > does. > thefox:~# netscape > Error: Can't open display: Hmmm... That's strange. This is what happens for my Redhat 6.0 installation with xforms-0.88 and my lyx-1.0.4 RPM installed: [kayvan@satyr ~]$ su - Password: [root@satyr /root]# echo $DISPLAY [root@satyr /root]# lyx lyx: Can't open display LyX: unable to access X display, exiting [root@satyr /root]# So, I don't know what the problem with your setup is. -- Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | | Robin Gregory (2/28/92)
