Bug #8852

Synology build of ruby-2.0.0-p247 is failing

Added by Steve Sparks 8 months ago. Updated 8 months ago.

[ruby-core:56965]
Status:Feedback
Priority:Normal
Assignee:-
Category:build
Target version:-
ruby -v:ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux] Backport:1.9.3: UNKNOWN, 2.0.0: UNKNOWN

Description

Looks like something is missing... _stackchkfaillocal

Gist output of "rvm --debug install ruby"

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

History

#2 Updated by Nobuyoshi Nakada 8 months ago

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

Probably a third party's issue?

#3 Updated by Michal Papis 8 months 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?

#4 Updated by Marcel Dopita 8 months 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.

#5 Updated by Nobuyoshi Nakada 8 months ago

It seems r40476.

Could you try the trunk?

#6 Updated by Marcel Dopita 8 months 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$$stackprotector/x$$stackprotectorbroken/g' $(WORKDIR)/$(PKG_DIR)/configure

#7 Updated by Steve Sparks 8 months ago

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

#8 Updated by Steve Sparks 8 months 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

_syncvalcompareandswap4

... suggestions?

#9 Updated by Marcel Dopita 8 months 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.

#10 Updated by Steve Sparks 8 months ago

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

#11 Updated by Marcel Dopita 8 months 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.

Also available in: Atom PDF