Mail Archives: djgpp/1997/12/21/13:46:41
on Sun, 21 Dec 1997 12:12:01 GMT Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> in
<Pine DOT SUN DOT 3 DOT 91 DOT 971221141137 DOT 8399a-100000 AT is> wrote:
>
>On Sat, 20 Dec 1997, John Covici wrote:
>
>> When I try to build emacs, I get a SIGSEGV while compiling syntax.c.
>
>It doesn't happen to me. Please tell which version of Emacs is that
>(19.34 or 20.2), and post the crash traceback.
It is 20.2 and here is what I got.
cd lib-src
f:/djgpp/bin/make.exe
make.exe[1]: Entering directory `f:/emacs-20.2/lib-src'
make.exe[1]: Nothing to be done for `all'.
make.exe[1]: Leaving directory `f:/emacs-20.2/lib-src'
cd ..
cd src
f:/djgpp/bin/make.exe
make.exe[1]: Entering directory `f:/emacs-20.2/src'
gcc -c -Demacs -DHAVE_CONFIG_H -I. -I. -O2 -g syntax.c
When I run it now, it just sits there -- not even an error. That would
suggest some kind of memory problem since I have a couple of more
processes running now than before.
I am using Windows 95 with a 200mhz Pentium and 40mb of real memory.
Here is my ejgpp.env
#= Don't edit this line unless you move djgpp.env outside
#= of the djgpp installation directory. If you do move
#= it, set DJDIR to the directory you installed DJGPP in.
#=
DJDIR=%:/>DJGPP%
+USER=dosuser
+TMPDIR=%DJDIR%/tmp
+EMU387=%DJDIR%/bin/emu387.dxe
+LFN=y
[bison]
BISON_HAIRY=%DJDIR%/lib/bison.hai
BISON_SIMPLE=%DJDIR%/lib/bison.sim
[cpp]
CPLUS_INCLUDE_PATH=%/>;CPLUS_INCLUDE_PATH%%DJDIR%/lang/cxx;%DJDIR%/include;%DJDIR%/contrib/grx20/include
C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/contrib/grx20/include
OBJCPLUS_INCLUDE_PATH=%/>;OBJCPLUS_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/lang/objc
OBJC_INCLUDE_PATH=%/>;OBJC_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/lang/objc
[gcc]
COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin
LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib;%DJDIR%/contrib/grx20/lib
[info]
INFOPATH=%/>;INFOPATH%%DJDIR%/info;/emacs-20.2/info
INFO_COLORS=0x1f.0x31
[emacs]
INFOPATH=%/>;INFOPATH%%DJDIR%/info;/emacs-20.2/info
[less]
LESSBINFMT=*k<%X>
LESSCHARDEF=8bcccbcc12bc5b95.b127.b
LESS=%LESS% -h5$y5$Dd2.0$Du14.0$Ds4.7$Dk9.0$
[locate]
+LOCATE_PATH=%DJDIR%/lib/locatedb.dat
[ls]
+LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37:*.gl=01;37:*.dl=01;37:*~=08:*.bak=08:
[dir]
+LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37:*.gl=01;37:*.dl=01;37:*~=08:*.bak=08:
[vdir]
+LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37:*.gl=01;37:*.dl=01;37:*~=08:*.bak=08:
>> Also, it looks like the djgpp info directory calls for .inf files, not
>> .info files as suggested in another thread.
>
>I don't understand what that means. What do you mean by ``the djgpp
>info directory calls for .inf files''? How can a directory call for
>files?
By directory I mean the dir file in the info directory. Sorry for the
confusion.
--
John Covici
covici AT ccs DOT covici DOT com
- Raw text -