Date: Fri, 1 Oct 2010 12:13:28 +0300 From: Odhiambo Washington <odhiambo@gmail.com> To: Daniel Bye <freebsd-questions@slightlystrange.org>, User Questions <freebsd-questions@freebsd.org> Subject: Re: Upgrading autoconf Message-ID: <AANLkTin1x_i6UCYjAD=WuDTAgOutaOwsgF0gSzSN4wY%2B@mail.gmail.com> In-Reply-To: <20100930155915.GA26665@catflap.slightlystrange.org> References: <AANLkTimz%2B-iD8WwH2eE2KkL=7nCvJCcs%2B=G-opfW0k4m@mail.gmail.com> <20100930155915.GA26665@catflap.slightlystrange.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye <
freebsd-questions@slightlystrange.org> wrote:
> On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote:
> > I am trying this out:
> >
> > #portupgrade -f 'autoconf*' 'automake*'
>
> Try upgrading the failing ports by hand. portupgrade tends to suppress full
> error output, making it difficult to ascertain exactly what's gone wrong.
>
> Alternatively, I would be tempted to just uninstall autoconf* and
> automake*,
> since they will get pulled in as dependencies whenever you come to build
> another port that requires them.
>
>
Hi Dan,
Turns out the culprit was m4. Once I did 'portupgrade m4' successfully,
everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I
was ashamed to mention:-)
Will migrate it to 8.x soon, by doing a new installation and migrating.
Or should I wait for FreeBSD-9 ??
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"If you have nothing good to say about someone, just shut up!."
-- Lucky Dube
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin1x_i6UCYjAD=WuDTAgOutaOwsgF0gSzSN4wY%2B>