[haiku-bugs] Re: [Haiku] #8609: optional package for libraries are not hybrid-enabled

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Mon, 28 May 2012 15:04:39 -0000

#8609: optional package for libraries are not hybrid-enabled
----------------------------+----------------------------
   Reporter:  pulkomandy    |      Owner:  bonefish
       Type:  enhancement   |     Status:  new
   Priority:  normal        |  Milestone:  Unscheduled
  Component:  Build System  |    Version:  R1/Development
 Resolution:                |   Keywords:
 Blocked By:                |   Blocking:
Has a Patch:  0             |   Platform:  All
----------------------------+----------------------------

Comment (by bonefish):

 Replying to [ticket:8609 pulkomandy]:
 >  * The package manager may solve that in a better way ? (installing the
 libs at the right place somehow ?)

 With package management there will simply be two gcc4 packages: one for a
 gcc4 Haiku, one for a gcc2 Haiku. As such this solution is not related to
 package management. It could be implemented already, but would require
 work on the build system, as well as building all the new packages --
 which would have to be solved differently/have to be redone with package
 management. So it isn't a particularly good investment of time ATM.

 >  * There is some work needed on build of packages, for example sdl-
 config, allegro-config and other pkg-config files should look to setgcc
 setting and use the right lib path according to that.

 First of all, as you already said, the runtime loader should not allow
 mixing shared objects for the two gcc versions. It should simply ignore
 mismatching ones. The reason why it doesn't and why both paths are
 searched is historical. It was necessary once, since we built C only
 libraries only for one gcc and used them in all combinations. I think all
 packages are available for both gccs now, so the runtime loader could be
 adjusted accordingly.

 We may also need to go further and use another library path variable for
 the alternative gcc (like `LIBRARY_PATH_GCC4` on a gcc2h build). Further
 path related changes (to gcc, cmake, pkg-config) may be necessary as well.

 Save for the runtime loader related ones I'd put off the changes until
 package management is ready.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/8609#comment:1>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: