Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
pon., 17 gru 2018 o 00:42 Alex McKeever napisał(a): > > 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 those a > while back (and personally I have been partial to Linux and how easily I can > just get software via APT or Zypper... I would be running Debian Sid if they > didn’t drop support for the eMac in terms of my internal display not working > after Jessie) FWIW, the x11/cde port is not just broken on MIPS and PowerPC; it's marked broken on FreeBSD 12 on all architectures. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
Hi people, (and thanks Alan for copying me in) On 2018-12-17 01:42, Mark Linimon wrote: 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 desktop ports are lagging way behind. For instance, we are still working to get gnome and kde working properly. Other desktop environments are going to require more people to take up working on them. I personally would like to see powerpc64 ports at (near-) parity with amd64, but we have a lot of work to go yet. I'm not sure if it's supported on PowerPC at all anyway by the developers (although obviously it used to work, perhaps not on FreeBSD though). Was it a straightforward error? Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 practice. That's interesting. Can you elaborate ? Is it the stability of the hardware itself ? Are the hardware offerings too diverse so that the boxes aren't compatible between each other ? Is the performance not sufficient to compete with amd64 ? Are there legal issues like intellectual property or such ? -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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, none of the offerings have been very good in practice. Except for Amazon which owns Annapurna every company I’ve spoken to is backing away from it. -M > -- > p...@freebsd.org +49 171 3101372 2 years to go ! > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 ! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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. (This is the equivalent of forcing an ignore of the BROKEN lines). Now, having said that ... over the past 2 weeks I've done a TRYBROKEN run over everything that is marked BROKEN on powerpc64. In the few cases where the port built, I deleted the line. So AFAIK all the ports marked BROKEN really don't build. I can provide logfiles to anyone who wants to do the debugging. Tangential to BROKEN is the makevar NOT_FOR/ONLY_FOR. This doesn't get overridden by TRYBROKEN. This setting is used to say "this port is not able to build on this architecture due to either missing code, lack of support for e.g. big-endian archs, and so forth." For those issues you may need to check with the port's upstream. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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". It's an overused trope (See all the "Netcraft confirms" memes). Yes, there are no new powerpc32 devices being produced, but there is still a lot of life left in old macs. Personally, I haven't been keeping up on powerpc32 for a while, but not much has happened in driver-land, and I've been focusing my 32-bit efforts on the Book-E world, which still does have some life to it, and will continue to exist for at least another 7 years due to NXP's product longevity program. Doesn't mean there will be new devices made around them, but they will continue to exist. Although the vast majority of powerpc effort as of late has been in the powerpc64 port, my Book-E efforts on the 32-bit side have been on the powerpcspe port. It's still 32-bit, and anything that would generally affect 32-bit will affect powerpcspe, so any bugs fixed for powerpcspe should fix general powerpc. We are bringing 64-bit package builders online in the FreeBSD cluster, and as you probably know, 64-bit powerpc can run 32-bit binaries just fine. So, when the builders are stable, we might add 32-bit jails as well to crank out packages. That said, don't expect that any time soon. 32-bit powerpc will never be Tier 1, and very well may go away in the next 10-15 years, but I will not claim to predict the future on it. powerpc64 is headed in the direction of Tier 1, but that's still a long crawl itself. Alex, if you find bugs, please file bug reports so they can at least be tracked. You can try to build the broken ports either by deleting the BROKEN line in the Makefile, or through some poudriere or make variable trickery (don't recall how in either case off-hand). That would let us at least know why it's broken. And, yes, I am generally considered the keeper of all things powerpc, and a strong advocate of such. I really should get my PowerMac G4, and PowerBooks (yes, plural) up to latest head, but have little time, so it becomes lower priority until needed. - Justin ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 dropped than to go Tier 1. Sorry. > Power8 is changing that. More $$$ going into making that work well. Maybe not to Tier 1, but not dying. Warner -Alan > > On Sun, Dec 16, 2018 at 5:42 PM Alex McKeever > wrote: > > > > 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 those a while back (and personally I have been partial to Linux and > how easily I can just get software via APT or Zypper... I would be running > Debian Sid if they didn’t drop support for the eMac in terms of my internal > display not working after Jessie) > > > > Sent from my iPad > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 platform other than amd64 to fully support modern graphics cards on FreeBSD. The limited volume of Raptor motherboards means that NRE costs are reflected in the board cost - so it will continue to be a niche solution, but it is definitely not going away any time soon. On Sun, Dec 16, 2018 at 5:32 PM Alan Somers wrote: > > 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 16, 2018 at 5:42 PM Alex McKeever > wrote: > > > > 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 those a while back (and personally I have been partial to Linux and > > how easily I can just get software via APT or Zypper... I would be running > > Debian Sid if they didn’t drop support for the eMac in terms of my internal > > display not working after Jessie) > > > > Sent from my iPad > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 desktop ports are lagging way behind. For instance, we are still working to get gnome and kde working properly. Other desktop environments are going to require more people to take up working on them. I personally would like to see powerpc64 ports at (near-) parity with amd64, but we have a lot of work to go yet. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 to go Tier 1. Sorry. Thank you for discouraging me and the other folks working on powerpc64. New systems with Power9 are being sold by a company called Raptor Systems in Round Rock, Texas. Several developers have them, and others (including me) have them on order. I have been working on bringing powerpc64 ports up to parity for quite some time. If you are not aware of the effort that myself, and many others, have been putting in, then you are obviously not reading the svnports@ list, and should not be speaking as an authority. src work on supporting P8 and P9 is also in very active development. Please try to keep up with the development situation for a plaform before posting about it. Frankly, I find your post insulting. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 16, 2018 at 5:42 PM Alex McKeever wrote: > > 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 those a > while back (and personally I have been partial to Linux and how easily I can > just get software via APT or Zypper... I would be running Debian Sid if they > didn’t drop support for the eMac in terms of my internal display not working > after Jessie) > > Sent from my iPad > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
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 those a while back (and personally I have been partial to Linux and how easily I can just get software via APT or Zypper... I would be running Debian Sid if they didn’t drop support for the eMac in terms of my internal display not working after Jessie) Sent from my iPad ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
