#10272: Incorporation of GCC 4.8 ----------------------------+---------------------------- Reporter: korli | Owner: nobody Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 1 | Platform: All ----------------------------+---------------------------- Comment (by bonefish): Replying to [comment:30 korli]: > Replying to [comment:29 bonefish]: > > I think, it's time to stop linking libgcc into libroot. That might require us to change the build process a bit (build a stub libroot, so we can build a shared libgcc), but I can't think of any negative side effects ATM. > > A few questions arise (What about hybrid builds? What would the migration path?). We could do that only for gcc 4. It should be possible for gcc 2 as well, but it is less relevant, since that compiler won't be updated anyway (safe for minor changes). For the build system it doesn't matter much whether the handling for both compilers is the same. There are only a few places that need the distinction anyway (building the stub libroot, building libroot, rule `AddSharedObjectGlueCode`). The tricky part might be figuring out how to build the cross gcc with the shared libgcc, since for building the stub libroot we may already need a compiler. -- Ticket URL: <https://dev.haiku-os.org/ticket/10272#comment:31> Haiku <https://dev.haiku-os.org> Haiku - the operating system.