boost.system doesn't link on Mac OS 10.4 SDK

[gse.nuks@…]

Hello everyone.

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.

I got the following answer :

---

"_stack_chk_fail", referenced from:

(anonymous namespace)::generic_error_category::message(int) constin libboost_system.a(error_code.o)

"_stack_chk_guard", referenced from:

_stack_chk_guard$non_lazy_ptr in libboost_system.a(error_code.o)

(maybe you meant: _stack_chk_guard$non_lazy_ptr)

ld: symbol(s) not found collect2: ld returned 1 exit status

---

The fact is that when i changed the var "Base SDK" [SDKROOT] from macosx10.4 to macosx10.5, it just worked well.

I found more or less the same problem on another project: ​http://trac.wildfiregames.com/wiki/BuildInstructions It notices:

---

If you get linker errors like /usr/bin/ld: Undefined symbols: _stack_chk_fail, _stack_chk_guard, this comes from using a libc that is not glibc >=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

---

It would be great if it was possible to patch that. Hope this ticket wasn't already posted. Best regards.

nuKs.

[Beman Dawes]

Posted to the Boost Build list:

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.

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?

[Vladimir Prus]

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?

Thanks, Volodya

[gse.nuks@…]

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.