Re: Linking problem building iconv on Solaris x86

[Dr. David Kirkby]

On 08/10/10 10:10 PM, Ralf Wildenhues wrote:
> Hello David,
>
> * Dr. David Kirkby wrote on Tue, Aug 10, 2010 at 10:48:25PM CEST:
> > On 08/10/10 09:28 PM, Ralf Wildenhues wrote:
> > > /bin/bash ../libtool --mode=link gcc  -m64 -fvisibility=hidden -o libiconv.la 
> > > -rpath /home/drkirkby/fulvia/64/sage-4.5.3.alpha0/local/lib -version-info 7:0:5 
> > > iconv.lo localcharset.lo relocatable.lo
> >
> > No, it does not.
> >
> > (sage subshell) fulvia:lib drkirkby$ /bin/bash ../libtool
> > --mode=link gcc  -m64 -fvisibility=hidden -o libiconv.la -rpath
> > /home/drkirkby/fulvia/64/sage-4.5.3.alpha0/local/lib -version-info
> > 7:0:5 iconv.lo localcharset.lo relocatable.lo
> > libtool: link: gcc -shared -Wl,-z -Wl,text -Wl,-h -Wl,libiconv.so.2
> > -o .libs/libiconv.so.2.5.0  .libs/iconv.o .libs/localcharset.o
> > .libs/relocatable.o   -lc  -m64
>
> Hrmpf.  On Solaris, we add '${wl}-z ${wl}text' to archive_cmds and
> archive_expsyms_cmds unconditionally, as opposed to only with
> -no-undefined.  I wonder why that is the case.

If you don't know, I'm sure I don't.

> But of course I also wonder why the problem happens at all.  iconv.o is
> built with PIC, so that would indicate a bug in GCC, or possibly the
> assembler or linker.  Which GCC version is this, and how was it
> configured?

gcc 4.5.1 configured to use the Sun linker and the GNU assembler. I personally 
did not configure it, but this is how it was configured.

64 address@hidden:[~] $ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.5.1/x86_64-SunOS-core2-sun-ld/libexec/gcc/i386-pc-solaris2.10/4.5.1/lto-wrapper
Target: i386-pc-solaris2.10
Configured with: /usr/local/gcc-4.5.1/src/gcc-4.5.1/configure 
--enable-languages=c,c++,fortran --with-gnu-as 
--with-as=/usr/local/binutils-2.20.1/x86_64-SunOS-core2-gcc-4.4.3/bin/as 
--with-ld=/usr/ccs/bin/ld 
--with-gmp=/usr/local/gmp-5.0.1/x86_64-SunOS-core2-gcc-4.5.0-abi32 
--with-mpfr=/usr/local/mpfr-3.0.0/x86_64-SunOS-core2-gmp-5.0.1-gcc-4.5.0-abi32 
--with-mpc=/usr/local/mpc-0.8.2/x86_64-SunOS-core2-mpfr-3.0.0-gmp-5.0.1-gcc-4.5.0-abi32 
--prefix=/usr/local/gcc-4.5.1/x86_64-SunOS-core2-sun-ld
Thread model: posix
gcc version 4.5.1 (GCC)


On the OpenSolaris machine which also has the problem.

-bash-3.2$ gcc -v
Reading specs from /opt/sfw/lib/gcc/i386-pc-solaris2.11/4.3.2/specs
Target: i386-pc-solaris2.11
Configured with: ./configure --prefix=/opt/sfw --enable-shared 
--with-gmp=/opt/sfw --with-mpfr=/opt/sfw --with-gnu-as 
--with-as=/usr/sfw/bin/gas --without-gnu-ld --with-ld=/usr/ccs/bin/ld 
--enable-stage1-languages=c,c++ --enable-languages=c,c++,objc,fortran
Thread model: posix
gcc driver version 4.3.2 (GCC) executing gcc version 4.2.3

You can see the resulting error message on the OpenSolaris machine here

http://trac.sagemath.org/sage_trac/ticket/9405

but its not very detailed. I could attach a complete log if you feel it would be 
useful, though it looks to be the same problem to me.

> Any chance you can create a small reproducible example to
> send to the GCC bugzilla?

I really would not have a clue how to, but if you have the time, I can probably 
get you an account on the machine. It related to the Sage project at the 
University of Washington, where I got you an account before.

 >> I've often had these "relocations remain against allocatable but
> > non-writable sections" messages on Solaris. They seem to fox a lot of
> > people when you Google for them.
>
> Sorry for them, but I don't think Google is accepting bug reports for
> Libtool nor GCC.  I don't recall a prior report for gcc on Solaris on
> the Libtool lists (unlike for a C++ compiler on Solaris).
>
> Cheers,
> Ralf

It's not so obvious where the bug here is, which is perhaps why people don't 
really know where to report it to.

Dave