Le 26/05/2013 21:54, Lowell Gilbert a écrit :
> Beeblebrox writes:
>
>> Sorry, my bad - port is part of marcuscom-gnome3 apparently. I have had so
>> many port-build fails (consistently over a long period) that a neglected to
>> check the port origin.
>> Will report issue to marcuscom-gnome3
>
>
Beeblebrox writes:
> Sorry, my bad - port is part of marcuscom-gnome3 apparently. I have had so
> many port-build fails (consistently over a long period) that a neglected to
> check the port origin.
> Will report issue to marcuscom-gnome3
You have been issuing a *lot* of e-mails to the ports lis
marcuscom.gnome3 &
xorg.devel
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/x11-toolkits-mx-build-fail-tp5815213p5815227.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
Beeblebrox writes:
> port fails to build in poudriere and on host with exact same output.
That port doesn't currently exist, as far as I can see.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To uns
-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 &
xorg.devel
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/x11-toolkits-mx-build-fail-tp5815213.html
Sent from the freebsd-ports mailing list archive at Nabble
