Upgrading autoconf

Odhiambo Washington odhiambo at gmail.com
Fri Oct 1 12:02:45 UTC 2010


On Fri, Oct 1, 2010 at 12:36 PM, Daniel Bye <
freebsd-questions at slightlystrange.org> wrote:

> On Fri, Oct 01, 2010 at 12:13:28PM +0300, Odhiambo Washington wrote:
> > On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye <
> > freebsd-questions at 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:-)
>
> Glad you fixed it!
>
> > Will migrate it to 8.x soon, by doing a new installation and migrating.
> >
> > Or should I wait for FreeBSD-9 ??
>
> I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for
> production, and when it is released, it should be pretty straight forward
> to
> upgrade from 8.x using the standard buildworld cycle, provided your setup
> isn't too outlandish!
>
>
Update 6.4 to 8.x??  Or you mean some upgrade path like install 8.x and then
migrate services?:-)


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"If you have nothing good to say about someone, just shut up!."
               -- Lucky Dube


More information about the freebsd-questions mailing list