"portmaster -o" behaves a little strangely (IMHO)

Conrad J. Sabatier conrads at cox.net
Tue Jan 24 21:19:10 UTC 2012

On Tue, 24 Jan 2012 12:31:54 -0800
Doug Barton <dougb at freebsd.org> wrote:

> On 01/24/2012 06:19, Conrad J. Sabatier wrote:
> > ===>>> Gathering dependency list for lang/gcc46 from ports
> > ===>>> Launching child to update gcc- to
> > gcc-
> >         lang/gcc46 >> gcc-
> > 
> > (What is the preceding line -- with the ">>" -- and the similar one
> > below, supposed to be indicating exactly?  If it means what I think
> > it does, then it seems as if portmaster is misinterpreting the
> > intention of the "-o" option)
> No, it means that the ports framework is seeing 4.4 as a dependency of
> 4.6 for some reason. I've seen that happen in the past when non-base
> gcc was in use, but have never had anyone track down the cause
> authoritatively. Obviously make.conf is a suspect, but I'm assuming
> you already looked there.
> What you probably have to do is pkg_delete -f 4.4, then do the same
> portmaster -o command but with 'lang/gcc44' as the second argument.

Yes, using origin designators in both places worked.  Is this an
unwritten requirement in the case of the -o option?

Anyway, moving merrily along...  :-)


Conrad J. Sabatier
conrads at cox.net

More information about the freebsd-ports mailing list