|
|
Created:
6 years, 5 months ago by sandersd (OOO until July 31) Modified:
6 years, 5 months ago CC:
chromium-reviews, posciak+watch_chromium.org, jam, mcasas+watch_chromium.org, feature-media-reviews_chromium.org, darin-cc_chromium.org, piman+watch_chromium.org, wjia+watch_chromium.org, Mark Mentovai Base URL:
https://chromium.googlesource.com/chromium/src.git@master Project:
chromium Visibility:
Public. |
DescriptionFix compilation with OS X SDK 10.8.
The system headers include visibility attributes, and thus should only be used if the frameworks are linked in.
BUG=393439
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=283267
Patch Set 1 #
Messages
Total messages: 20 (0 generated)
It works for me, thanks!
Which SDK were you using when it broke, and how is it declaring things incorrectly that caused this problem?
On 2014/07/14 21:50:46, Mark Mentovai wrote: > Which SDK were you using when it broke, and how is it declaring things > incorrectly that caused this problem? This patch fixes the build for me as well. I'm on OSX 10.9.4 with Xcode 5.1.1. I think these are the latest versions you can get without a paid ADC membership. The build process selected the 10.8 SDK by default. A default install of Xcode 5.1.1 only has the 10.8 and 10.9 SDKs in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/. I hope this helps.
On 2014/07/14 21:50:46, Mark Mentovai wrote: > Which SDK were you using when it broke, and how is it declaring things > incorrectly that caused this problem? The only thing special about these symbols is that they were declared both by vt_stubs and by the system headers.
On 2014/07/14 22:19:53, sandersd wrote: > On 2014/07/14 21:50:46, Mark Mentovai wrote: > > Which SDK were you using when it broke, and how is it declaring things > > incorrectly that caused this problem? > > The only thing special about these symbols is that they were declared both by > vt_stubs and by the system headers. Okay, it looks like the system headers add visibility attributes as part of the SDK version macros, and so should only be included if we are also linking.
On 2014/07/14 22:34:59, sandersd wrote: > On 2014/07/14 22:19:53, sandersd wrote: > > On 2014/07/14 21:50:46, Mark Mentovai wrote: > > > Which SDK were you using when it broke, and how is it declaring things > > > incorrectly that caused this problem? > > > > The only thing special about these symbols is that they were declared both by > > vt_stubs and by the system headers. > > Okay, it looks like the system headers add visibility attributes as part of the > SDK version macros, and so should only be included if we are also linking. can you add that to the CL description? other than that -- lgtm! thanks for the quick fix!
The CQ bit was checked by sandersd@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/sandersd@chromium.org/393633002/1
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_dbg_triggered_tests on tryserver.chromium (http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...) win_chromium_rel on tryserver.chromium (http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_dbg_triggered_tests on tryserver.chromium (http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
The CQ bit was checked by mathp@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/sandersd@chromium.org/393633002/1
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_dbg_triggered_tests on tryserver.chromium (http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_dbg_triggered_tests on tryserver.chromium (http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
The CQ bit was checked by sandersd@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/sandersd@chromium.org/393633002/1
Message was sent while issue was closed.
Change committed as 283267 |