From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] samba: Add support for libnss_win*.so* installation
Date: Wed, 26 Nov 2014 22:26:07 +0100 [thread overview]
Message-ID: <20141126222607.4c57066e@free-electrons.com> (raw)
In-Reply-To: <1416960016-5956-1-git-send-email-benoit.thebaudeau.dev@gmail.com>
Dear Beno?t Th?baudeau,
On Wed, 26 Nov 2014 01:00:15 +0100, Beno?t Th?baudeau wrote:
> The libnss_wins and libnss_winbind libraries are required in order to
> add support for the wins and winbind sources to the Name Service Switch
> (NSS), so make it possible to install them. This is useful in order to
> resolve NetBIOS names or user and group information from a Windows NT
> server.
>
> These libraries are installed to /lib/ like the standard libnss_*
> libraries from (E)GLIBC.
>
> Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau.dev@gmail.com>
Applied to next. One question, though.
> +ifeq ($(BR2_PACKAGE_SAMBA_LIBNSS_WINS),y)
> +define SAMBA_INSTALL_LIBNSS_WINS
> + # install libnss_wins
> + $(INSTALL) -m 0755 -D $(@D)/nsswitch/libnss_wins.so $(TARGET_DIR)/lib/libnss_wins.so
> + ln -snf libnss_wins.so $(TARGET_DIR)/lib/libnss_wins.so.2
This dance is a bit weird. Normally, it's the opposite that is done:
the .so.X is the real file, and the .so is a symbolic link. Any reason
to do it the way you did it?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-26 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 0:00 [Buildroot] [PATCH v2] samba: Add support for libnss_win*.so* installation Benoît Thébaudeau
2014-11-26 0:09 ` Benoît Thébaudeau
2014-11-26 21:26 ` Thomas Petazzoni
2014-11-26 21:26 ` Thomas Petazzoni [this message]
2014-11-27 20:46 ` Benoît Thébaudeau
2014-11-27 21:22 ` Thomas Petazzoni
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=20141126222607.4c57066e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox