> > I mean I see no reason why > > we should feel discouraged to recognize that it's sparc64. What does > > uname -m return on your machine? But most of all I wonder do we really > > have to have separate lines for NetBSD, FreeBSD and OpenBSD? Why can't > > we unify those lines to asteriskBSD-platform? In which case sparc64 > > recognition becomes a must as other flavors do support non-UltraSPARCs. > > Well, the information is currently obtained via a sysctl, which > returns (on sparc) > > enigma# sysctl hw.model > hw.model: Sun Microsystems UltraSparc-II
Does it mean that 'uname -m' doesn't work? Never did? Never will? Going to seize any time soon? But even if sysctl is the only option, we still can map *UltraSparc* to sparc64 and I think we should favor it as it's denoting ABI and is therefore less confusing. As for asteriskBSD. Can you test if './Configure OpenBSD-sparc64' works on your FreeBSD machine? A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
