From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10561] OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5
Date: Fri, 08 Dec 2017 18:19:22 +0000 [thread overview]
Message-ID: <bug-10561-163-nAn2dL6Jgx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10561-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10561
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-12-08 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 10:59 [Buildroot] [Bug 10561] New: OpenZwave generates libopenzwave.so.1.4 instead of libopenzwave.so.1.5 bugzilla at busybox.net
2017-12-08 18:19 ` bugzilla at busybox.net [this message]
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-nAn2dL6Jgx@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 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.