On Fri 09 Jan 2004, Kim Woelders wrote:
> Ibukun Olumuyiwa wrote:
> >That said, I have been thinking of the need to do a cleanup act on the
> >autofoo in many of the modules to eliminate the warnings and complaints
> >usually output by autoconf 2.5x. For example, eliminating the use of
> >acconfig.
Michael Jennings wrote:
While I appreciate the patch, it does not remove the aforementioned
warning messages.
Odd.
This is what I get on RH-7.2 (autoconf-2.13):
$ ./autogen.sh
Generating configuration files for libast, please wait
+ libtoolize -c -f
Remember to add `AC_PROG_LIBTOOL' to `confi
On Friday, 09 January 2004, at 21:24:25 (+0100),
Kim Woelders wrote:
> Index: configure.in
> ===
> RCS file: /cvsroot/enlightenment/eterm/libast/configure.in,v
> retrieving revision 1.13
> diff -u -r1.13 configure.in
> --- configure.i
Michael Jennings wrote:
On Friday, 09 January 2004, at 20:14:33 (+0100),
Kim Woelders wrote:
In the e16 case above config.h.in is generated from configure.in without
any acconfig.h being involved.
I believe it does require that the third parameter to AC_DEFINE is used,
as in
AC_DEFINE(USE_IMLIB
On Friday, 09 January 2004, at 20:14:33 (+0100),
Kim Woelders wrote:
> In the e16 case above config.h.in is generated from configure.in without
> any acconfig.h being involved.
> I believe it does require that the third parameter to AC_DEFINE is used,
> as in
> AC_DEFINE(USE_IMLIB2, 1, [Imlib2
Michael Jennings wrote:
On Friday, 09 January 2004, at 19:40:56 (+0100),
Kim Woelders wrote:
Quoting config.h.in for e16 generated on RH-7.2 (auto{conf,header}-2.13):
"/* config.h.in. Generated automatically from configure.in by
autoheader. */"
In my experience, things that aren't in the def
On Friday, 09 January 2004, at 19:40:56 (+0100),
Kim Woelders wrote:
> Quoting config.h.in for e16 generated on RH-7.2 (auto{conf,header}-2.13):
>
> "/* config.h.in. Generated automatically from configure.in by
> autoheader. */"
In my experience, things that aren't in the default autoheader f
Michael Jennings wrote:
usually output by autoconf 2.5x. For example, eliminating the use
of acconfig.h, adding the description parameter to AC_DEFINEs
etc. It is
If acconfig.h is eliminated, what file will be used to generate
config.h.in?
Do not remove the acconfig.h or any other files needed by
> > usually output by autoconf 2.5x. For example, eliminating the use
> > of acconfig.h, adding the description parameter to AC_DEFINEs
> > etc. It is
If acconfig.h is eliminated, what file will be used to generate
config.h.in?
Do not remove the acconfig.h or any other files needed by autoconf
2.
Ibukun Olumuyiwa wrote:
That said, I have been thinking of the need to do a cleanup act on the
autofoo in many of the modules to eliminate the warnings and complaints
usually output by autoconf 2.5x. For example, eliminating the use of
acconfig.h, adding the description parameter to AC_DEFINEs etc.
On Sun 04 Jan 2004, Michael Jennings wrote:
> On Sunday, 04 January 2004, at 21:10:34 (-0500),
> Mike Frysinger wrote:
>
> > http://www.enlightenment.org/pages/cvsnotes.html
>
> 'autotools
> The best versions of the tools you need to build E and related software
> are as follows: autoconf 2.1
On Sunday, 04 January 2004, at 21:10:34 (-0500),
Mike Frysinger wrote:
> http://www.enlightenment.org/pages/cvsnotes.html
'autotools
The best versions of the tools you need to build E and related software
are as follows: autoconf 2.13, automake 1.4, libtool 1.4.2, gettext 0.10.38.
As far as
On Sunday 04 January 2004 20:52, Michael Jennings wrote:
> Where on earth did you get that idea?
http://www.enlightenment.org/pages/cvsnotes.html
in bold:
If you have problems building the source, the most common problems involve old
versions of the build tools.
Present versions recommended are G
On Sunday, 04 January 2004, at 20:25:05 (-0500),
Mike Frysinger wrote:
> i thought e was taking a stance that if it works with latest
> autotools you should update :)
Where on earth did you get that idea?
Type 'autotools on #E, say 3 Hail Raster's, and go to Confession.
Michael
--
Michael Jen
On Sunday 04 January 2004 20:20, Nathan Ingersoll wrote:
> This was a known issue on autoconf 2.13 and automake 1.4-p6. I committed
> a fix for this today. There didn't appear to be anything wrong with the
> checks that were causing problems, but the nesting of checks seemed to
> throw it for a loo
This was a known issue on autoconf 2.13 and automake 1.4-p6. I committed
a fix for this today. There didn't appear to be anything wrong with the
checks that were causing problems, but the nesting of checks seemed to
throw it for a loop. I flattened the checks and it apparently is
portable between v
On Sunday 04 January 2004 07:02, Ben Rockwood wrote:
> The lines for ECORE_TXT don't exist. Because of this the vars don't get
> chomped off, and when you look at the makefile for the TXT module you see:
what autotool versions you using to autogen ?
what configure flags are you using ?
here's wha
Looks like we're all lost on this one. I've found the problem but don't
know how to fix it
If you look in config.status you'll see a bunch of regex's which strip out
autof00 vars such that they aren't included later in the resultant
Makefile's.
These lines come from the configure script, whic
18 matches
Mail list logo
