On Sun, 3 Feb 2008 20:23:12 -0500 David Boyes <[EMAIL PROTECTED]> wrote:

:>> :>I would have a look at how the vendor's built the package(s). Also,
:>> :>unless you have good reason not to, the vendor's source is the
:>source to
:>> :>start from.
:>> I would prefer starting off with something other than a sledgehammer.

:>Actually, this is rather good advice, especially if you expect your code
:>to interoperate and otherwise play nicely with PAM. There are lots of
:>moving parts to PAM, and looking at how someone else did it will help
:>you get your stuff structured in a compatible way.

:>> Thus leading to my question - are there any special options required?

:>That's what looking at the distribution build will tell you. The various
:>distributions sometimes put PAM headers in different places, and some
:>expect particular options to be used when building libraries, etc.

:>> Is gcc -o enough?

:>No. See above.

:>> I would rather concentrate on the code, rather than packaging at this
:>> early
:>> time.
:>> [snip]
:>> My issue is not in writing the code - it is in the installation. And I
:>> would
:>> like as easy a build method as possible as I start this coding.

:>The two are fairly closely linked. You need to be conscious of how PAM
:>is installed and maintained on your distribution to avoid a lot of extra
:>work later in the game.

OK.

I used an existing directory as a model and I now have modules/pam_dissen as a
directory with what appears to be the appropriate make files.

What make command can I issue to compile pam_dissen.c and generate
pam_dissen.so ?

>From which directory should I issue the make command?

I tried

   make modules/pam_dissen

from the

Linux-PAM-0.99.9.0

directory, with result

make: Nothing to be done for `modules/pam_dissen'.

--
Binyamin Dissen <[EMAIL PROTECTED]>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to