On Tue, 2005-11-29 at 09:11 -0700, Ed Hartnett wrote:
Howdy all!
I believe the common consensus is that one should not set CFLAGS in
configure.ac.
However, I have a problem that seems to call for it. Is there a better
way to get this working then messing with CFLAGS?
My configure
On Thursday 01 December 2005 6:40 am, Roesner Thomas wrote:
thank you for the replie, make DESTDIR=`pwd` install works fine, but i´d
like to omit the naming of the installpath in all commands. I´d prefer
setting it within the configure.in or Makefile.am.
You _could_ just say `prefix=', in
On Thu, 1 Dec 2005, Brian Lloyd wrote:
Try this.
saved_CFLAGS=$CFLAGS
CFLAGS=$CFLAGS -I$(HDF5DIR)/include -L$(HDF5DIR)/lib
AC_CHECK_LIB([hdf5], [H5Fflush], [], [nc_hdf5_lib_missing=yes])
CFLAGS=$saved_CFLAGS
This gives the needed CFLAGS for the CHECK_LIB function, but leaves the
CFLAGS
Brian Lloyd [EMAIL PROTECTED] writes:
Try this.
saved_CFLAGS=$CFLAGS
CFLAGS=$CFLAGS -I$(HDF5DIR)/include -L$(HDF5DIR)/lib
AC_CHECK_LIB([hdf5], [H5Fflush], [], [nc_hdf5_lib_missing=yes])
CFLAGS=$saved_CFLAGS
This gives the needed CFLAGS for the CHECK_LIB function, but leaves the
CFLAGS
This one is the reason for a subtle CVS Libtool testsuite failure..
With ash-0.3.8, OpenBSD 3.8 'sh' and 'ksh' PD KSH v5.2.14 99/07/13.2,
I get
$ false; eval 'foo=$?'; echo $foo
0
Is this a shell bug, or am I doing something wrong?
If bug, where should I report it?
If not, is this behavior
I submit that anything that causes somebody familiar with the
framework or that causes more than 2 or 3 newbies problems should be
documented.
H
--
This one is the reason for a subtle CVS Libtool testsuite failure..
With ash-0.3.8, OpenBSD 3.8 'sh' and 'ksh' PD KSH v5.2.14 99/07/13.2,
I get
I've seen conflicting advice about how to handle extra macros, whether
developed locally or from the archive. What's the best way to get them
into configure? I think this reduces to the question of how to make
aclocal aware of them.
1. AC_CONFIG_MACRO_DIR doesn't work, according to prior posts
RB == Ross Boylan [EMAIL PROTECTED] writes:
RB 5. The autoconf manual has no index entry for aclocal. There is one for
RB aclocal.m4, and the text refers to aclocal. Is aclocal deprecated?
aclocal is part of Automake, not autoconf. The Automake manual
documents aclocal and explains how to
On Thu, 2005-12-01 at 21:38 +0100, Alexandre Duret-Lutz wrote:
RB == Ross Boylan [EMAIL PROTECTED] writes:
RB 5. The autoconf manual has no index entry for aclocal. There is one for
RB aclocal.m4, and the text refers to aclocal. Is aclocal deprecated?
aclocal is part of Automake, not
Ralf Wildenhues [EMAIL PROTECTED] writes:
is this behavior considered common knowledge or should it be
mentioned in the Autoconf shell portability section?
The latter, I think. I installed this:
2005-12-01 Paul Eggert [EMAIL PROTECTED]
* doc/autoconf.texi (Shellology): Document
A further thought:
On Thursday 01 December 2005 1:54 pm, I wrote:
On Thursday 01 December 2005 6:40 am, Roesner Thomas wrote:
thank you for the replie, make DESTDIR=`pwd` install works fine, but
i´d like to omit the naming of the installpath in all commands. I´d
prefer setting it within
On Thursday 01 December 2005 9:10 pm, Ross Boylan wrote:
On Thu, 2005-12-01 at 21:38 +0100, Alexandre Duret-Lutz wrote:
RB == Ross Boylan [EMAIL PROTECTED] writes:
RB 5. The autoconf manual has no index entry for aclocal. There is one
for RB aclocal.m4, and the text refers to aclocal.
Patrick Welche [EMAIL PROTECTED] writes:
Isn't the long term goal aclocal must be subsumed into autoconf? What
is preventing this from happening sooner rather than later?
I never really understood why one would want to use aclocal rather than
m4_include with separate .m4 files unless one was
On Thu, 2005-12-01 at 09:33 -0600, Bob Friesenhahn wrote:
On Thu, 1 Dec 2005, Brian Lloyd wrote:
Try this.
saved_CFLAGS=$CFLAGS
CFLAGS=$CFLAGS -I$(HDF5DIR)/include -L$(HDF5DIR)/lib
AC_CHECK_LIB([hdf5], [H5Fflush], [], [nc_hdf5_lib_missing=yes])
CFLAGS=$saved_CFLAGS
This gives
Ralf Wildenhues dixit:
This one is the reason for a subtle CVS Libtool testsuite failure..
With ash-0.3.8, OpenBSD 3.8 'sh' and 'ksh' PD KSH v5.2.14 99/07/13.2,
ash-based MirBSD #8 sh and pdksh-based mksh R26 too:
[EMAIL PROTECTED]:/home/tg $ /bin/sh -c 'false; eval 'foo=$?'; echo $foo'
0
On Thu, Dec 01, 2005 at 08:43:31PM +0100, Ralf Wildenhues wrote:
With ash-0.3.8, OpenBSD 3.8 'sh' and 'ksh' PD KSH v5.2.14 99/07/13.2,
I get
$ false; eval 'foo=$?'; echo $foo
0
Is this a shell bug, or am I doing something wrong?
If POSIX mode is enabled by using `set -o posix' or setting
On Thu, 1 Dec 2005, Matthias Kilian wrote:
On Thu, Dec 01, 2005 at 08:43:31PM +0100, Ralf Wildenhues wrote:
With ash-0.3.8, OpenBSD 3.8 'sh' and 'ksh' PD KSH v5.2.14 99/07/13.2,
I get
$ false; eval 'foo=$?'; echo $foo
0
Is this a shell bug, or am I doing something wrong?
If
17 matches
Mail list logo
