Opened 9 years ago

Closed 9 years ago

#8769 closed Bugs (wontfix)

Fails to build Boog.Log using Apple GCC 4.2.1

Reported by: manphiz@… Owned by: Andrey Semashev
Milestone: To Be Determined Component: log
Version: Boost 1.54.0 Severity: Problem
Keywords: Cc:

Description

Currently 1.54.0 release fails to build using Apple GCC 4.2.1, which is the default compiler in Mac OS X 10.6 and also available through 10.8. The build log in Homebrew is attached.

Attachments (1)

boost_1.54.0_snow_leopard_build.log.gz (243.2 KB ) - added by manphiz@… 9 years ago.
Full build log of 1.54.0 using Apple GCC 4.2.1 on Mac OS X 10.6.

Download all attachments as: .zip

Change History (6)

by manphiz@…, 9 years ago

Full build log of 1.54.0 using Apple GCC 4.2.1 on Mac OS X 10.6.

comment:1 by anonymous, 9 years ago

Sorry, my mistake: Apple GCC has not been shipped since XCode 4.0, but is still provided by the R project and widely used.

comment:2 by Andrey Semashev, 9 years ago

From the compile errors it looks like the compiler can't cope with TR1 result_of protocol. If that's the case, I'm afraid I can't help it because this basically renders filters and formatters useless. Note that the compiler is listed as not supported in the test farm and the docs (not explicitly) for this reason.

I do not have access to this platform, so I cannot experiment with it. So the only way I can add support for this compiler is by applying a patch. Do you have one?

comment:3 by Xiyue Deng <manphiz@…>, 9 years ago

So this looks like similar problem with https://svn.boost.org/trac/boost/ticket/8639, which is understandable as GCC 4.2 is also quite old. Though I'd like to look into this, it will take time and given the complexity of the library it won't happen soon.

comment:4 by Marshall Clow, 9 years ago

If you look at the test results, you'll notice that all the log tests have been marked "expected fail" on Mac OS X with gcc 4.2.1

comment:5 by Andrey Semashev, 9 years ago

Resolution: wontfix
Status: newclosed

I'm closing this ticket for now. Feel free to reopen it if you have a patch.

Note: See TracTickets for help on using tickets.