Skip to contentSkip to conversation

New: OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5

Buildroot bugzilla at busybox.net 1 participant 2 messages Dec 8, 2017

lore
Share & tools
lore
#0 lore 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

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 10561] OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5

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

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Peter Korsgaard <[email protected]> ---
This isn't a problem. The soname does not _NEED_ to match the package version, and the openzwave upstream has decided (explictly or by accident) to not bump the soname version when releasing version 1.5.

See cpp/build/support.mk in the openzwave sources for details.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.