Package: libnetxx-dev Version: 0.3.2-2 Severity: normal Tags: newcomer upstream
Dear Maintainer, I cross compile with netxx, and then discovered miner bug. The symbolic link between libNetxx.so and libNetxx.so.1 are not in the same package as libNetxx.so.1 * What led up to the situation? I discovered it because I wanted to use the Netxx in both on Armhf and on my AMD64 build machine and libnetxx-dev packages for these mutually exclusive and I had to be swapped libnetxx-dev package depending on what I wanted to build. * What exactly did you do (or not do) that was effective (or ineffective)? I fix this problem for myself, have created the symbolic link and everything works. /usr/lib/arm-linux-gnueabihf/libNetxx.so -> libNetxx.so.1 I tried to do a patch, looking at netxx-0.3.2 code but was not wise on the mkmf file. libnetxx-dev and libnetxx1 is created in the same package, but I can not understand where they mixed together. Sorry, have not create a debian package before. A mini issue in this, why dose not apt-get allow that I have libnetxx-dev:armhf and libnetxx-dev:amd64 installed at the same time? It hase unique paths to the lib, etc. I can not see that there would be a problem. Best regarde Rickard -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
