I have 2 modules, each with their own _init and _fini functions. My
Makefile.am file is as follows:
lib_LTLIBRARIES = dns.la select.la
dns_la_SOURCES = dns.c
dns_la_LDFLAGS = -module $(LDFLAGS)
select_la_SOURCES = select.c
select_la_LDFLAGS = -module $(LDFLAGS)
After running automake, autoconf, e
From: "Dr. David Kirkby" <[EMAIL PROTECTED]>
If the developers insist on dropping backward compatibility, would it
not be better to at least do a test for old hardware/software (i.e.
determine a machine is running SunOs 4.1.4), print an informative
error message then exit, rather than produce the
Thank you for your interest in the Handspring Foundation. Currently, we are not
accepting new applications/proposals for our Cash Grants Program at this time.
However, submissions for our Product Donation Program will continue to be accepted and
reviewed.Beginning with the November 1, 200
Raphaël Poss <[EMAIL PROTECTED]> writes:
> Here is a minimal configure.ac:
[...]
>
> autoreconf -v -f -i => ok
> ./configure =>
> configure: error: cannot find install-sh or install.sh in . ./.
Versions: ac 2.57, am 1.7.2
This works:
---8<---
AC_INIT(tools, 0.1)
AC_CONFIG_HEADER(config.h)
AC_O
Hi all,
I have a small touble with libtool 1.4.2 and automake 1.6 on my RH 8.0
box. Everything I use is installed from vanilla packages.
I noticed a couple of people complaining about ltmain.sh is not added to
required files (a warning is issued). As I looked into the automake
command source,
Roger Leigh wrote:
> Even in the case of GCC, why can't you build, say, 2.7.2, and then
> bootstrap 2.95.x and then 3.2.x in succession? As long as there's an
> "upgrade path", there's no need for the current toolchain to be fully
> backward-compatible with every system out there.
Whether or not
