From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10561] New: OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5
Date: Fri, 08 Dec 2017 10:59:39 +0000 [thread overview]
Message-ID: <bug-10561-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10561
Bug ID: 10561
Summary: OpenZwave generates libopenzwave.so.1.4 instead of
libopenzwave.so.1.5
Product: buildroot
Version: 2017.02
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: laibulle at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hello,
I am a new user of BuildRoot. I am trying to use OpenZwave 1.5 on raspberry Pi
3, I have fetched buildroot-2017.02.8.tar.gz but the generated lib is version
1.4 but the content of is package/openzwave/openzwave.mk is
OPENZWAVE_VERSION = V1.5
OPENZWAVE_SITE = $(call github,OpenZWave,open-zwave,$(OPENZWAVE_VERSION))
OPENZWAVE_LICENSE = LGPLv3+, GPLv3 (examples), Apache-2.0 (sh2ju.sh)
OPENZWAVE_LICENSE_FILES = license/license.txt license/lgpl.txt \
license/gpl.txt license/Apache-License-2.0.txt
Am doing something wrong ?
Best regards
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-12-08 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 10:59 bugzilla at busybox.net [this message]
2017-12-08 18:19 ` [Buildroot] [Bug 10561] OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5 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-10561-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