[haiku-bugs] Re: [Haiku] #10272: Incorporation of GCC 4.8
- From: "korli" <trac@xxxxxxxxxxxx>
- Date: Wed, 29 Jan 2014 07:47:25 -0000
#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 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?). When fixed, the commit to be reverted is this [http://cgit.haiku-
os.org/buildtools/commit/?id=f34aded965ad590a48d0a26966a0c70de4ed61a4
one]. I'll open a ticket.
4.8.2 integrated in btrev43069. GCC with graphite fixed in hrev46783. m68k
build fixed in btrev43070.
Native packages are updated in hrev46788, hrev46789 , hrev46791.
Two notes:
* -pipe for cross tools build should only be used when --use-gcc-pipe is
passed to configure.
* anevilyak: "the multijob cross-tools build is broken here for 4.8 ; even
as little as -j2 results in a failure early on where mkdir complains about
cross-tools/x86/include already existing. Without any parallelization, it
succeeds. This is on FreeBSD 9.2, and the cross tools build worked fine
for -j8 with 4.7.3."
--
Ticket URL: <https://dev.haiku-os.org/ticket/10272#comment:30>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
