From: "ko1 (Koichi Sasada)" Date: 2013-02-18T09:03:18+09:00 Subject: [ruby-core:52415] [ruby-trunk - Bug #7856] The usage of try_run in extconf.rb is broken when crosscompiling Issue #7856 has been updated by ko1 (Koichi Sasada). Assignee set to nobu (Nobuyoshi Nakada) Target version changed from 1.9.2 to next minor ---------------------------------------- Bug #7856: The usage of try_run in extconf.rb is broken when crosscompiling https://bugs.ruby-lang.org/issues/7856#change-36470 Author: luizluca (Luiz Angelo Daros de Luca) Status: Feedback Priority: Normal Assignee: nobu (Nobuyoshi Nakada) Category: ext Target version: next minor ruby -v: 1.9.2p0 Hello, Every "try_run" inside extconf.rb (found in some ext/*/extconf.rb) tries to compile and run the generated binary. However, when crosscompiling, this simply can't work. Please, make try_run be ignored (or just test the compilation) when crosscompiling is detected. I tested this only at 1.9.2 but this might affect all versions that uses try_run to test dependencies. Taking socket as an example, this can be solved individually, from the original: getaddr_info_ok = (enable_config("wide-getaddrinfo") && :wide) || (checking_for("wide getaddrinfo") {try_run(< && false) || (checking_for("wide getaddrinfo") {try_run(<