Hi ,
I create shared library, so I had to put AC_PROG_LIBTOOL macro call in
configure.in.
The result is that configure script makes some strange and unnecessary (at
least for me ;) ) checks now, e.g:
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
che
On Fri, 15 Oct 2004, Adam Dyga wrote:
I create shared library, so I had to put AC_PROG_LIBTOOL macro call in
configure.in.
The result is that configure script makes some strange and unnecessary (at
least for me ;) ) checks now, e.g:
checking for g77... no
checking for f77... no
checking for xlf...
On Friday 15 October 2004 14:00, Bob Friesenhahn wrote:
> On Fri, 15 Oct 2004, Adam Dyga wrote:
> > I create shared library, so I had to put AC_PROG_LIBTOOL macro call in
> > configure.in.
> > The result is that configure script makes some strange and unnecessary
> > (at least for me ;) ) checks no
On Fri, 15 Oct 2004, Adam Dyga wrote:
That's strange because other C++ libraries (I've tested some - libds for
example) use AC_PROG_LIBTOOL macro call too and configure doesn't make those
strange checks later.
Some packages include a libtool which has been patched to only test
the languages the pa
> It should not: the architecture is made for these tests to be
> implementable independently of the language.
Currently, if I'm not wrong AC_CHECK_SIZEOF checks for C, as it
uses _AC_COMPUTE_INT([(long int) (sizeof ($1))].
This wont work for fortran and even less in a fortran only environment.
> Dive into fortran.m4 and complete the missing bits.
I was planning on doing something similar for endianess detection, but
using the C code seems superior in most cases as it should work for
cross compilation. Will it be usefull to have a fortran only macro in
that case ?
Pat
__
Hi,
In the attached file there is a macro which could be used to test if a
backslash escapes characters, the test being the escape of '.
Pat
# _AC_PROG_FC_BACKSLASH_ESCAPE
# -
#
# Find if a backslash `\' escapes in quoted strings.
AC_DEFUN([_AC_PROG_FC_BACKSLASH_
$>./configure
func_success failed.
func_success failed.
No shell found that supports shell functions.
Please tell [EMAIL PROTECTED] about your system,
including any error possibly output before this
message
checking for a BSD-compatible install... /usr/bin/install -c
... (then works normally)
Syst