On Thu, Oct 27, 2005 at 06:56:57PM +0200, Thiemo Seufer wrote: > > The attached patch adds big-endian arm support to gcc-2.95. It's > > more-or-less the same as its gcc-4.0 counterpart: teach the debian > > build scripts about 'armeb', and patch gcc so that it defaults to > > big-endian. > > I'm curious, is there a reason why you _need_ 2.95 for a new port? > Wouldn't it be better to fix the few packages which still require it?
Some packages in sarge required libstdc++2.10 to build (aiksaurus?), and thus the gcc-2.95 armeb patch ended up in our repository. I'm just forward-porting all patches that we have, I don't actually know whether there are any packages left in sid that still depend on libstdc++2.10. (At least aiksaurus doesn't anymore, see #262556.) The patch is fairly simple, and so I figured "why not?", but I do agree that there shouldn't be any packages left in sid still requiring 2.95. Another reason for submitting this patch was to have all patches needed for the armeb architecture archived in a central place. (Since armeb was never part of any high-profile distro, there are various armeb patches floating around the net, scattered around all over the place.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]