Sender: rich AT delorie DOT com
Message-ID: <39081435.E2EDBC04@bigfoot.com>
Date: Thu, 27 Apr 2000 11:19:33 +0100
From: Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Some questions about porting fileutils 4.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

I've started trying to port fileutils 4.0. I've hit a couple of problems:

1. The main top-level Makefile is 'GNUmakefile'. This uses the following
to detect whether configure has been run:

[Quoted from GNUmakefile]
have-Makefile := $(shell test -f Makefile && echo yes)

# If the user runs GNU make but has not yet run ./configure,
# give them a diagnostic.
ifeq ($(have-Makefile),yes)

include Makefile
include $(srcdir)/Makefile.maint

else

all:
        @echo There seems to be no Makefile in this directory.
        @echo "You must run ./configure before running \`make'."
        @exit 1

endif
[End quoted from GNUmakefile]

I have run configure, but when I try running 'make', I get the following
error:

c:/djgpp/bin/test.exe: too many arguments
There seems to be no Makefile in this directory.
You must run ./configure before running \`make'.

This was run from bash. I am running with DJGPP 2.03, bash 2.03,
shellutils 1.12. This is not really a problem, since the GNUmakefile and
Makefile.maint are non-vital - I can build using 'make -f Makefile'.

2. src/chgrp.c seems to require lstat(). I looked at the fileutils 3.16
port and chgrp.c seems unchanged. Since the readme describes chgrp as
being a no-op program, I was wondering how you made it so, Eli?

configure seems to complete OK and finds $PREFIX, $SHAREDIR, etc.
automatically - this /dev/env feature is very nice! I ran configure with
'--disable-nls' - is there any point attempting to build with NLS, given
the recent discussion?

BTW, Eli, I had to upgrade to texinfo 4.0 to read the info docs supplied
with make 3.79. Is this expected? Until I did this, I could not access the
section on $(shell ...) from the menu, even though all the info files were
present.

Thanks, bye,

-- 
Richard Dawe
richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/