From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: gmock linkage / packaging errors
Date: Fri, 06 Mar 2015 00:14:58 +0100 [thread overview]
Message-ID: <54F8E372.1060103@bisect.de> (raw)
In-Reply-To: <54F89BEB.3080303@dachary.org>
Am 05.03.2015 um 19:09 schrieb Loic Dachary:
> Hi Danny,
>
> The build of master shows linkage errors:
>
> http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-deb-trusty-amd64-basic/log.cgi?log=60e2bec73ff3970e0c6b44250ce465e6c5dde56f
>
> error: dpkg-shlibdeps: couldn't find library libgmock_main.so.0 needed by debian/ceph-test/usr/bin/ceph_test_cls_lock (ELF format: 'elf64-x86-64'; RPATH: '')
>
> error: dpkg-shlibdeps: couldn't find library libgtest.so.0 needed by debian/ceph-test/usr/bin/ceph_test_cls_lock (ELF format: 'elf64-x86-64'; RPATH: '')
>
> error: dpkg-shlibdeps: couldn't find library libgmock_main.so.0 needed by debian/ceph-test/usr/bin/ceph_test_rados_api_c_write_operations (ELF format: 'elf64-x86-64'; RPATH: '')
>
> Do you know where that comes from ? IIRC it successfully compiled in the gitbuilders on a branch of yours. That's weird.
Hm ... I have to take a look at it tomorrow. This build worked on the
branch:
http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-tarball-precise-amd64-basic/log.cgi?log=be7b4c38e363457efab52fc5d8d995b63cdc73fd
and also this one:
http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-tarball-precise-amd64-basic/log.cgi?log=be7b4c38e363457efab52fc5d8d995b63cdc73fd
Not sure why this all is working in the branch and not in master, it's
really strange.
Danny
next prev parent reply other threads:[~2015-03-05 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 18:09 gmock linkage / packaging errors Loic Dachary
2015-03-05 23:14 ` Danny Al-Gaaf [this message]
2015-03-06 16:56 ` Loic Dachary
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=54F8E372.1060103@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.
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.