Fwd: Re: [wdiff-bugs] wdiff-0.6.1 build problems

[Martin von Gagern]

I realize I have forgotten to cc this message to the wdiff-bugs list.

-------- Original Message --------
Subject: Re: [wdiff-bugs] wdiff-0.6.1 build problems
Date: Sat, 03 Apr 2010 09:21:07 +0200
From: Martin von Gagern <address@hidden>
To: Nelson H. F. Beebe <address@hidden>

Hi Nelson!

On 02.04.2010 20:58, Nelson H. F. Beebe wrote:
> I've successfully built, validated, and installed wdiff-0.6.1 on more
> than 25 flavors of Unix, but there are three systems for which the
> builds failed.  In each case, simple workarounds produced success.

Thanks for reporting these issues.

As I don't have the systems in question at my disposal, I'd appreciate
if you could run some tests for me, in the hope that future wdiff
releases will build without workarounds.

> FreeBSD 8.0 and OSF/1 4.0 Alpha:  configure sets
> 
>       LIBS=-lauto

I have to assume that this was due to me using == instead of = in a
shell test string comparison. Please try the attached version, see if
that solves the issue.

> in the Makefile, but no such library exists.  I overrode it with
> 
>       make LIBS=-ltermcap                     # on FreeBSD
>       make LIBS='-ltermcap -lsnprintf'        # on OSF/1

What made you add lsnprintf? The sources of wdiff itself only use
printf, fprintf and sprintf, as far as I can tell. And if something in
Gnulib uses a flavour of snprintf, and doesn't provide it, this might
well be a bug in Gnulib.

If, on the other hand, snprintf is a dependency of termcap, and the
linker doesn't handle dependencies like I'm used from my ELF-based
Linux, then the only reasonable solution might be switching wdiff to use
libtool.

> On Solaris 7 SPARC, compilation with cc fails like this:
> 
>       cc -DHAVE_CONFIG_H -I. -I..  -DDEFAULT_TEXT_DOMAIN=\"wdiff-gnulib\"
>       -I../intl -I/usr/local/include  -I/usr/local/include -c localcharset.c
>       "./getopt.h", line 31: empty file name
>       cc: acomp failed for localcharset.c
> 
> I did a fresh build using gcc-2.95.3 (the last gcc version that builds
> on that O/S), and that solved the problem.

As the problem occurs in Gnulib code, this might be a Gnulib bug. It
would be nice to have a look at the generated lib/getopt.h as well as
config.log and config.status. If you still have these around, or can
downgrade gcc without too much trouble, that is.

Greetings,
 Martin von Gagern

signature.asc
Description: OpenPGP digital signature