Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12671] New: leveldb won't detect that snappy is present (static libs only)
Date: Thu, 19 Mar 2020 09:36:43 +0000	[thread overview]
Message-ID: <bug-12671-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=12671

            Bug ID: 12671
           Summary: leveldb won't detect that snappy is present (static
                    libs only)
           Product: buildroot
           Version: 2020.02
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: maksis33 at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Fresh installation of 2020.02 with the following config:

Toolchain -> Enable C++ support -> enabled
Build options -> libraries -> static only
Target packages -> Libraries -> Database -> leveldb -> enabled

From the cmake output of leveldb:

-- Looking for snappy_compress in snappy
-- Looking for snappy_compress in snappy - not found


Snappy is being detect correctly when building with shared libraries. This
issue wasn't present in buildroot 2019.02.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-03-19  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  9:36 bugzilla at busybox.net [this message]
2020-03-26 13:08 ` [Buildroot] [Bug 12671] leveldb won't detect that snappy is present (static libs only) bugzilla at busybox.net
2020-05-18  5:23 ` bugzilla at busybox.net
2020-05-18  6:27 ` bugzilla at busybox.net
2020-06-03 14:53 ` bugzilla at busybox.net

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=bug-12671-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox