Hello,
I have two related programs (tuxmath and tuxtype) that share a lot of
code in a human-maintained, copy-and-past fashion. We have been
working on moving the overlapping code into a separate library
package, libt4kcommon. All the programs use Autoconf, Automake, and
Gettext where needed.
Hello,
On Mon, Dec 28, 2009 at 3:22 AM, Alberto Luaces alua...@udc.es wrote:
David Bruce writes:
Hello,
I have two related programs (tuxmath and tuxtype) that share a lot of
code in a human-maintained, copy-and-past fashion. We have been
working on moving the overlapping code into a
David Bruce writes:
OK, I can get it to work post-installation with either LD_LIBRARY_PATH
or the ldconfig+/etc/ld.so.conf mechanism. What I want to learn is
the right way to do this as a programmer/packager from an autotools
perspective so that a user can do ./configure; make; sudo make
Hey,
When passing -pthread to my_lib_LDFLAGS and my_lib_CFLAGS in Makefile.am,
on OpenBSD (libtool 1.5.26), the linker does not have -lpthread, but just
-pthread :
gcc -shared -fPIC -DPIC
-o .libs/libeina-ver-pre-svn-05.so.9.9 .libs/libeina_la-eina_error.o
.libs/libeina_la-eina_log.o
On Mon, 28 Dec 2009, Vincent Torri wrote:
When passing -pthread to my_lib_LDFLAGS and my_lib_CFLAGS in Makefile.am, on
OpenBSD (libtool 1.5.26), the linker does not have -lpthread, but just
-pthread :
Is -pthread not sufficient to do everything needed? Notice that this
is GCC and not just
On Mon, 28 Dec 2009, Bob Friesenhahn wrote:
On Mon, 28 Dec 2009, Vincent Torri wrote:
When passing -pthread to my_lib_LDFLAGS and my_lib_CFLAGS in Makefile.am,
on OpenBSD (libtool 1.5.26), the linker does not have -lpthread, but just
-pthread :
Is -pthread not sufficient to do
