public inbox for
 help / color / mirror / Atom feed
From: Florian Weimer <>
To: Pranjal Goswami via Libc-help <>
Cc: Pranjal Goswami <>
Subject: Re: Need help with adding a new service to nsswitch.conf
Date: Wed, 15 Jun 2022 07:51:52 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Pranjal Goswami via Libc-help's message of "Tue, 14 Jun 2022 20:26:14 +0530")

* 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]
>       |                                ^~~~~~~
> ./../include/libc-symbols.h:32:26: note: in definition of macro
>    32 | #define PASTE_NAME1(a,b) a##b
>       |                          ^
> ./../include/libc-symbols.h:34:20: note: in expansion of macro 'PASTE_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.


  reply	other threads:[~2022-06-15  5:51 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 [this message]
2022-06-15  7:03   ` Pranjal Goswami
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).