Linker errors? My first assumption is that you are trying to link to the PAM libraries, in which case... gcc -o pam_module.so pam_module.c -llibpam Of course this is all listed within the developers handbook Jas On Dec 20, 2011, at 5:53 PM, "ben" <ben@xxxxxxxxxxxxxxxxxx> wrote: > So the problem began with browsing my Linux distro's repository looking > for a pam module to create home directories on demand. I found one that > works almost like I want. Almost, not quite, so onto the source code. It > is written in python. I have a severe Pathological and Eclectic aversion > to python. It reminds me of the Rubbish Lists i turned in in my > hi-school COBOL programing class. I'd rather try to transcend dental > medication. > > so... I've been looking for a project to brush up my c skills, maybe > embed a interpreter for practice... so announcing version 0.0001. Write > your own device driver days here. It is about 75% to theoretically > functional level. > > I expect to reach theoretical functional in about a week or two, but I > figured that this is far enough along to fire up a debugger, Which > brings us to the real question: how do you debug pam modules, especially > linker errors? > > code is available. License requires fixing bugs to distribute until > version 0.5 when I will go gpl. > thanks, > ben > > -- > Ben Hildred > Estimator > Applied Plastic Coatings, Inc. > 5000 Tabor St. > Wheat Ridge, CO 80033 > 303 424 9200 > F: 303 424 8800 > ben@xxxxxxxxxxxxxxxxxx > http://appliedplastic.com > > _______________________________________________ > Pam-list mailing list > Pam-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/pam-list _______________________________________________ Pam-list mailing list Pam-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/pam-list
