On Tue, 18 Mar 2003, Ged Haywood wrote:
> I hope you'll do something about the instructions for building it
> before you put it out as 1.1.5. It's very confusing because there's
> so much of it that's out of date and inconsistent. It doesn't need to
> be completely rewritten but if you put some up-to-date instructions in
> a file called INSTALL then people who are used to doing
>
> ./configure
> make
> make install
>
> will be more much comfortable.
This is exactly what the file "QuickStart" is supposed to do -- please
tell me what you want to have changed in QuickStart -- I may be blind but
the instructions are up-to-date as far as I know.
> The build scripts seem to be very fragile, I changed the directories
> in the compiletime-options and although everything was supposed to be
> in my home directory the make install failed with permission problems
> unless I was root.
Shouldn't be and I just tested it. You must clean the tree and recompile
(and reconfigure) DOSEMU if you fiddle with the compiletime-settings
though, but maybe a Makefile rule could be added to do that
automatically.
> It asked me if it was OK to use /home/ged/dosemu
> and I said no, use /home/ged/src/dosemu and it said OK, then I'll use
> /home/ged/src/dosemu/dosemu so I tried to stop that. The script then
> had trouble because it had created ~/.dosemu but hadn't done other
> stuff that was needed. When finally I got it figured out it failed
> again because the symlinks in /usr/local/share/dosemu/freedos/dosemu
> already existed. I had to keep doing rm -rf on a few directories to
> get a build I was happy with.
There are two things here you talk about and I can't quite follow you here
(to be able to correct the problem I must be able to reproduce your
problems and without telling exactly what you did that is very difficult).
a) problems with 'make install'
b) problems running dosemu for the first time.
One problem with a symlink may be solved using:
--- dosemu-1.1.4.15/src/arch/linux/Makefile.main Mon Mar 17 11:26:13 2003
+++ dosemu-1.1.4.16/src/arch/linux/Makefile.main Mon Mar 17 11:27:58 2003
@@ -273,8 +273,8 @@
$(INSTALL) -d $(DESTDIR)$(syshdimagedir)/drives; \
ln -s $(DESTDIR)$(dosemudir)/freedos $(DESTDIR)$(syshdimagedir)/drives/c; \
fi; \
- rmdir $(DESTDIR)$(syshdimagedir)/freedos/tmp; \
- ln -sf /tmp $(DESTDIR)$(syshdimagedir)/freedos/tmp; \
+ rm -f $(DESTDIR)$(dosemudir)/freedos/tmp; \
+ ln -sf /tmp $(DESTDIR)$(dosemudir)/freedos/tmp; \
fi
$(INSTALL) -d $(DESTDIR)$(sysconfdir)
if [ ! -f $(DESTDIR)$(sysconfdir)/dosemu.conf ]; then \
to the question:
Going to install your private DOSEMU files into the directory
$HOME/dosemu
Enter an empty string to confirm, a new path, or \"none\" (without
the quotes) if you don't want this:"
you said you entered
/home/ged/src/dosemu/
and then it uses
/home/ged/src/dosemu/dosemu
well the files are going into "/home/ged/src/dosemu/", just with one more
directory below it. I don't see why that would be a major problem?
The reason why is that a tarfile (by default,
/usr/local/share/dosemu/dosemu-freedos-bin.tgz)
is untarred into this directory and the pathnames just happen to start
with dosemu/
But is what you really mean that the install script could be clearer and
say something like
Going to install your private DOSEMU files into the directory
$HOME/dosemu
Enter an empty string to confirm, a new path, or \"none\" (without
the quotes) if you don't want this,
example: /home/ged/src installs your private DOSEMU files into
/home/ged/src/dosemu.
?
> It grumbled about not having freedos
> even though I'd set 'fdtarball none' in the compiletime-settings.
Same thing here as a few lines above: "fdtarball none" only takes effect
after you run configure again.
> Having said that once it did compile (2.4.19) it started and ran quite
> a few things fine, but the attached pager (LIST.COM) crashes dosemu
> very reliably under X on my system.
I just tried it, it doesn't crash for me. Which DOS are you using in your
DOSEMU?
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
