[haiku-bugs] Re: [Haiku] #7792: error when compiling Haiku with gcc 4.5.3

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Tue, 12 Jul 2011 15:52:31 -0000

#7792: error when compiling Haiku with gcc 4.5.3
----------------------------+----------------------------
   Reporter:  diger         |      Owner:  korli
       Type:  bug           |     Status:  closed
   Priority:  normal        |  Milestone:  R1
  Component:  Build System  |    Version:  R1/Development
 Resolution:  invalid       |   Keywords:
 Blocked By:                |   Blocking:
Has a Patch:  0             |   Platform:  All
----------------------------+----------------------------

Comment (by bonefish):

 Replying to [comment:15 siarzhuk]:
 > Replying to [comment:14 bonefish]:
 > > I wouldn't say that this is a bug. The gcc-4.5.3 optional package only
 works on a Haiku system built with that compiler. Installing it on a
 mismatching Haiku is a user error.
 > >
 > User has not installed the new compiler - he has only updated the source
 tree. The compiler was changed silently

 Updating the source tree does certainly not change the installed compiler.
 Nor does anything you can do with the build system, save for actually
 installing a new Haiku over your old one.

 > and that change costs a bit of time to understand the problem and write
 this long [and futile!] discussion in the Trac. May be some gcc version
 check should be introduced in build scripts to prevent entering this "gray
 area" again in the future?

 We do have a version check for gcc 2. It was intentionally omitted for the
 experimental gcc 4 to avoid annoying developers unnecessarily. We could
 maybe make that a warning. Anyway, it wouldn't have helped in this case
 though, since installing a compiler not matching the OS (however that was
 done) simply results in a broken compiler. That doesn't really have
 anything to do Haiku's build system.

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

Other related posts: