[haiku-commits] Re: BRANCH midar-github.master - src/system/libroot/posix/glibc/stdio-common src/servers/app src/kits/app src/apps/icon-o-matic/shape headers/os/support

  • From: Jonathan Schleifer <js-haiku-commits@xxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Sun, 25 Nov 2012 15:18:04 +0100

Am 25.11.2012 um 15:02 schrieb pulkomandy:

> I don't see why. We use it in the Kernel in Haiku, and I already used it
> at lower levels in some other projects (you can get the reset vectors
> for a Cortex-M3 processor written entirely in C++, for example). Has
> libc a very special exception to that ?

Yes. It means that you always have to pull in C++ which is not fully compatible 
with C. In every C application.

It also means that static linking will be broken: You suddenly have to specify 
-lstdc++ to link a C program, as dependencies are only resolved for shared 

That whole file is ugly (like the rest of this ancient glibc), so I don't see 
why we should really bother? We should instead focus on importing a newer and 
more sane libc for gcc4.


Other related posts: