Project

General

Profile

Bug #12528

Ruby 2.3.1 Fails to Compile on FreeBSD 8.4-STABLE

Added by martin_vahi (Martin Vahi) about 3 years ago. Updated 24 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:76172]

Description

Build commands:

make clean

CFLAGS=" -mtune=native -ftree-vectorize " CXXFLAGS=" -mtune=native -ftree-vectorize " ./configure --prefix=/www/apache/domains/www.softf1.com/private_tree_1/m_local/bin_p/Ruby/v_2_3_1  --enable-multiarch --disable-install-doc

CFLAGS=" -mtune=native -ftree-vectorize " CXXFLAGS=" -mtune=native -ftree-vectorize " time nice -n 20 make

An excerpt that describes the failure:

linking shared-object -test-/st/update.so
compiling cstr.c
compiling ellipsize.c
compiling fstring.c
compiling enc_associate.c
compiling set_len.c
compiling nofree.c
compiling coderange.c
compiling qsort.c
compiling modify.c
compiling normalize.c
compiling init.c
compiling enc_str_buf_cat.c
linking shared-object -test-/string.so
compiling duplicate.c
compiling member.c
compiling init.c
linking shared-object -test-/struct.so
compiling type.c
compiling init.c
linking shared-object -test-/symbol.so
compiling init.c
compiling new.c
linking shared-object -test-/time.so
compiling tracepoint.c
compiling gc_hook.c
linking shared-object -test-/tracepoint.so
compiling typeddata.c
linking shared-object -test-/typeddata/typeddata.so
compiling at_exit.c
linking shared-object -test-/vm/at_exit.so
compiling wait_for_single_fd.c
linking shared-object -test-/wait_for_single_fd/wait_for_single_fd.so
compiling bigdecimal.c
linking shared-object bigdecimal.so
/usr/bin/ld: bigdecimal.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC
bigdecimal.o: could not read symbols: Bad value
*** Error code 1

Stop in /home/vhost7825ssh/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1/ext/bigdecimal.
*** Error code 1

Stop in /home/vhost7825ssh/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1.
*** Error code 1

Stop in /home/vhost7825ssh/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1.
       59.58 real        45.37 user        12.40 sys
[vhost7825ssh@hamal ~/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1]$ uname -a
FreeBSD hamal.elkdata.ee 8.4-STABLE FreeBSD 8.4-STABLE #0: Fri Nov 29 14:11:33 EET 2013     root@hamal.elkdata.ee:/usr/obj/usr/src/sys/ELKDATA  amd64
[vhost7825ssh@hamal ~/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1]$ date
Tue Jun 28 11:31:50 UTC 2016
[vhost7825ssh@hamal ~/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1]$ gcc --version
gcc (GCC) 4.2.1 20070831 patched [FreeBSD]
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[vhost7825ssh@hamal ~/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1]$ g++ --version
g++ (GCC) 4.2.1 20070831 patched [FreeBSD]
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[vhost7825ssh@hamal ~/private_tree_1/m_local/bin_p/Ruby/kompil/ruby-2.3.1]$

History

Updated by nobu (Nobuyoshi Nakada) about 3 years ago

  • Status changed from Open to Feedback

What configure options do you use?
Could you try --enable-shared if it is not used?

Updated by martin_vahi (Martin Vahi) about 3 years ago

Nobuyoshi Nakada wrote:

What configure options do you use?
Could you try --enable-shared if it is not used?

It seems that You are right, the --enable-shared solved the problem.
Is it possible to make the --enable-shared to be switched on by default?
If it is de facto mandatory, then it should be switched on by default.

Updated by nagachika (Tomoyuki Chikanaga) about 3 years ago

  • Backport changed from 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN to 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: REQUIRED

Updated by nobu (Nobuyoshi Nakada) about 3 years ago

Martin Vahi wrote:

It seems that You are right, the --enable-shared solved the problem.
Is it possible to make the --enable-shared to be switched on by default?
If it is de facto mandatory, then it should be switched on by default.

It is a different story. --disable-shared isn't working should be a bug.
Could you show rbconfig.rb and ext/bigdecimal/mkmf.log files when failed?

#5

Updated by jeremyevans0 (Jeremy Evans) 24 days ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF