From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Cppunit undefined reference
Date: Sat, 2 May 2015 23:00:26 +0200 [thread overview]
Message-ID: <20150502210026.GA9796@debian> (raw)
Hello,
trying to create a package for librevenge (input of libreoffice), during
"make check" the following happens:
CXXLD test
/gnu/store/6zd4cq3qsxlvcla5wpysf8sadmnq5l5w-cppunit-1.12.1/lib/libcppunit.so: undefined reference to `dlsym'
/gnu/store/6zd4cq3qsxlvcla5wpysf8sadmnq5l5w-cppunit-1.12.1/lib/libcppunit.so: undefined reference to `dlopen'
/gnu/store/6zd4cq3qsxlvcla5wpysf8sadmnq5l5w-cppunit-1.12.1/lib/libcppunit.so: undefined reference to `dlclose'
collect2: error: ld returned 1 exit status
John passed "LDFLAGS=-ldl", and the tests pass. Is this the good approach,
or do we have a problem with cppunit?
$ ldd /gnu/store/6zd4cq3qsxlvcla5wpysf8sadmnq5l5w-cppunit-1.12.1/lib/libcppunit.so
linux-vdso.so.1 (0x00007fffbe81b000)
libstdc++.so.6 => /gnu/store/rsw0dkmv1x2krv9pl1ciai1h235r9nb7-gcc-4.8.4-lib/lib/libstdc++.so.6 (0x00007f098eb8c000)
libm.so.6 => /gnu/store/hy2hi0zj5hrqkmkhpdxf04c9bcnlnsf9-glibc-2.21/lib/libm.so.6 (0x00007f098e889000)
libc.so.6 => /gnu/store/hy2hi0zj5hrqkmkhpdxf04c9bcnlnsf9-glibc-2.21/lib/libc.so.6 (0x00007f098e4e9000)
libgcc_s.so.1 => /gnu/store/rsw0dkmv1x2krv9pl1ciai1h235r9nb7-gcc-4.8.4-lib/lib/libgcc_s.so.1 (0x00007f098e2d3000)
/gnu/store/wiqbxcvzj3r35hd55yxzz919b1dv1hnv-glibc-2.21/lib/ld-linux-x86-64.so.2 (0x00007f098f0ce000)
Running "strings" on libcppunit.so indeed returns instances of "dlopen".
And adding LDFLAGS=-ldl to cppunit instead of librevenge works as well;
I suppose that this is the good approach finally?
Andreas
next reply other threads:[~2015-05-02 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 21:00 Andreas Enge [this message]
2015-05-03 7:38 ` Cppunit undefined reference Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150502210026.GA9796@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.