Richard W.M. Jones wrote:
> On Mon, Jun 18, 2012 at 11:53:01AM +0200, Jim Meyering wrote:
>> Richard W.M. Jones wrote:
>> > With gnulib from around May 25th, I get this error when compiling
>> > on RHEL 5.
>> >
>> > bash ../../libtool-kill-dependency_libs.sh ../../libtool --tag=CC
>> > --mode=link gcc -g -O2 -o test-futimens test-futimens.o libtests.a
>> > ../../gnulib/lib/libgnu.la libtests.a -lrt
>> > gcc -g -O2 -o test-futimens test-futimens.o
>> > ../../gnulib/lib/.libs/libgnu.a libtests.a -lrt
>> > libtests.a(utimecmp.o): In function `utimecmp':
>> > /home/rjones/d/libguestfs/gnulib/tests/utimecmp.c:183: undefined
>> > reference to `hash_insert'
>> > /home/rjones/d/libguestfs/gnulib/tests/utimecmp.c:200: undefined
>> > reference to `hash_lookup'
>> > /home/rjones/d/libguestfs/gnulib/tests/utimecmp.c:171: undefined
>> > reference to `hash_initialize'
>> > collect2: ld returned 1 exit status
>> > make[3]: *** [test-futimens] Error 1
>> >
>> > I tried to add 'hash' as a dependency of the utimens-tests module, but
>> > that didn't appear to make a difference. Perhaps something is missing
>> > in the 'Link:' section of the module?
>>
>> Hi Rich,
>>
>> Thanks for the report.
>> I've just run gnulib's stand-alone test of the futimens module
>> (along with all of its dependent modules):
>>
>> # Run this from a gnulib source directory.
>> ./gnulib-tool --create-testdir --with-tests --test futimens
>>
>> and all tests linked and passed on Fedora 17, RHEL6.3, and RHEL5.5:
>> (all x86_64)
>>
...
>> PASS: test-futimens
...
>>
>> If that also fails for you, would you please post the full output?
>
> That test does pass, although it skips the specific test we're
> interested in:
>
> skipping test: setting symlink time not supported on this file system
> SKIP: test-utimens
That suggests that it linked.
In what context did you see the link failure?
While running tests for some other package?
> Here's the kernel and filesystem:
>
> $ uname -a
> Linux builder-rhel5 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT
> 2011 x86_64 x86_64 x86_64 GNU/Linux
> $ /sbin/blkid -o value -s TYPE /dev/mapper/VolGroup00-LogVol00
> ext3
>
> Still investigating ...
Hmm... I now see that the kernel in use on that system is a lot newer,
and not an official RHEL5 one: 2.6.37+
I too used ext3:
# df -hT .
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
ext3 220G 81G 128G 39% /
