Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Kurt Jaeger
Hi! > > > PPC64 with the advent of Power9 is the only real alternative platform > > > to amd64 in the data center [...] > > I'm curious, isn't arm64 also a contender in this market ? > Supposedly. The FF has invested in it greatly. Nonetheless, none of the > offerings have been very good in

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Matthew Macy
On Sun, Dec 16, 2018 at 23:10 Kurt Jaeger wrote: > Hi! > > > PPC64 with the advent of Power9 is the only real alternative platform > > to amd64 in the data center [...] > > I'm curious, isn't arm64 also a contender in this market ? > Supposedly. The FF has invested in it greatly. Nonetheless,

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Kurt Jaeger
Hi! > PPC64 with the advent of Power9 is the only real alternative platform > to amd64 in the data center [...] I'm curious, isn't arm64 also a contender in this market ? -- p...@freebsd.org +49 171 3101372 2 years to go ! ___

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Mark Linimon
On Sun, Dec 16, 2018 at 08:21:14PM -0600, Justin Hibbits wrote: > You can try to build the broken ports either by deleting the BROKEN > line in the Makefile True, but see below ... > or through some poudriere trickery -T Try building BROKEN ports by defining TRYBROKEN for the build.

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Justin Hibbits
On Mon, 17 Dec 2018 01:54:22 + Mark Linimon wrote: > If we are talking powerpc32 and not powerpc64 (as I assumed), the one > developer continuing to actively work on it is jhibbits@. Perhaps he > can give you a status report. > > mcl I really wish people would stop saying "XXX is dying".

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Warner Losh
On Sun, Dec 16, 2018, 6:33 PM Alan Somers CC the package maintainer. > > As for powerpc on tier 1, I'm afraid that it's not likely to ever > happen. Powerpc is dying. If anybody were buying new ppc hardware, > then it would be a different story. But I predict that powerpc is > likely to be

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Mark Linimon
If we are talking powerpc32 and not powerpc64 (as I assumed), the one developer continuing to actively work on it is jhibbits@. Perhaps he can give you a status report. mcl ___ freebsd-stable@freebsd.org mailing list

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Matthew Macy
Let's speak with a bit more precision. PowerPC (32-bit), with only a lingering handful of embedded uses is "dying" and is only marginally more relevant than the likes of sparc64. PPC64 with the advent of Power9 is the only real alternative platform to amd64 in the data center and the only

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Mark Linimon
On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote: > I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) > on my eMac. I don't know of anyone else who has tried to run it. The server-class ports on powerpc64 have been in good shape for several years. However, the

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Mark Linimon
On Sun, Dec 16, 2018 at 06:12:35PM -0700, Alan Somers wrote: > As for powerpc on tier 1, I'm afraid that it's not likely to ever > happen. Powerpc is dying. If anybody were buying new ppc hardware, > then it would be a different story. But I predict that powerpc is > likely to be dropped than

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Alan Somers
CC the package maintainer. As for powerpc on tier 1, I'm afraid that it's not likely to ever happen. Powerpc is dying. If anybody were buying new ppc hardware, then it would be a different story. But I predict that powerpc is likely to be dropped than to go Tier 1. Sorry. -Alan On Sun, Dec

fist impressions of 12.0R

2018-12-16 Thread Lucas Nali de Magalhães
Hi everyone, I think I found a bug… it's on a desktop system I keep on the last version and it's going from 11.2 to 12.0. The resume is: # freebsd-update upgrade -r 12.0-RELEASE (…) Does this look reasonable (y/n)? n # A re-start wasn't what I expected. The program let me edit a file and

Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

2018-12-16 Thread Alex McKeever
I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) on my eMac. It says it is broken and cannot be compiled. Also, any ETA on when this port of the OS will go into Tier 1? Compiling software, desktop environments, X11, using 11.1 and the now unsupported 10.4 failed when I tried

Problem reports for sta...@freebsd.org that need special attention

2018-12-16 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Re: HEADS UP: TCP CUBIC Broken on 12.0-RELEASE/STABLE

2018-12-16 Thread Matt Garber
On Sun, Dec 16, 2018 at 11:44 AM Kurt Jaeger wrote: > Will CUBIC be used if the system is running 12.0, or does it only happen > if one actively configures the use of the algorithm ? > > Can the use be detected somehow ? > This only happens if someone explicitly configured the use of the

HEADS UP: TCP CUBIC Broken on 12.0-RELEASE/STABLE

2018-12-16 Thread Matt Garber
Hi all: Just a heads-up for those beginning to test or use FreeBSD 12.0-RELEASE or 12/STABLE, the alternate TCP congestion control algorithm CUBIC (cc_cubic) is currently broken and causes complete stalls of certain network traffic (e.g., rsync, git checkouts, etc.), as well as what appears to