Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libcedar.so not found automatically #766

Closed
2 tasks done
qupfer opened this issue Oct 23, 2018 · 13 comments
Closed
2 tasks done

libcedar.so not found automatically #766

qupfer opened this issue Oct 23, 2018 · 13 comments

Comments

@qupfer
Copy link

qupfer commented Oct 23, 2018

Hi,
I'm not very well with the "libary search thing" of linux systems, so this is maybe correct behaviour and my system is not propper configured. :-)

Prerequisites

  • Can you reproduce?
  • Are you running the latest version of SoftEtherVPN?

SoftEther version:
commit 5b11e6b (HEAD -> master, tag: v5.01.9661, origin/master, origin/HEAD)

Component:
Server

Operating system:
Linux (arch)

Architecture:
64 bit

Description

[Description of the bug]
If I want to start vpnserver (or vpnclient, vpncmd) I got the following error:
/usr/local/libexec/softether/vpnserver/vpnserver: error while loading shared libraries: libcedar.so: cannot open shared object file: No such file or directory
Expected behavior:
vpnserver starts

Actual behavior:
vpnserver did not start because libcedar.so not found

Steps to reproduce

1. ./configure
2. make -j4 -C tmp
3. sudo  make -j4 -C tmp install
4. vpnserver

Workaround

env LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib64 vpnserver

chipitsine added a commit to chipitsine/SoftEtherVPN that referenced this issue Oct 23, 2018
@chipitsine
Copy link
Member

@qupfer , can you try the following #767 ?

chipitsine added a commit to chipitsine/SoftEtherVPN that referenced this issue Oct 23, 2018
@qupfer
Copy link
Author

qupfer commented Oct 24, 2018

Works on my system. Thanks

@chipitsine
Copy link
Member

it works for me as well. ok, merging

@paskal
Copy link
Contributor

paskal commented Nov 5, 2018

https://github.com/paskal/SoftEtherVPN-debianisation/issues/6 is the same, is it supposed to be fixed in upstream?

@davidebeatrici
Copy link
Member

Yes, see #767.

@paskal
Copy link
Contributor

paskal commented Dec 3, 2018

@davidebeatrici @chipitsine current location is an issue for debian:

Found files in /usr/local (must be in /usr).
debian/softether-common/usr/local
debian/softether-common/usr/local/lib
debian/softether-common/usr/local/lib/libcedar.so
debian/softether-common/usr/local/lib/libmayaqua.so
dh_builddeb.pkgbinarymangler: dpkg-deb --build debian/softether-common .. returned exit code 1

I'll switch it to /usr/lib for Ubuntu PPA and suggest you do the same.

@chipitsine
Copy link
Member

we build packages for ubuntu 16.04, 18.04 (I am going to add upload to launchpad for those packages some time)

https://ci.appveyor.com/project/SoftEtherVPN/softethervpn/build/job/w1tydq8nsd0o1b3u

as a part of test process, we install packages and do "systemctl restart ...", it restarts (that means, no issue with /usr/local)

as for "doing the same", it is bad to use hardcode path, I think configurable path is better.
in those terms /usr/local is more "configurable" then default /usr/lib

you can choose either solution.
if you will include "install package" + "test restart" (ike we did already for app veyor), it would be nice

@chipitsine
Copy link
Member

as for "doing the same in upstream", feel free to open PR on that (if you understand what you mean exactly), as I said already, we do not observe those issues in upstream anymore

@paskal
Copy link
Contributor

paskal commented Dec 3, 2018

It's against Debian standard which is why Ubuntu PPA build refuses to do so. Quote:

/usr/local/ : Tertiary hierarchy for local data installed by the system administrator

@chipitsine
Copy link
Member

it is exactly what you are installing.
local data.

how can you determine SE VPN is not local data, installed by system administrator ?

@paskal
Copy link
Contributor

paskal commented Dec 3, 2018

Local data installed by system administrator means something which is brought manually, not by packages: no standard Ubuntu package write to this folder.
Also an issue I've bumped into: I can't use this repo tags because they are not correct version number from dpkg-buildpackage POV:

dpkg-buildpackage: warning:     debian/changelog(l1): version 'v5.01.9665~201812020153~ubuntu18.04.1' is invalid: version number does not start with digit
LINE: softether-vpn (v5.01.9665~201812020153~ubuntu18.04.1) bionic; urgency=low

Because of this I need to maintain my own versions. Could you please use tags without "v" in future?

@chipitsine
Copy link
Member

@paskal, you seem trying to find the worst practice ever.

this issue is closed already. and originally it is not related to tags.

why not to open dedicated issue on tags ?

as for tags, currently they are not used for build numbers. build numbers are supposed to be taken from src/CurrentBuild.txt

probably we need to discuss it and do something. like CI check on "are build numbers the same in tag and inside that file"

@boubou
Copy link

boubou commented Jul 4, 2020

Still have the same issue when building the source from git on a Debian 10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants