From: Joel Soete Date: 2010-01-26T18:05:28+09:00 Subject: [ruby-core:27847] [Bug #2638] ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located. Issue #2638 has been updated by Joel Soete. Hello Sir, Please accept my apology, I am always trying to be more accurate in my pr report but here I was a bit disturbe. So here is my configure options: ./configure \ --prefix=/opt/${Co}pware \ --program-suffix=1.9 \ --libexecdir="\${prefix}/lib/ruby1.9" \ --mandir=/opt/${Co}pware/man \ --infodir=/opt/${Co}pware/info \ --enable-shared (with variable Co="mce-" as you certainly guess) That said, # gcc -print-libgcc-file-name /opt/freeware/lib/gcc/powerpc-ibm-aix5.3.0.0/4.2.0/libgcc.a returns well the full path of libgcc.a but my libgcc_s.a is in the same dir: # ll /opt/freeware/lib/gcc/powerpc-ibm-aix5.3.0.0/4.2.0/ total 7616 drwxr-xr-x 6 root system 4096 Aug 07 06:49 . drwxr-xr-x 3 root system 256 Mar 25 2008 .. drwxr-xr-x 7 root system 4096 Aug 07 06:47 include drwxr-xr-x 3 root system 256 Jul 31 07:11 install-tools -rw-r--r-- 1 root system 124713 Mar 25 2008 libgcc.a -rw-r--r-- 1 root system 45584 Mar 25 2008 libgcc_eh.a -rw-r--r-- 1 root system 125986 Feb 18 2008 libgcc_s.a -rw-r--r-- 1 root system 27086 Mar 25 2008 libgcov.a -rwxr-xr-x 1 root system 3376733 Mar 25 2008 libstdc++.a -rw-r--r-- 1 root system 178720 Mar 25 2008 libsupc++.a drwxr-xr-x 2 root system 256 Aug 07 06:49 ppc64 drwxr-xr-x 3 root system 256 Aug 07 06:49 pthread Well it would be more clean to run full 'make test' but after the installation some samples seems to work fine: # ruby1.9 ./sample/fib.rb 6765 # ruby1.9 ./test/test_timeout.rb Loaded suite ./test/test_timeout Started . Finished in 0.134635 seconds. # ruby1.9 ./test/ruby/test_thread.rb Loaded suite ./test/ruby/test_thread Started ............................... Finished in 21.258614 seconds. 31 tests, 101 assertions, 0 failures, 0 errors, 0 skips 1 tests, 1 assertions, 0 failures, 0 errors, 0 skips Anyway, I already see 2 issues: - I don't now if it wouldn't be better to use the 'pthread' version of libgcc_s (/opt/freeware/lib/gcc/powerpc-ibm-aix5.3.0.0/4.2.0/pthread)? - how would I manage a 64bit build: * normaly I would simply use -m64 gcc compile option to do so; * but "# gcc -m64 -print-libgcc-file-name" always return same result and not /opt/freeware/lib/gcc/powerpc-ibm-aix5.3.0.0/4.2.0/ppc64? Thanks a lot for your attention, J. ---------------------------------------- http://redmine.ruby-lang.org/issues/show/2638 ---------------------------------------- http://redmine.ruby-lang.org