On 05/24/2011 11:51 AM, [email protected] wrote: > On Tue, May 24, 2011 at 10:46:52AM +0100, Andrew Haley wrote: > >> FYI: mips-openbsd gcc to be deprecated. >> >> Is the MIPS OpenBSD port dead? > > No. I am using and writing to you from a MIPS-based > machine (Lemote Loongson) where code is compiled > using gcc. > > I saw your message dated May 24th 02:40 am about it. > > I remember seeing something about a.out being deprecated, > but I thought (I am wrong ?) that it would not affect > ELF output. > > On this web page : > http://gcc.gnu.org/gcc-4.6/changes.html > > There is this : > > a.out NetBSD ([...] but not *-*-netbsdelf*) > > Since OpenBSD and NetBSD have close toolchains, well at least > both based on gcc for the same platforms, I thought this would > also apply to OpenBSD. > > Compiled code we use on MIPS platforms I know of is > ELF 64-bit code. So if a.out gets deprecated it's not a > problem since we use ELF binaries. > > All BSD systems have moved to the ELF format and a.out > is only used for older versions of the systems. So seeing gcc > deprecated a.out is not a problem I think. > > But do their deprecation is about removing a.out output > for MIPS code on Open and NetBSD or do they intend to remove > the possibility of producing MIPS code ? > > I doubt it. Currently, we use gcc to compile our binaries > the very same way people on Linux do it, on the same > platforms. > > I have not been able to find if they are talking of removing > a.out output from gcc or if they intend to remove all gcc > support for those MIPS processors/platforms for BSD > systems (that would be surprising).
It would. I think it's only the old MIPS32 a.out that's deprecated. Andrew.
