Build error is solved by following change.
diff --git a/test/Makefile.am b/test/Makefile.am
index 829146d..d764190 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -98,10 +98,10 @@ ack_shutdown_count_set_SOURCES =\
ack_shutdown_count_set_LDADD = $(LIBNDCTL_LIB) $(KMOD_LIBS)
blk_ns_SOURCES = blk_namespaces.c $(testcore)
-blk_ns_LDADD = $(LIBNDCTL_LIB) $(KMOD_LIBS)
+blk_ns_LDADD = $(LIBNDCTL_LIB) $(KMOD_LIBS) $(UUID_LIBS)
pmem_ns_SOURCES = pmem_namespaces.c $(testcore)
-pmem_ns_LDADD = $(LIBNDCTL_LIB) $(KMOD_LIBS)
+pmem_ns_LDADD = $(LIBNDCTL_LIB) $(KMOD_LIBS) $(UUID_LIBS)
dpa_alloc_SOURCES = dpa-alloc.c $(testcore)
dpa_alloc_LDADD = $(LIBNDCTL_LIB) $(UUID_LIBS) $(KMOD_LIBS)
@@ -143,6 +143,7 @@ device_dax_LDADD = \
$(LIBNDCTL_LIB) \
$(KMOD_LIBS) \
$(JSON_LIBS) \
+ $(UUID_LIBS) \
../libutil.a
smart_notify_SOURCES = smart-notify.c
-----Original Message-----
From: Li, Redhairer
Sent: Thursday, December 26, 2019 9:48 AM
To: Dan Williams <[email protected]>
Cc: [email protected]
Subject: RE: [PATCH] daxctl: Change region input type from INTEGER to STRING.
I try "--enable-destructive".
But I always see the following msg when I run "make check" and "make
TESTS=daxctl-devices.sh check".
Do I miss anything here?
/usr/bin/ld: blk_namespaces.o: undefined reference to symbol
'uuid_generate@@UUID_1.0'
//lib/x86_64-linux-gnu/libuuid.so.1: error adding symbols: DSO missing from
command line
collect2: error: ld returned 1 exit status
Makefile:850: recipe for target 'blk-ns' failed
make[3]: *** [blk-ns] Error 1
Makefile:1477: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
Makefile:785: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
Makefile:1079: recipe for target 'check' failed
make: *** [check] Error 2
-----Original Message-----
From: Dan Williams <[email protected]>
Sent: Thursday, December 26, 2019 5:18 AM
To: Li, Redhairer <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] daxctl: Change region input type from INTEGER to STRING.
On Wed, Dec 25, 2019 at 2:33 AM Li, Redhairer <[email protected]> wrote:
>
> Hi Dan,
>
> I don't see any failure even apply my patch.
> What failure do you observe?
I see the failure in the daxctl-devices.sh unit test. That test and others are
included in the "destructive" set of unit tests. They are classified
"destructive" because they write to platform persistent memory resources
instead of the emulated nfit_test resources. You need to pass
"--enable-destructive" to the configure script at build time to enable the
destructive tests.
_______________________________________________
Linux-nvdimm mailing list -- [email protected]
To unsubscribe send an email to [email protected]
