This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: exceptions on sparc64 OpenBSD...


On Mon, Jan 31, 2005 at 11:07:45AM -0800, Richard Henderson wrote:
> On Mon, Jan 31, 2005 at 07:48:20PM +0100, Marc Espie wrote:
> > Actually, we are using a shared libstdc++, but the organization of code is
> > a bit different from other OSes.
> 
> Why?  What do you hope to gain other than pain and suffering
> maintaining your own view of the world?


less security holes, for starters...

Okay, probably not directly related to the issue at hand, but we've always
been very careful with dynamic loading.

Also, we're a BSD system. We can't really use GPL'ed code all over the
place. We have to be very careful about that.

And yes, even the special exception for linking executables is something
we need to ponder. I'm not certain we're going to allow code with that
provision anywhere in our system.

It would be much simpler and easier for us if the unwinder code were under a
BSD licence.  As it is, well, I'm going to look at what FreeBSD thinks
about that code, about what NetBSD thinks about that code and I'll talk
with my fellow OpenBSD developers, and we'll reach a decision.

I'm not saying that you *should* put that unwinder code under a BSD
licence. I'm just saying that it's part of the reason why we sometimes
do things differently.

It's like not having /usr/local in the include/library path by default,
or having our own linker. We're not the GNU system. We don't have quite
the same goals.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]