Problems upgrading GNUTLS 2.2.2 to 2.4.0 (SOLVED)
Doug Poland
doug at polands.org
Thu Jun 26 18:54:00 UTC 2008
Sean Cavanaugh wrote:
>
> > Date: Thu, 26 Jun 2008 10:55:08 -0500
> > From: doug at polands.org
> > To: schiz0phrenic21 at gmail.com
> > CC: questions at freebsd.org
> > Subject: Re: Problems upgrading GNUTLS 2.2.2 to 2.4.0
> >
> > Schiz0 wrote:
> > > On Thu, Jun 26, 2008 at 11:09 AM, Doug Poland <doug at polands.org> wrote:
> > >> Hello,
> > >>
> > >> I'm having issues upgrading GNUTLS 2.2.2 to 2.4.0. The box in
> questions is
> > >> running 7.0-STABLE i386.
> > >>
> > >> The error message I'm receiving is...
> > >>
> > >>
> > >> ===> Configuring for gnutls-2.4.0
> > >> aclocal.m4:16: warning: this file was generated for autoconf 2.62.
> > >> You have another version of autoconf. It may work, but is not
> guaranteed
> > >> to.
> > >> If you have problems, you may need to regenerate the build system
> entirely.
> > >> To do so, use the procedure documented by the package, typically
> > >> `autoreconf'.
> > >> configure.in:28: version mismatch. This is Automake 1.10,
> > >> configure.in:28: but the definition used by this AM_INIT_AUTOMAKE
> > >> configure.in:28: comes from Automake 1.10.1. You should recreate
> > >> configure.in:28: aclocal.m4 with aclocal and run automake again.
> > >> *** Error code 63
> > >>
> > >> Stop in /usr/ports/security/gnutls.
> > >>
> > >> I've installed devel/autoconf-2.62 but it makes no difference.
> I've googled
> > >> and tried lots of things to get autoconf to run but to no avail.
> > >>
> > >> Any suggestions are appreciated.
> > >>
> > >> --
> > >> Regards,
> > >> Doug
> > >
> > > This isn't a solution, just an issue I had too.
> > >
> > > When I upgraded from 2.2.5 to 2.4.0, I also got that message about a
> > > version mis-match for Automake. However, this did not stop the build
> > > process, and it installed successfully.
> > >
> > Interesting... I'm unable to continue the build process because of the
> > error code. How did you get around it?
> >
> > --
> > Regards,
> > Doug
>
> My best guess would be to upgrade your automake to a version that's at
> least 1.10.1 like the message says which so happens to be the version
> that's in ports right now. upgrading autoconf prob wouldn't be bad either.
>
Thanks, upgrading automake to 1.10.1 made everything alright.
--
Regards,
Doug
More information about the freebsd-questions
mailing list