Boost C++ Libraries: Ticket #4788: boost.system doesn't link on Mac OS 10.4 SDK https://svn.boost.org/trac10/ticket/4788 <p> Hello everyone. </p> <p> In fact i'm compiling on Mac OS 10.6, but i was trying to compile for 10.4 to get a better compatibility for my application. It was working until I add the boost filesystem library, which uses the boost system library. </p> <p> I got the following answer : </p> <hr /> <blockquote> <p> "<span class="underline">_stack_chk_fail", referenced from: </span></p> <blockquote> <p> (anonymous namespace)::generic_error_category::message(int) constin libboost_system.a(error_code.o) </p> </blockquote> </blockquote> <blockquote> <blockquote> <p> "<span class="underline">_stack_chk_guard", referenced from: </span></p> <blockquote> <p> <span class="underline">_stack_chk_guard$non_lazy_ptr in libboost_system.a(error_code.o) </span></p> </blockquote> <p> (maybe you meant: <span class="underline">_stack_chk_guard$non_lazy_ptr) </span></p> </blockquote> </blockquote> <p> ld: symbol(s) not found collect2: ld returned 1 exit status </p> <hr /> <p> The fact is that when i changed the var "Base SDK" [SDKROOT] from macosx10.4 to macosx10.5, it just worked well. </p> <p> I found more or less the same problem on another project: <a class="ext-link" href="http://trac.wildfiregames.com/wiki/BuildInstructions"><span class="icon">​</span>http://trac.wildfiregames.com/wiki/BuildInstructions</a> It notices: </p> <hr /> <p> If you get linker errors like /usr/bin/ld: Undefined symbols: <span class="underline">_stack_chk_fail, </span>_stack_chk_guard, this comes from using a libc that is not glibc &gt;=2.4. Until this is detected by the build system, you can hack it by removing the "-fstack-protector-all" line (and the next line too if needed) from build/premake/premake.lua </p> <hr /> <p> It would be great if it was possible to patch that. Hope this ticket wasn't already posted. Best regards. </p> <p> nuKs. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/4788 Trac 1.4.3 anonymous Mon, 25 Oct 2010 21:23:05 GMT keywords set https://svn.boost.org/trac10/ticket/4788#comment:1 https://svn.boost.org/trac10/ticket/4788#comment:1 <ul> <li><strong>keywords</strong> bjam linking mac 10.4 added </li> </ul> Ticket Beman Dawes Wed, 01 Dec 2010 21:11:23 GMT <link>https://svn.boost.org/trac10/ticket/4788#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/4788#comment:2</guid> <description> <p> Posted to the Boost Build list: </p> <p> Ticket svn.boost.org/trac/boost/ticket/4788 got assigned to Boost.System, but it seems to me that it is really complaining that bjam and/or the build system is using an option not supported by older Apple SDK's. </p> <p> To me, this seems to be more akin to user error than a problem with any Boost component. Should I just close it as worksforme, or would any of the Build folks like to try to do something about it? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Vladimir Prus</dc:creator> <pubDate>Wed, 01 Dec 2010 21:23:16 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/4788#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/4788#comment:3</guid> <description> <p> I am afraid I don't fully understand what exactly are you doing to get this problem. Do you have a reproduction recipe. Also, Boost.Build is not using the -fstack-protector-all option at all, as far as I can see, so, what is the proposed fix? </p> <p> Thanks, Volodya </p> </description> <category>Ticket</category> </item> <item> <author>gse.nuks@…</author> <pubDate>Thu, 02 Dec 2010 03:30:57 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/4788#comment:4 https://svn.boost.org/trac10/ticket/4788#comment:4 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">worksforme</span> </li> </ul> <p> I'm sorry, I'm not able to reproduce the problem a second time and I didn't save the project when I had it. Sorry to have wasted your time. </p> Ticket