On Fri, Dec 21, 2012 at 12:28 PM, David Boesner <david.boes...@gmail.com> wrote: > Hi everyone, > > > I'm working on a PAM module. Therefore it is necessary to create a shared > object in > /lib/security. That words fine. My problem is, that the .la file is also > created next to the so file. > That's why I would like to either create a shared object without the la > file or delete the > la file after creating the .so file. > > I try it this way: > > pamlibdir = $(PAM_DEST_DIR) > pamlib_LTLIBRARIES = my_module.la > > my_module_la_SOURCES = ./src/pam_mypam.c > my_module_la_LDFLAGS = -module -avoid-version -shared -export-dynamic > -ltspi -lpam --as-needed --disable-static > my_module_la_CFLAGS= -Wall -Werror -Wextra > > Could you please help me? > > Merry X-Mas and a happy new year to everyone. > > Regards > > David
Have you found a solution to this? I'd like to do the same thing with the GCC builds. When we build with a sysroot, we get lots of improperly placed la files around that we have to manually remove from the toolchain. It'd be fantastic if there was an automatic way to do that.
