Date: Sun, 04 Nov 2007 13:54:04 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Christian Baer <christian.baer@uni-dortmund.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: Doesn't anything work around here? Message-ID: <472DC0EC.3070904@FreeBSD.org> In-Reply-To: <fgkadp$185e$5@nermal.rz1.convenimus.net> References: <ffg2gk$1n1r$1@nermal.rz1.convenimus.net> <200711011822.25884.linimon@lonesome.com> <fgk8ug$185e$3@nermal.rz1.convenimus.net> <472DACD7.6040501@FreeBSD.org> <fgkadp$185e$5@nermal.rz1.convenimus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Baer wrote: > On Sun, 04 Nov 2007 12:28:23 +0100 Kris Kennaway wrote: > >> ^^^^^ >>> Someone is working on FreeBSD/sparc32? >> FreeBSD does not support 32-bit sparc and it is unlikely it ever will. > > That's why I was a little shocked about the Sun4v. Was that a typo? No, sun4v is the latest sparc architecture. It is very much 64 bit ;) >>> I'm just wondering how two really common apps that have been broken for >>> quite a while now could just slip through the grid. >> Few people use sparc64 on their desktop. That means that if you want to >> do that you are running without the benefit of a large testing >> community, and you will have to shoulder part of that burden yourself. > > That would be fine with me. So I wasn't complaining about the ports > themselves being broken or even that noone had noticed Keepassx being > broken (although that doesn't even build on my machine). > > When I couldn't get Firefox and Thunderbird to run I googled around a bit > to find a solution. All I found out was that the broken port was known for > more than a year now. It wasn't a problem that nobody actually fixed it (I > know the sparc64 community on FreeBSD is still quite small) but that > nobody had marked the ports as broken. My complaint was actually that just > about everybody had to find out by themselves that these ports are broken. > I was annoying enough for me with a U60 with 450MHz CPUs. I wonder how > long it would have taken someone with a much slower machine to "find out". It has been broken and fixed many times over history. That is what I meant by "fragile", i.e. when someone fixes it in one version, later versions tend to become broken again. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?472DC0EC.3070904>