Bug #8852
closedSynology build of ruby-2.0.0-p247 is failing
Description
Looks like something is missing... __stack_chk_fail_local
Gist output of "rvm --debug install ruby"
Updated by mpapis (Michal Papis) over 10 years ago
possibly related to => http://bugs.ruby-lang.org/issues/5676
but there is only gcc-4.2 => https://gist.github.com/stevesparks/772743522bbd9bdbf978#file-ipkg-list-txt-L277
Updated by nobu (Nobuyoshi Nakada) over 10 years ago
- Status changed from Open to Feedback
- Assignee deleted (
nobu (Nobuyoshi Nakada))
Probably a third party's issue?
Updated by mpapis (Michal Papis) over 10 years ago
What does it mean third party's issue
- who do you think should be investigating it?
Can you explain what to investigate, this is really edge case (Synology platform) with limited availability, how would one start debugging it?
Updated by moneytoo (Marcel Dopita) over 10 years ago
It cross compiles fine with following patch https://github.com/SynoCommunity/spksrc/blob/fad915904222094328425c2855f4fa193731ba84/cross/ruby/patches/fix-thread-stack.patch from from SynoCommunity.
It's currently reverted but I tested it and it works with 2.0.0-p247 as well.
Updated by nobu (Nobuyoshi Nakada) over 10 years ago
It seems r40476.
Could you try the trunk?
Updated by moneytoo (Marcel Dopita) over 10 years ago
moneytoo (Marcel Dopita) wrote:
It cross compiles fine with following patch https://github.com/SynoCommunity/spksrc/blob/fad915904222094328425c2855f4fa193731ba84/cross/ruby/patches/fix-thread-stack.patch from from SynoCommunity.
It's currently reverted but I tested it and it works with 2.0.0-p247 as well.
Sorry, I was not exactly right - this patch is valid only for 2.0.0-p0 as it's already fixed 2.0.0-p247. The only fix should be:
Desactivate fstack-protect because we couldn't link to libspp on synology¶
sed -i -e 's/x$$stack_protector/x$$stack_protector_broken/g' $(WORK_DIR)/$(PKG_DIR)/configure
Updated by barbecuesteve (Steve Sparks) over 10 years ago
Sorry, I am a Ruby newb, using RVM to handle the build details. I should do what, where?
Updated by barbecuesteve (Steve Sparks) over 10 years ago
Okay, I fiddled with the 'configure' file so that stack_protector came out broken. It quieted those entries but then died on our old friend
__sync_val_compare_and_swap_4
... suggestions?
Updated by moneytoo (Marcel Dopita) over 10 years ago
Well, the detection of atomic operations is working fine with Synology toolchain for me. I guess you should be able to override atomic builtins in configure.
Updated by barbecuesteve (Steve Sparks) over 10 years ago
Would you mind telling me which gcc you're using?
Updated by moneytoo (Marcel Dopita) over 10 years ago
I'm running arch 88f6281 so the toolchain includes GCC 4.2.1. If you're stuck, just give spksrc a shot to check the Ruby configure.log etc.
Updated by jeremyevans0 (Jeremy Evans) almost 5 years ago
- Status changed from Feedback to Closed
- Backport deleted (
1.9.3: UNKNOWN, 2.0.0: UNKNOWN)