[haiku-development] Re: Updates relating to build-o-matic, haiku-files.org

  • From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 17 May 2011 21:58:56 +0100

Are there any thoughts, as to how gcc2 compatibility will be
handled/provided in post-R1?

... I don't expect that we would want (pre)R1 gcc2 bits going into
lib/  (and the other add-ons folders).
Though, old&  unmaintained software would still expect to be extracted
into lib/ and such.

It may be possible to tag the elf files with version info (I think this is done already) and have the runtime loader drop files when the version doesn't match. We may want to add more checks for that, for example in ld to warn at compile time.

As the new gcc4 API drifts away from the legacy one, the odds of getting something linked mixing both kinds of libs will be reduced, so we shouldn't see too much problems ?

Other related posts: