bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AC_FUNC_GETMNTENT problem on UNICOS


From: James Youngman
Subject: AC_FUNC_GETMNTENT problem on UNICOS
Date: Fri, 19 Nov 2004 20:04:00 +0000
User-agent: Mutt/1.3.28i

Hello,

I've received a bug report for findutils that the value that configure
sets up in $LIBS includes -lsun which generates a linker warning
because there is no libsun.a.  I think it turns out that the reason
for this is that "getmntent" is in the C library and hence does not
require -lsun, but attempting to link against the nonexistent -lsun
results in the linker returning atatus 0, and so -lsun is added to
$LIBS by AC_FUNC_GETMNTENT:


AN_FUNCTION([getmntent], [AC_FUNC_GETMNTENT])
AC_DEFUN([AC_FUNC_GETMNTENT],
[# getmntent is in -lsun on Irix 4, -lseq on Dynix/PTX, -lgen on Unixware.
AC_CHECK_LIB(sun, getmntent, LIBS="-lsun $LIBS",
  [AC_CHECK_LIB(seq, getmntent, LIBS="-lseq $LIBS",
    [AC_CHECK_LIB(gen, getmntent, LIBS="-lgen $LIBS")])])
AC_CHECK_FUNCS(getmntent)
])

xHence AC_FUNC_GETMNTENT experiences this problem because AC_CHECK_LIB
doesn't realise that there is no -lsun (or any need for it).


The relevant but of the config.log file looks like this :-

> checking whether getcwd (NULL, 0) allocates memory for result... no
> checking for getpwnam in -lsun... yes
[...]
> checking for getmntent in -lsun... yes
> checking for getmntent... yes

Hence "make" produces the following warning :-

cc  -g   -o find  find.o fstype.o parser.o pred.o tree.o util.o version.o 
../lib/libfind.a ../gnulib/lib/libgnulib.a  -lsun -lsun
 ldr-334 cc: CAUTION
     File 'libsun.a' cannot be found in any of the search directories.

Does anybody have any suggestions as to what I should do about this?

There are more complete log files (and the configure file etc.) in the
original bug report against findutils, which is at
http://savannah.gnu.org/bugs/?func=detailitem&item_id=11008

Please copy any response to Mark Baushke (he's already on the CC list).


Thanks,
James Youngman.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]