public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Pranjal Goswami <mechanic.p@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Pranjal Goswami via Libc-help <libc-help@sourceware.org>
Subject: Re: Need help with adding a new service to nsswitch.conf
Date: Wed, 15 Jun 2022 12:33:27 +0530	[thread overview]
Message-ID: <CANrCi94Pf9Xb4oiipddvTyohAaED80MwxHrC9=b+DqNof9V6ow@mail.gmail.com> (raw)
In-Reply-To: <87r13qqxs7.fsf@oldenburg.str.redhat.com>

I see. So we have an option of building my own NSS module outside the glibc
build system , referencing <nss.h> and using  NSS_DECLARE_MODULE_FUNCTIONS
(secmgr) to get to the  declarations for the plug-in functions. So it means
that for writing a new module, we need <nss.h> and
NSS_DECLARE_MODULE_FUNCTIONS (secmgr)  only. There are no other changes to
be done within the nss folder ?

Regards
Pranjal

On Wed, Jun 15, 2022 at 11:21 AM Florian Weimer <fweimer@redhat.com> wrote:

> * Pranjal Goswami via Libc-help:
>
> > Hi Friends ,
> > I am looking at adding another service in nsswitch.conf which can look
> for
> > user presence in a file other than /etc/password. I have copied the files
> > from nss_files  to a new folder and I  have made the changes in the
> > Makefile  under nss to get my module to build.. However I get an error
> when
> > I try  to build glibc.
> > /../include/libc-symbols.h:34:32: warning: "MODULE_libnss_secmgr" is not
> > defined, evaluates to 0 [-Wundef]
> >    34 | #define IN_MODULE  PASTE_NAME (MODULE_, MODULE_NAME)
> >       |                                ^~~~~~~
> > ./../include/libc-symbols.h:32:26: note: in definition of macro
> > 'PASTE_NAME1'
> >    32 | #define PASTE_NAME1(a,b) a##b
> >       |                          ^
> > ./../include/libc-symbols.h:34:20: note: in expansion of macro
> 'PASTE_NAME'
> >    34 | #define IN_MODULE  PASTE_NAME (MODULE_, MODULE_NAME)
> >
> > secmgr is the module that I am adding. I suspect that the problem is
> > related to the  line NSS_DECLARE_MODULE_FUNCTIONS (secmgr).
> > So if we are adding a new service under nss , what additional things we
> > need to do besides adding a module under nss and having teh same set of
> > files as in nss/files - renamed to the  new service that that  am using?
>
> Is there a reason why you need to build your NSS module under the glibc
> build system?  <nss.h> is an installed header file, and you can use
> NSS_DECLARE_MODULE_FUNCTIONS (secmgr) to get declarations for all the
> recognized plug-in functions.
>
> Thanks,
> Florian
>
>

  reply	other threads:[~2022-06-15  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 14:56 Pranjal Goswami
2022-06-15  5:51 ` Florian Weimer
2022-06-15  7:03   ` Pranjal Goswami [this message]
2022-06-15  7:07     ` Florian Weimer
2022-06-15  9:58       ` Pranjal Goswami

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='CANrCi94Pf9Xb4oiipddvTyohAaED80MwxHrC9=b+DqNof9V6ow@mail.gmail.com' \
    --to=mechanic.p@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).