From: nobu@...
Date: 2014-12-18T12:53:55+00:00
Subject: [ruby-core:66950] [ruby-trunk - Bug #10210] [Closed] LDSHARED and LDSHAREDXX set to null ('')

Issue #10210 has been updated by Nobuyoshi Nakada.

Status changed from Open to Closed
% Done changed from 0 to 100

Applied in changeset r48886.

----------
configure.in: fix fox BusyBox

* configure.in (rb_cv_binary_elf): get rid of -e option of cat
  which is not available on BusyBox, use tr instead.
  [ruby-core:64824] [Bug #10210]

----------------------------------------
Bug #10210: LDSHARED and  LDSHAREDXX set to null ('')
https://bugs.ruby-lang.org/issues/10210#change-50492

* Author: Ivailo Monev
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: build
* Target version: current: 2.2.0
* ruby -v: 1.9.3-p547, 2.1.2
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
While attempting to build Ruby on custom linux setup versions from 1.9.3-p547 to 2.1.2 fail to build, setting `LDSHARED` to "gcc -shared" and `LDSHAREDXX` to "g++ -shared" kind of sorted the problem but I still see some messages in the build log like:

~~~
make[2]: o: Command not found
make[2]: [../../.ext/i686-linux/ripper.so] Error 127 (ignored)
~~~

I'm attaching the config.log. Also, I want to highlight that on this setup Busybox is used and during the configure step I see the following (stripped) message:

~~~
checking whether ELF binaries are produced... cat: invalid option -- 'e'
BusyBox v1.22.1 (2014-08-30 20:49:51 UTC) multi-call binary.
...
no
~~~


---Files--------------------------------
config.log (837 KB)


-- 
https://bugs.ruby-lang.org/