autoconf check for building shared library

During the course of attempting to develop a ruby gem C extension, I came upon the following error trying to build a simple C library on a FreeBSD system: linking shared-object gdi.so /usr/bin/ld: /home/william/lib/libWinspool.a(winspool.o): relocation R_X86_64_PC32 against `memset@@FBSD_1.0' can

Re: autoconf check for building shared library

On Sat, 2 Apr 2016, Will Parsons wrote: I amm interested in an autoconf solution, not involving e.g., automake or libtool. You should be able to take advantage of macros from libtool without actually using libtool itself. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simpl

Re: Add clang++ to AC_PROG_CXX

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] The goal of Autoconf is to compile the program with whatever compilers are available.

Re: Add clang++ to AC_PROG_CXX

Richard Stallman wrote: The goal of Autoconf is to compile the program with whatever compilers are available. Yes, and the Autoconf patch I installed does that: it adds clang to the list of compilers to try. With a patched Autoconf, 'configure' tries gcc before clang. http://git.savannah.gnu