>>> On Sun, Feb 3, 2008 at 3:50 AM, in message <[EMAIL PROTECTED]>, Binyamin Dissen <[EMAIL PROTECTED]> wrote: > On Sat, 2 Feb 2008 23:04:43 -0700 Mark Post <[EMAIL PROTECTED]> wrote: -snip- > :>What distribution are you building it for? That will determine to a large > extent how you do it. > > SUSE for Z.
Ok, that's an RPM-based distribution. If you had been developing for Slack/390 or Debian/390, that wouldn't have been the case. > But to be even more basic. Say I write my own PAM routine - exactly what > command is required to compile it into an .so format? What I normally recommend to people that want to build packages for a Linux distribution is look at how the distribution provider normally does it. In this case, look at the *.src.rpm package for the PAM modules shipped with SLES. If you do an "rpm -ivh pam*.src.rpm" the source files and patches get put into /usr/src/packages/SOURCES/ and the .spec file gets put into /usr/src/packages/SPECS/. You can look at the .spec file and see exactly how the as-shipped package is built, and adapt that to meet your own needs. > Do I need to create a make file? If you do the job right, and I suspect you're the kind of person that does, then you'll need to create a whole lot more than that. Creating your own .spec file from an existing one can be very tedious trial-and-error work. You'll also need to create your own .src.rpm and ship that with the package. Most PAM packages have a GPL license on them, but some have mixed BSD and GPL , or an Apache license. Mark Post ---------------------------------------------------------------------- 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
