[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:16948] Compiling sylpheed 0.8.5 on Solaris 8
From:       Marc Richter <marc () marc-richter ! net>
Date:       2002-10-30 0:39:03
[Download RAW message or body]

Hi,

I'm currently trying to compile sylpheed on Solaris 8.
So far, without success, unfortunately.

The configure summary looks like this:
-------------<snip>-------------------
sylpheed 0.8.5

image support : yes (gdk-pixbuf)
GnuPG         : no
JPilot        : no
LDAP          : no
OpenSSL       : yes
compface      : no
libjconv      : no
IPv6          : no
-------------<snip>-------------------

If I then run 'make' the compile begins but fails lateron as 'sylpheed' is going to be linked.
The error is:
-------------<snip>-------------------
Undefined                       first referenced
 symbol                             in file
gdk_ic_attr_new                     gtkstext.o
gdk_ic_attr_destroy                 gtkstext.o
ld: fatal: Symbol referencing errors. No output written to sylpheed
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `sylpheed'
-------------<snip>-------------------

I've found gdk_ic_attr_new and gdk_ic_attr_destroy defined in <gdk/gdk.h>, which is in the include path
for the compiler, so I don't know what the issue is here. It should know the two symbols.

In the configure process I get the following message:
-------------<snip>-------------------
checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... 
*** Warning: Releases of GCC earlier than version 3.0 cannot reliably
*** create self contained shared libraries on Solaris systems, without
*** introducing a dependency on libgcc.a.  Therefore, libtool is disabling
*** -no-undefined support, which will at least allow you to build shared
*** libraries.  However, you may find that when you link such libraries
*** into an application without using GCC, you have to manually add
*** `gcc --print-libgcc-file-name` to the link command.  We urge you to
*** upgrade to a newer version of GCC.  Another option is to rebuild your
*** current GCC to use the GNU linker from GNU binutils 2.9.1 or newer.

yes
-------------<snip>-------------------

Could that message and the linker problem above be related ?

thanks for any help
--Marc
[prev in list] [next in list] [prev in thread] [next in thread]