> :>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. ---------------------------------------------------------------------- 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
