On Tue, Jan 08, 2008 at 08:03:01PM -0800, Stephen Hurd wrote:
> Marius Strobl wrote:
> >FYI, it's fixed by the following commit:
> >http://docs.freebsd.org/cgi/mid.cgi?200711051136.lA5BaHpL069527
> >
> >Marius
>
> Looks like a low chance of it making it into 7.0-RELEASE?
No, it actually got appro
Marius Strobl wrote:
FYI, it's fixed by the following commit:
http://docs.freebsd.org/cgi/mid.cgi?200711051136.lA5BaHpL069527
Marius
Looks like a low chance of it making it into 7.0-RELEASE?
___
freebsd-ports@freebsd.org mailing list
http://lists.fre
On Mon, Jan 07, 2008 at 11:44:18PM +0100, Marius Strobl wrote:
> On Sat, Jan 05, 2008 at 12:57:27PM -0800, Stephen Hurd wrote:
> > Mark Linimon wrote:
> > >On Wed, Jan 02, 2008 at 05:10:56PM -0600, Mark Linimon wrote:
> > >
> > >>Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on
On Sat, Jan 05, 2008 at 12:57:27PM -0800, Stephen Hurd wrote:
> Mark Linimon wrote:
> >On Wed, Jan 02, 2008 at 05:10:56PM -0600, Mark Linimon wrote:
> >
> >>Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
> >>we are with respect to sparc64 packages, from portmgr's perspe
On Sat, Jan 05, 2008 at 12:57:27PM -0800, Stephen Hurd wrote:
> In debugging it though, it seems that gdb doesn't support thread debugging
> on sparc64 which is causing some problems... is this due to the lack of
> TLS?
Nope.
___
freebsd-ports@freebsd.
Mark Linimon wrote:
On Wed, Jan 02, 2008 at 05:10:56PM -0600, Mark Linimon wrote:
Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
we are with respect to sparc64 packages, from portmgr's perspective.
I have updated the charts and detailed-list pages on portsmon
On Wed, Jan 02, 2008 at 05:10:56PM -0600, Mark Linimon wrote:
> Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
> we are with respect to sparc64 packages, from portmgr's perspective.
I have updated the charts and detailed-list pages on portsmon with the
latest information
Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
we are with respect to sparc64 packages, from portmgr's perspective.
Quick summary: we're far behind where we are on i386. In particular, we
can't build KDE anywhere at the moment, which affects the release package
set. We
