RE: FW: Follow up: 2.1.4, solaris 8, fails to start

[Andrew Diederich <andrew@NETdelivery.com>]

Crle is behaving in ways I didn't expect.  Below are a commented out "what
crle tells me right now", a crle command I run, and then the output of crle
again.  It does the : thing by itself.  I'm still building with your last
suggestion, after the make distclean.

#andrew@lindstrom:/var/src/openldap-2.1.5 > crle
#
#Configuration file [3]: /var/ld/ld.config
#  Default Library Path (ELF):
/usr/lib:/usr/local/BerkeleyDB.4.0/lib:/usr/local/ssl/lib:/usr/local/lib:/us
r/lib/sasl2
#  Trusted Directories (ELF):    /usr/lib/secure
#
#Command line:
#  crle -c /var/ld/ld.config -l
/usr/lib:/usr/local/BerkeleyDB.4.0/lib:/usr/local/ssl/lib:/usr/local/lib:/us
r/lib/sasl2 -s /usr/lib/secure

# Now, do a new crle as root:

crle -l /usr/lib -l /usr/local/BerkeleyDB.4.0/lib -l /usr/local/ssl/lib \
-l/usr/local/lib:/usr/lib/sasl2 \
-s /usr/lib/secure

# show running crle again:
andrew@lindstrom:/var/src/openldap-2.1.5 > crle

Configuration file [3]: /var/ld/ld.config
  Default Library Path (ELF):
/usr/lib:/usr/local/BerkeleyDB.4.0/lib:/usr/local/ssl/lib:/usr/local/lib:/us
r/lib/sasl2
  Trusted Directories (ELF):    /usr/lib/secure

Command line:
  crle -c /var/ld/ld.config -l
/usr/lib:/usr/local/BerkeleyDB.4.0/lib:/usr/local/ssl/lib:/usr/local/lib:/us
r/lib/sasl2 -s /usr/lib/secure

-----Original Message-----
From: Igor Brezac [mailto:igor@ipass.net]
Sent: Wednesday, September 25, 2002 13:50
To: Andrew Diederich
Cc: 'openLDAP (E-mail)'
Subject: RE: FW: Follow up: 2.1.4, solaris 8, fails to start



On Wed, 25 Sep 2002, Andrew Diederich wrote:

> crle _says_ I ran it with this command:
> Command line:
>   crle -c /var/ld/ld.config -l
>
/usr/lib:/usr/local/BerkeleyDB.4.0/lib:/usr/local/ssl/lib:/usr/local/lib:/us
> r/lib/sasl2 -s /usr/lib/secure
>
> but I distinctly remember doing many -l flags, and then being surprised
when
> it concatenated them together.
>
> I re-did my little set file with multiple -L and -R flags, and I'm trying
a
> compile now.  I had found that with -I I needed to use a -I for each dir,
> but it seemed to work ok before with a single.  That, and crle really
seemed
> to want to separate the paths with a ":".
>

Here is what man page says.  You need to use multiple -l's.

     -l dir
           This option specifies a new default  search  directory
           dir   for  standard  ELF  or  AOUT  objects.  Multiple
           occurrences of this option are permitted. The type  of
           object  applicable  to  the search is specified by the
           preceding -t option, or defaults to ELF.

Note that my build suggestion should work without crle.

> Just curious -- why don't you do a "make depend"?  I don't remember which
> way the documentation specified, but after ./configure it tells you to do
> that first.
>

You can run make depend; this is mostly helpful for developers.

-Igor