From: <dav...@am...> - 2001-08-31 21:36:50
|
Hi, I'm new to Linux, and am trying to get the LTP quickhitter tests running. As a first step, I unzipped the LTP files and this created the ltp-20010801 directory. Then I did a "make Clean" followed by a "make" from the ltp-20010801 directory. I had a few problems that I wanted to report: 1) The build found failures on many of the include files and several of the C files. One of the predominant failures was something about having extra "/" charaters in the file(s). I looked at the affected files using VI, and saw that at the end of the lines the ^M sequence was present. To fix this, I edited the files using kedit, made a small, innocuous change, and then saved the file. All of these build errors went away after I "fixed" 7 or 8 files in this manner. 2) Near the end of the build, the makefile tries to run lex against scan.l to create scan.c. Lex is not included in my SuSE distribution, and so I will have to go find a version that's compatible with what the original builder's used. That's where I am left at right now. Can you tell me what version of Lex to use and where I can get it? Thanks, Dave. |
From: Aaron L. <al...@sg...> - 2001-08-31 22:07:53
|
dav...@am... wrote: > > 1) The build found failures on many of the include files and > several of the C files. One of the predominant failures was something > about having extra "/" charaters in the file(s). I looked at the > affected files using VI, and saw that at the end of the lines the ^M > sequence was present. To fix this, I edited the files using kedit, made > a small, innocuous change, and then saved the file. All of these build > errors went away after I "fixed" 7 or 8 files in this manner. The ^M comes for 'carriage return' character before the 'newline'. Unix systems use only a single newline character to indicate an end of line. The ^M is vi's way of displaying a control character it can't display. Other operating systems, such as Windows, use a combination of carriage return before a newline. Could it be that one of the files was edited on Windows and then compiled on linux? That said, I was able to compile all of quickhit without a hitch. > 2) Near the end of the build, the makefile tries to run lex > against scan.l to create scan.c. Lex is not included in my SuSE > distribution, and so I will have to go find a version that's compatible > with what the original builder's used. That's where I am left at right > now. Can you tell me what version of Lex to use and where I can get it? Its called 'flex,' which is the GNU version. On my system: $ ls -l /usr/bin/lex lrwxrwxrwx 1 root root 4 Sep 1 2000 /usr/bin/lex -> flex* --aaron -- Aaron Laffin Silicon Graphics, Inc. |
From: Andreas J. <aj...@su...> - 2001-09-01 05:47:00
|
dav...@am... writes: > 2) Near the end of the build, the makefile tries to run lex against > scan.l to create scan.c. Lex is not included in my SuSE distribution, and > so I will have to go find a version that's compatible with what the > original builder's used. That's where I am left at right now. Can you tell > me what version of Lex to use and where I can get it? Just install the flex RPM which should be part of the distro, it contains a link to lex. Andreas -- Andreas Jaeger SuSE Labs aj...@su... private aj...@ar... http://www.suse.de/~aj |