Christian Weisgerber writes: > Grepping the ports tree for uses of /usr/bin/gcc turned up > devel/arm-elf/gcc. That port has been marked BROKEN "due to frequent > segfaults during build" for 4.5 years. I guess nobody has missed > it since. > > I was going to suggest that we remove the port, but it's part of > four related ones: > > devel/arm-elf/binutils > devel/arm-elf/gcc > devel/arm-elf/gdb > devel/arm-elf/newlib > > newlib depends on gcc, so it will have to go too if gcc goes. > binutils and gdb are independent of gcc, and in fact we have packages > for them. But are they any use on their own? > > The ports were imported in 2007, once updated in 2010, the maintainer > asked to be removed in 2012, and otherwise the changes have been > mostly infrastructure churn. > > Can we delete all of devel/arm-elf? Yes? No? > What's the use of an "arm-elf" cross-tools suite?
I used to program Olimex boards with those ports. But that was nearly ten years ago. We have many cross-compilers in the tree. It should be easy enough for someone who needs it to send a diff based on the working ones. A port broken this long doesn't need to stay. ok bentley@
