From kde-solaris  Fri Sep 14 15:18:25 2001
From: Nick Thompson <nickthompson () agere ! com>
Date: Fri, 14 Sep 2001 15:18:25 +0000
To: kde-solaris
Subject: Re: [kde-solaris] Compiling KOffice
X-MARC-Message: https://marc.info/?l=kde-solaris&m=100048139002767

In the man for Sun ld it says:

 -z text     In dynamic mode only, forces  a  fatal  error  if  any
             relocations against non-writable, allocatable sections
             remain.
 -z textoff  In dynamic mode only, allows relocations  against
             all allocatable  sections,  including  non-writable  ones.
             This is the default when building a shared object.
 -z textwarn In dynamic mode only, lists a warning if  any  reloca-
             tions   against   non-writable,  allocatable  sections
             remain. This is the default when building  an  execut-
             able.

Still, its anyones guess what that means :)

If you are building a library then I guess you would expect end up with
relocations required in the text (read only) section. The above suggests
the -z textoff is the default in that case (shared object). However, if
gcc is suggesting to ld that it should use -z text when building shared
objects (%{shared:-G -dy %{!mimpure-text:-z text}}), then presumably ld
ignores the default, textoff, and fails on a condition you would expect
to find in a shared library. I think that is a mistake in the gcc
install.

Nick.

Mathias Waack wrote:

> On Friday 14 September 2001 14:05, Nick Thompson wrote:
> > I have seen this in the past. It seems to be a problem with using
> > gcc in conjunction with Solaris ld. I eventually switched to the
> > GNU binutils package and rebuilt gcc to use as and ld from that.
> > This is a much more satisfactory setup than the one I had before
> > (better error messages and less errors like yours). However, for a
> > while I worked around the problem. If you look in the spec file
> > that is in the gcc tree (gcc -v will tell you where), you will see
> > the option '-z text' used in a few places. Removing these
> > references seems to help. In both cases just remove the text '-z
> > text' and the syntax still appears to be acceptable to gcc.
>
> Hmm, its a bit magic to me but the simplest solution. I've tried it
> and it works. But believe me - I hate it to do things I don't
> understand.

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.