Hi,
the library names and the version in the installed
nanomsg.pc is still not right when using the release tarball.
[zozo@term026 build]$ sudo make install
[ 49%] Built target nanomsg
[ 50%] Built target async_shutdown
[ 51%] Built target block
[ 52%] Built target bug328
[ 53%] Built target bus
[ 54%] Built target cmsg
[ 55%] Built target device
[ 56%] Built target device4
[ 57%] Built target device5
[ 58%] Built target device6
[ 59%] Built target device7
[ 60%] Built target domain
[ 61%] Built target emfile
[ 62%] Built target hash
[ 63%] Built target inproc
[ 64%] Built target inproc_lat
[ 65%] Built target inproc_shutdown
[ 66%] Built target inproc_thr
[ 67%] Built target iovec
[ 68%] Built target ipc
[ 69%] Built target ipc_shutdown
[ 70%] Built target ipc_stress
[ 71%] Built target list
[ 72%] Built target local_lat
[ 73%] Built target local_thr
[ 74%] Built target msg
[ 76%] Built target nanocat
[ 77%] Built target pair
[ 78%] Built target pipeline
[ 79%] Built target poll
[ 80%] Built target prio
[ 81%] Built target pubsub
[ 82%] Built target remote_lat
[ 83%] Built target remote_thr
[ 84%] Built target reqrep
[ 85%] Built target reqttl
[ 86%] Built target separation
[ 87%] Built target shutdown
[ 88%] Built target stats
[ 89%] Built target survey
[ 90%] Built target surveyttl
[ 91%] Built target symbol
[ 92%] Built target tcp
[ 93%] Built target tcp_shutdown
[ 94%] Built target term
[ 95%] Built target timeo
[ 96%] Built target trie
[ 97%] Built target ws
[ 98%] Built target ws_async_shutdown
[100%] Built target zerocopy
Install the project...
-- Install configuration: ""
-- Installing: /usr/include/nanomsg/nn.h
-- Installing: /usr/include/nanomsg/inproc.h
-- Installing: /usr/include/nanomsg/ipc.h
-- Installing: /usr/include/nanomsg/tcp.h
-- Installing: /usr/include/nanomsg/ws.h
-- Installing: /usr/include/nanomsg/pair.h
-- Installing: /usr/include/nanomsg/pubsub.h
-- Installing: /usr/include/nanomsg/reqrep.h
-- Installing: /usr/include/nanomsg/pipeline.h
-- Installing: /usr/include/nanomsg/survey.h
-- Installing: /usr/include/nanomsg/bus.h
-- Installing: /usr/bin/nanocat
-- Removed runtime path from "/usr/bin/nanocat"
-- Installing: /usr/lib64/pkgconfig/nanomsg.pc
*-- Installing: /usr/lib64/libnanomsg.so.Unknown*
-- Installing: /usr/lib64/libnanomsg.so.5.0.0
-- Up-to-date: /usr/lib64/libnanomsg.so
[zozo@term026 build]$ *cat /usr/lib64/pkgconfig/nanomsg.pc*
prefix=/usr
exec_prefix=${prefix}
includedir=${prefix}/include
libdir=${prefix}/lib
Name: nanomsg
Description: High-Performance Scalability Protocols
URL: http://nanomsg.org/
*Version: Unknown*
Requires:
Libs: -L${libdir} -lnanomsg
Libs.private: -lanl -lrt -lpthread -lnsl
Cflags: -I${includedir}
[zozo@term026 build]$ ls -l /usr/lib64/libnanomsg.so
lrwxrwxrwx. 1 root root 19 máj 16 07.00 /usr/lib64/libnanomsg.so ->
libnanomsg.so.5.0.0
[zozo@term026 build]$ ls -l /usr/lib64/libnanomsg.so.Unknown
-rwxr-xr-x. 1 root root 395432 jún 6 08.48 /usr/lib64/libnanomsg.so.Unknown
[zozo@term026 build]$ ls -l /usr/lib64/libnanomsg.so.5.0.0
lrwxrwxrwx. 1 root root 21 jún 6 08.49 /usr/lib64/libnanomsg.so.5.0.0 ->
libnanomsg.so.Unknown
Also, the "libnanomsg.so.Unknown" is the binary, not the .so.5.0.0.
Best regards,
Zoltán Böszörményi
2016-06-04 01:55 keltezéssel, Garrett D'Amore írta:
All,
I’ve posted release candidate 1.0.0rc1 — which is the first (and hopefully final!) release candidate for 1.0.0 of nanomsg.
You can download it at the usual locations.
We’ve addressed (we think) the main outstanding issues, as well as the feedback given to us since v0.9 was released.
Note that one semantic difference you *might notice* (very unlikely) is that the RFC specified limit of 8 hops per message is now enforced for REP and RESPONDENT protocols. (This means you cannot chain more than 8 devices together in series with nn_device().) This limit can be altered with the NN_MAXTTL option, up to a maximum of 255. This limit provides increased protection against loops in device configurations, making it a little harder to shoot yourself in the foot by accident.
I’ve already mentioned that nn_bind() has new semantics around bind/listen, in an earlier message.
We don’t believe that nanomsg is *perfect*, and there are still outstanding issues (particularly some involving inproc, and others involving fork() compatibility), but for the vast majority of users we hope that nanomsg will be found suitable for production use. (We aren’t formally stating that it *is*, but we are *expecting* to soon.)
We do not anticipate any more code changes between now and the production release of 1.0. This release candidate is intended to help us ensure that we really did fix the issues that were causing trouble, and to ensure we iron out the kinks in the process.
We would greatly, greatly appreciate folks taking time to download and test this release candidate. It would be enormously useful in assuring that when we do release 1.0.0 for production use, that that release is “good”.
Thanks.
- Garrett
