delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/03/03/19:54:17

From: Myknees <Myknees AT aol DOT com>
Message-ID: <1877b620.34fca533@aol.com>
Date: Tue, 3 Mar 1998 19:49:52 EST
To: eliz AT is DOT elta DOT co DOT il
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Subject: Re: emacs (was Re: New User : Vi)

In a message dated 98-03-03 03:30:49 EST, you write:
>  On Mon, 2 Mar 1998, Myknees wrote:
>  
>  > just saying it:  I typed "make install" and the other things that I
>  > described; I saw much successful-looking activity on the screen; and
>  > then I was thoroughly confused to find no bin directory and no new
>  > emacs.exe.
>  
>  This would probably mean that either the line which creates the bin
>  subdirectory somehow fails, or `mv' fails to move the emacs.exe
>  there.

Well, I searched the whole hard disk, and there is only one file named
"emacs.exe", and that's the version 19.34 one.

>  What version of Make, and what version of `mv' did you use?  Are you
>  sure these are the latest DJGPP ports?

GNU Make version 3.76.1
mv (GNU fileutils) 3.16

I got them a few months ago when I was gearing up to rebuild the binutils.

>  Also, do you maybe set SHELL in the environment to point to Bash or
>  another Unix-like shell?

No, it is plain-old command com.

>  You could try to create the bin subdirectory by hand, then run "make
>  install" once again and see if that helps.  If it does, we still will
>  need to understand why the following line doesn't work for you:

I think that I know one problem.  I am failing to carefully read what make is
saying.  I just typed "make install" after creating a bin directory, and this
is what I saw:


C:\elc\djgpp\gnu\emacs  .make install
cd lib-src
c:/elc/djgpp/bin/make.exe
make.exe[1]: Entering directory `c:/elc/djgpp/gnu/emacs/lib-src'
make.exe[1]: Nothing to be done for `all'.
make.exe[1]: Leaving directory `c:/elc/djgpp/gnu/emacs/lib-src'
cd ..
cd src
c:/elc/djgpp/bin/make.exe
make.exe[1]: Entering directory `c:/elc/djgpp/gnu/emacs/src'
make.exe[1]: Nothing to be done for `all'.
make.exe[1]: Leaving directory `c:/elc/djgpp/gnu/emacs/src'
redir -o gdb.sed echo '/-geometry/s,^.*,set environment HOME
c:/elc/djgpp/gnu/em
acs,'
redir -oa gdb.sed echo '/environment *TERM/s/^.*/set environment TERM
internal/'

redir -oa gdb.sed echo '/x_error_quitter/s/^.*/set environment NAME root/'
redir -o gdb.tmp sed -f gdb.sed _gdbinit
redir -oa gdb.tmp echo 'set environment USER root'
redir -oa gdb.tmp echo 'set environment EMACSPATH c:/elc/djgpp/gnu/emacs/bin'
redir -oa gdb.tmp echo 'set environment SHELL C:/WINDOWS/COMMAND.COM'
redir -oa gdb.tmp echo 'set environment PATH
C:/WINDOWS;C:/WINDOWS/COMMAND;C:/EL
C/DOS;C:/ELC/DJGPP/BIN;C:/ELC/PERL/BIN;C:/ELC/DJGPP/GNU/EMACS/BIN;C:/ELC/DJGPP
/G
NU/EMACS'
update gdb.tmp gdb.ini
rm -f gdb.tmp gdb.sed
cd ..
cd man
c:/elc/djgpp/bin/make.exe
make.exe[1]: Entering directory `c:/elc/djgpp/gnu/emacs/man'
make.exe[1]: *** No rule to make target `viper-cmd.texi', needed by
`../info/vip
er'.  Stop.
make.exe[1]: Leaving directory `c:/elc/djgpp/gnu/emacs/man'
make.exe: *** [man] Error 2


Now, I realize that I was clueless before: I saw that error message before and
it didn't register.  So perhaps the whole make install is being cut short due
to an error.  The more I look at the makefile the more it looks like batch
file syntax, and following the labels it looks like the process exits in the
section labeled "man".  OK.

It's still weird that that error occured, though.  

>  	if not exist bin\nul md bin
>  
>  > Now that you mention it, there is a 4219K emacs file in the src
directory.
>  
>  Mine is smaller: 3879K.  How weird...

That too is strange.  

I thought that maybe the problem was the untar program that I used to un-
compress the tar.gz file, so I used djtar and re-performed the patching,
configuring, and make-installing.  I still got the same error at the end of
the make install:

cd ..
cd man
c:/elc/djgpp/bin/make.exe
make.exe[1]: Entering directory `c:/elc/djgpp/gnu/emacs/man'
cd .; makeinfo emacs.texi
Making info file `../info/emacs' from `emacs.texi'.
make.exe[1]: *** No rule to make target `viper-cmd.texi', needed by
`../info/vip
er'.  Stop.
make.exe[1]: Leaving directory `c:/elc/djgpp/gnu/emacs/man'
make.exe: *** [man] Error 2

So the next thing I would try is downloading the whole tar file again, but I
won't be able to do that right away.  There's also a chance that this is
another manifestation of the bug you just fixed in make-- would that make
sense in this case?

--Ed (Myknees)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019