alright, this is getting downright retarded...
Joe Rhett
jrhett at isite.net
Sat Nov 22 22:16:25 CET 2003
> But you you use automake daily?
Perhaps not every day, but many times per week. As I said, we use autoconf
for management scripts in our own productions.
(not very well, IMHO, but we do use it)
> It looks to me like there is a breakage in the linkage between autoconf
> and automake. I will look some more later, but that is my first
> impression.
Clue me in and I'll look around.
> You neglected to mention what OS you are running, but I think that is
> not the issue.
Whoops, sorry. Solaris 8, x86, AMD Althon XP+; current on patches
--message history quoted below:
On Fri, Nov 21, 2003 at 07:45:50PM -0500, Karl DeBisschop wrote:
> On Fri, 2003-11-21 at 15:57, Joe Rhett wrote:
> > > > Well, automake-1.6 and autoconf-2.58 pukes all over these files as well.
> > > > Please someone tell me you're halfway through a commit?
> > >
> > > Hmmm. I'm running automake 1.78 and autoconf 2.57 (on Fedora Core 1), no
> > > problems here.
> >
> > I just upgraded to the latest, I was about one version before yours, now
> > I'm at 1.79 and 2.58 just like you mentioned in your followup message.
> >
> > > > I'm more than willing to spend time and effort hacking away on this, but
> > > > the development environment needs to be even halfway capable of providing a
> > > > build.
> > >
> > > I guess the first thing that would help is to find out why the gnu tool
> > > chain is failing for you. Can you be more specific than "pukes"
> >
> > cyclops 490% aclocal
> > aclocal: configure.in: 1406: macro `AM_GNU_GETTEXT_VERSION' not found in library
> > aclocal: configure.in: 1407: macro `AM_GNU_GETTEXT' not found in library
> >
> > cyclops 490% autoconf
> > configure.in:6: error: possibly undefined macro: AM_INIT_AUTOMAKE
> > If this token and others are legitimate, please use m4_pattern_allow.
> > See the Autoconf documentation.
> > configure.in:1406: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
> > configure.in:1407: error: possibly undefined macro: AM_GNU_GETTEXT
> >
> > cyclops 491% autoheader
> >
> > cyclops 492% automake
> > configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
> > configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
> > configure.in: that aclocal.m4 is present in the top-level directory,
> > configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
> > configure.in: required file `./install-sh' not found
> > configure.in: required file `./mkinstalldirs' not found
> > configure.in: required file `./missing' not found
> > configure.in:8: required file `./config.guess' not found
> > configure.in:8: required file `./config.sub' not found
> > Makefile.am: required file `./INSTALL' not found
> > lib/Makefile.am: required file `./depcomp' not found
> > /opt/gnu/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
> > /opt/gnu/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
> > /opt/gnu/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
> > /opt/gnu/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
> >
> >
> > Just FYI, we use autoconf for our internal code and I use it daily for
> > various other projects we're tracking via CVS. There are no system problems
> > with autoconf that I'm aware of, and we do use it daily.
>
> But you you use automake daily?
>
> It looks to me like there is a breakage in the linkage between autoconf
> and automake. I will look some more later, but that is my first
> impression.
>
> You neglected to mention what OS you are running, but I think that is
> not the issue.
>
> --
> Karl
--
Joe Rhett Chief Geek
JRhett at Isite.Net Isite Services, Inc.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
More information about the Developers
mailing list