Re: LDM 2.2.14 inconsistent plugin path
Vagrant Cascadian <[email protected]> Mon, 15 Sep 2014 23:55:36 -0500
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============5403604081368830153==
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha512; protocol="application/pgp-signature"
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On 2014-09-12 15:55:08 -0500, Floris Bos wrote:
> I compiled LDM 2.2.14 from source, and get a segmentation fault in=20
> ldm_setup_plugin()
...
> The reason it cannot find it in plugin_list is because plugin_list is emp=
ty.
> Seems it searches for plugins in /usr/libexec/ldm, but they are=20
> installed in /usr/lib/ldm
>
> ldm-2.2.14/src/Makefile.am:
>
> ldmlibexecdir =3D $(libexecdir)/ldm
> [...]
> -DLDM_PLUG_DIR=3D\""$(ldmlibexecdir)"\"
>
> ldm-2.2.14/src/plugins/ssh/Makefile.am
>
> ldmplugdir =3D $(libdir)/ldm/
>
>
> Which of the two should be the correct folder?
I suspect they should both use libexecdir...
The problem stems from the fact that on Debian and Ubuntu derivatives,
they are (or should be) the same, and common packaging systems will
build them with libexecdir set to the same value as libdir.
If building manually on Debian or derivatives, it may use the default
for libexecdir and not set it to the same value...
live well,
vagrant
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUF8LIAAoJELeLgtSBS5G2bDQP/iaE0NhNmreWgvIn/6WPG4Gj
RvX3tH18nRx3D6pv5Kbb9heC+1DI5k4N+5MYmEwr/Vd/ys0rEsLbfRCCLSRMV2HA
z6lOmgPAWTAn2oUxDPxwUnX72lHbmD2dxA5VXHurJLIgaw5DY/Yg19nN88jXVtFs
8oeVO6siM3yPk/S5fArkz9pkfHztvxGd9t3Ly2rVphmJeJY/2VJoOwq/+pCpPbRv
rbwlAgdNkjPw/DgVUKu1u07WJfFNRfDe2nfW8cWCZ3j/kFQp6lUXfjxLr3JcRHBD
v0GgMIAMgSmKpUyV8fFx7ld0dbw+zigbdlg8XUcY1O0ldN9wlwmqQOnOXUbtAr/K
Mw7rcaFV/TlWDhiF7eHiP3xfL4MLMYAK1TZOl5w0/HmeDeicCu1IpxXUy2rJ/in6
Lp6M1L9Zhnvf8lyVhvh2hd0d7Hix7mvQCYP+zNDdTdIpPqNyYQxXPDzxv3BgCCZe
E63K6jx0TKQp6DpkmGJUHHz0FYN21tKBwUIPsdFYOaMMMxpEIm1ELBsRxC32XWea
gk9MnzgBqXn4YIk5Lwn8QQnPXpzlWMCKDLairN5wR4sdQyhamUINKT9C7oIe0mAf
2ECkITQ/2JB5Y6MCM2Z7YkwRxR3xdQQ/4Otk4GoUz53P53aS885XYbzNq5mnyzqG
7FCB52Oe+jxdC4Js0Yui
=QtO0
-----END PGP SIGNATURE-----
--=-=-=--
--===============5403604081368830153==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
--===============5403604081368830153==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_____________________________________________________________________
Ltsp-developer mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help, try #ltsp channel on irc.freenode.net
--===============5403604081368830153==--