Re: Error in 'dircolors.c' while building fileutils statically.

[Bob Proulx]

> I’m trying to compile fileutils statically, without nls. I used the 
> commands:
> ------------------------------------------
> ./configure --disable-nls
> make LDFLAGS=-static
> ------------------------------------------

Those should be fine.  However in general I would have passed the
LDFLAGS to configure at configure time.

  LDFLAGS=-static ./configure --disable-nls
  make

In this case it should not matter for you.  But this way configure can
test other options in the presence of your option and deduce
conflicts.  This really comes into play when passing into CFLAGS the
-g or -O options which are mutually exclusive on many compilers.

> The configure command gives no errors, but when I run make I get this error 
> output:
> ------------------------------------------
> ...
> Making all in src
> make[2]: Entering directory `/mnt/linux2/root/originals/fileutils-4.0/src'
> gcc -DLOCALEDIR=\"/usr/local/share/locale\" -DSHAREDIR=\"/usr/local/share\" -
> DHAVE_CONFIG_H -I.. -I. -I../lib -I../intl  -D_FILE_OFFSET_BITS=64  -g -O2 -c 
> dircolors.c
> dircolors.c:40:15: macro "strndup" requires 2 arguments, but only 1 given
> make[2]: *** [dircolors.o] Error 1
> make[2]: Leaving directory `/mnt/linux2/root/originals/fileutils-4.0/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/mnt/linux2/root/originals/fileutils-4.0'
> make: *** [all-recursive-am] Error 2
> ------------------------------------------
> 
> Fileutils is version 4.0 and I’m running Mandrake 8.0.
> 
> I read the README file and the INSTALL file, but no luck. I’ve
> also searched google, but no luck there either. I even opened the
> dircolors.c and had a lock inside, but as the hopeless C programmer
> I am, I didn’t understand much.

That is pretty strange.  I could not see how you would be getting that
message.  I just now test compiled fileutils 4.0 on a Mandrake 8.0
system using your flags and everything worked fine.  I could not
recreate your problem.  I have no suggestions for you except to try it
on a different machine.  At the C program level you could run the
output through 'cc -E' and look at the processed output file.

Note that fileutils-4.1 is available.

  ftp://ftp.gnu.org/pub/gnu/fileutils/fileutils-4.1.tar.gz

Bob