Bug #8852: Synology build of ruby-2.0.0-p247 is failing

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]

[barbecuesteve (Steve Sparks)]

Looks like something is missing... __stack_chk_fail_local

Gist output of "rvm --debug install ruby"

https://gist.github.com/stevesparks/eebabfbcc23884b29c24

[mpapis (Michal Papis)]

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

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Feedback
• Assignee deleted (nobu (Nobuyoshi Nakada))

Probably a third party's issue?

[mpapis (Michal Papis)]

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?

[moneytoo (Marcel Dopita)]

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.

[nobu (Nobuyoshi Nakada)]

It seems r40476.

Could you try the trunk?

[moneytoo (Marcel Dopita)]

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

[barbecuesteve (Steve Sparks)]

Sorry, I am a Ruby newb, using RVM to handle the build details. I should do what, where?

[barbecuesteve (Steve Sparks)]

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?

[moneytoo (Marcel Dopita)]

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.

[barbecuesteve (Steve Sparks)]

Would you mind telling me which gcc you're using?

[moneytoo (Marcel Dopita)]

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.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed
• Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN)