Hi all,
I am finding that the use of AC_LANG_SOURCE() is having different
results on autoconf 2.64 vs. 2.59. On 2.59 it seems to have been
including confdefs.h into generate programs but in 2.64 this seems to no
longer be the case.
To illustrate more clearly, on 2.59:
[AC_LANG_SOURCE([LB_LANG_P
On Thu, 2010-02-25 at 16:09 -0500, NightStrike wrote:
> How about those two minor things I pointed out? :)
And the confdefs.h issue I pointed out a week or two ago.
In fact I've been meaning to ask how I should work around that problem
for people who are using releases with that bug in it.
Any
On Sun, 2010-02-28 at 10:25 +0100, Ralf Wildenhues wrote:
> * Ralf Wildenhues wrote on Sat, Feb 20, 2010 at 10:57:04AM CET:
> > * Brian J. Murrell wrote on Thu, Feb 18, 2010 at 07:15:08PM CET:
> > > I am finding that the use of AC_LANG_SOURCE() is having different
> > &g
On Tue, 2010-03-02 at 07:00 +0100, Ralf Wildenhues wrote:
> When you have fixed the issue (as described in the other mail)
> and then can reproduce your bug, please also try adding
>AC_PROG_CC
Sure.
> to your configure.ac before the use of LB_LINUX_COMPILE_IFELSE
> and see whether your probl
On Tue, 2010-03-02 at 22:35 +0100, Ralf Wildenhues wrote:
>
> So you use Autoconf's AC_LANG_SOURCE but your own version of
> AC_LANG_CONFTEST,
Yes, it would seem so. You will have to excuse my lack of decisiveness
on this. I am more-or-less just getting to the party. :-)
> and the fact that
On Tue, 2010-03-02 at 15:48 -0700, Eric Blake wrote:
> The change was made back on 2008-11-03 (commit 8e27cc7f5, contained in
> autoconf 2.63b), so although it is somewhat of a regression
> (AC_LANG_CONFTEST outputs defines now, when it did not do so previously),
> there obviously aren't that many
We are seeing the following in trying to build our package(s) with some
versions of autoconf/automake:
libcfs/libcfs/autoMakefile.am:88: variable `DIST_SOURCES' is defined but no
program or
libcfs/libcfs/autoMakefile.am:88: library has `DIST' as canonic name (possible
typo)
lnet/klnds/ciblnd/aut
