Dean Povey wrote:
>
[snip]
> >Maybe I am the one now who is totally not getting it, but:
> >
> >How could you distribute a binary to run on all the different kinds of
> >systems? I use Cygwin and MinGW. Am I going to be excluded from Open
> >Source packages because the package maintainer decided
Dean Povey wrote:
> The easiest way would be for ./configure to find the C compiler and build
> a simple utility binary from source, then use that for the rest of the
> configuration.
Problem is that by the time you've figured out how to do that,
you're most the way done. Now, if you depended u
On Tue, 15 Oct 2002 05:38:49 +1000
Dean Povey <[EMAIL PROTECTED]> wrote:
> >How could you distribute a binary to run on all the different kinds of
> >systems? I use Cygwin and MinGW. Am I going to be excluded from Open
> >Source packages because the package maintainer decided not to provide
> >su
>>> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
[...]
Paul> noinst_PROGRAMS = loadavg
Paul> nodist_loadavg_SOURCES = loadavg.c
Paul> loadavg_CFLAGS = -DTEST
Paul> loadavg_LDADD = @GETLOADAVG_LIBS@
Paul> loadavg.c: $(srcdir)/getloadavg.c
Paul> cp $(srcdir)/getloadavg.c loada
Hi all; I'm using automake 1.7 (with autoconf 2.54 and gettext 0.11.5).
I'm trying to add ansi2knr support so I can use ANSI function
definitions in GNU make.
I have special code to test the getloadavg.c, which builds a test
program using that code. The test program is embedded in the file, and
>> (im not an expert on autotools and this may sound simplistic, but
>> FWIW) Ive often wondered why ./configure has to be a script, i
>> understand it has to be portable, but couldnt the build tools compile
>> a binary that calls on a c library that provides most of the
>> functionality.
>
>Mayb
