atom feed4 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: Courier build...
FromSent OnAttachments
Zsolt Kiss GereSep 6, 2002 10:17 am 
Sam VarshavchikSep 6, 2002 11:23 am 
John KlossSep 6, 2002 11:45 am 
Zsolt Kiss GereSep 8, 2002 7:58 am 
Subject:RE: [courier-users] Re: Courier build failed on Solaris 8
From:John Kloss (jkl@sapiens.wustl.edu)
Date:Sep 6, 2002 11:45:41 am
List:net.sourceforge.lists.courier-users

Or you could use crle and be done with it.

crle -l /usr/lib -l /usr/lib/64 -l /usr/local/lib -l /usr/some/other/lib

That sets the Solaris ld default search path to

/usr/lib:/usr/lib/64:/usr/local/lib:/usr/some/other/lib

It's much like ld.conf in linux. Infact it sets an ld.config file under /var/ld and /var/ld/64.

Gish Lab, Genome Sequencing Center Washington University Medical School ... in St. Louis

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net] On Behalf Of Sam Varshavchik Sent: Friday, September 06, 2002 11:24 AM To: cour@lists.sourceforge.net Subject: [courier-users] Re: Courier build failed on Solaris 8

Zsolt Kiss Gere writes:

Hi,

I am trying to compile and run the Courier server on a Solaris 8 platform. After installation, when trying to run sg I get the following:

ld.so.1: /usr/lib/courier/libexec/courier/aliascombine: fatal: libgcc_s.so.1: open failed: No such file or directory ld.so.1: /usr/lib/courier/libexec/courier/aliascreate: fatal: libgcc_s.so.1: open failed: No such file or directory Killed ld.so.1: /usr/lib/courier/libexec/courier/aliasexp: fatal: libgcc_s.so.1: open failed: No such file or directory

I don't know what is this about. I guess it is connected with the following warning:

Typical Solaris nonsense. You have stuff installed in /usr/local, however Solaris's runtime linker does not search /usr/local.

You'll need to manually create a bunch of soft links from /usr/lib to /usr/local/lib.