From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 31961@debbugs.gnu.org
Subject: bug#31961: java-libsnappy and java-libsnappy-1 have test failures (java.lang.UnsatisfiedLinkError)
Date: Mon, 25 Jun 2018 12:16:52 +0200 [thread overview]
Message-ID: <20180625121652.028fc269@alma-ubu> (raw)
In-Reply-To: <87y3f318hl.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Mon, 25 Jun 2018 12:11:18 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:
>
> > java.lang.UnsatisfiedLinkError: /tmp/snappy-unknown-libsnappyjava.so: /gnu/store/4ixlfq2baw24ihqx3058vcbq5sq9q5y3-gcc-4.9.4-lib/lib/libstdc++.so.6:
> > version `GLIBCXX_3.4.21' not found (required
> > by /gnu/store/4amdzkqix0grksrgw3h5wcv2azvz6pkd-snappy-1.1.7/lib/libsnappy.so.1)
> > org.xerial.snappy.SnappyError:
> > java.lang.UnsatisfiedLinkError: /tmp/snappy-unknown-libsnappyjava.so: /gnu/store/4ixlfq2baw24ihqx3058vcbq5sq9q5y3-gcc-4.9.4-lib/lib/libstdc++.so.6:
> > version `GLIBCXX_3.4.21' not found (required
> > by /gnu/store/4amdzkqix0grksrgw3h5wcv2azvz6pkd-snappy-1.1.7/lib/libsnappy.so.1)
>
> Where does that old GCC come from?
>
I understand too few of the C/linking system to answer that. I rebuilt
snappy, greped through the sources and the build log, the guix gc
--references, and found nothing. That's it for me. Anyone else?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-06-25 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 22:11 bug#31961: java-libsnappy and java-libsnappy-1 have test failures (java.lang.UnsatisfiedLinkError) Björn Höfling
2018-06-25 10:11 ` Ricardo Wurmus
2018-06-25 10:16 ` Björn Höfling [this message]
2018-07-03 12:23 ` Gábor Boskovits
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=20180625121652.028fc269@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=31961@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.