In the autoconf manual, there is a list of a recommended order of operations:
Autoconf requirements
AC_INIT(package, version, bug-report-address)
information on the package
checks for programs
checks for libraries
checks for header files
checks for types
che
NightStrike <[EMAIL PROTECTED]> writes:
> If I do this:
>
> AC_CHECK_FUNC(
> [chokeme],
> [],
> []
> )
The else part is not empty, it consists of explicit whitespace. When
collecting arguments only unquoted leading whitespace is skipped by m4,
trailing whitespace (quoted or not) is preserv
On 3/8/08, Andreas Schwab <[EMAIL PROTECTED]> wrote:
> NightStrike <[EMAIL PROTECTED]> writes:
>
> > If I do this:
> >
> > AC_CHECK_FUNC(
> > [chokeme],
> > [],
> > []
> > )
>
> The else part is not empty, it consists of explicit whitespace. When
> collecting arguments only unquoted leading
NightStrike <[EMAIL PROTECTED]> writes:
> On 3/8/08, Andreas Schwab <[EMAIL PROTECTED]> wrote:
>> NightStrike <[EMAIL PROTECTED]> writes:
>>
>> > If I do this:
>> >
>> > AC_CHECK_FUNC(
>> > [chokeme],
>> > [],
>> > []
>> > )
>>
>> The else part is not empty, it consists of explicit whitespac
Hello,
* NightStrike wrote on Sat, Mar 08, 2008 at 09:01:54AM CET:
> In the autoconf manual, there is a list of a recommended order of operations:
>
> Autoconf requirements
> AC_INIT(package, version, bug-report-address)
> information on the package
> checks for programs
>
Hi,
I need to use complex functions from a fortran library in a c/c++ code.
As I have seen there are two calling conventions for complex functions.
g77 used the following calling convention.
Functions that return type default REAL actually return the C type
double, and functions that return type
Hello,
I have a *very* obscure autoconf problem. It first surfaced trying to
build the alpha releases of Python 3.0. However it also shows up with
the Python 2.5.2 sources, and some other tarballs I happened to have
handy that depend on autoconf.
The system in question is FreeBSD 6.2-STABLE, alth
