From: Nate Eldredge Newsgroups: comp.os.msdos.djgpp Subject: Re: make problems Date: 23 Jan 2000 12:35:54 -0800 Organization: InterWorld Communications Lines: 37 Message-ID: <83zotwo79x.fsf@mercury.st.hmc.edu> References: NNTP-Posting-Host: mercury.st.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: nntp1.interworld.net 948659867 2652 134.173.45.219 (23 Jan 2000 20:37:47 GMT) X-Complaints-To: usenet AT nntp1 DOT interworld DOT net NNTP-Posting-Date: 23 Jan 2000 20:37:47 GMT User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii writes: > On Sun, 23 Jan 2000, Andy wrote: > > > C:\UTILS\Djgpp\contrib\tvision>make install > > install -d -m 0755 c:/utils/djgpp/include/rhtvision > > C:\UTILS\DJGPP\BIN\GINSTALL.EXE: cannot open > > make.exe: *** [install] Error -1 > > This is due to a known bug in the version of DJGPP with which the > ported Fileutils 3.16 were compiled: simulated symlinks didn't work > when the target of the symlink (ginstall.exe in this case) had exactly > 8 characters in its name before the dot. > > As a work-around, use this: > > make install INSTALL=ginstall > > I'm assuming that the Makefile supplied with YAMD has a variable > INSTALL which is set to "install"; the above command overrides that. > If the above doesn't work, simply edit the Makefile and replace > "install" by "ginstall" manually. Actually, it doesn't. So editing might be necessary. Or you could probably do cd \utils\djgpp\bin copy ginstall.exe install.exe Btw, the next version of YAMD will have the build process completely redone (I'm going to use automake/autoconf, to make porting easier). -- Nate Eldredge neldredge AT hmc DOT edu