Can't find libgcc after building 1.4.1

[vadim]

In fact, it comes now into my mind, I had similar problems with earlier
versions of MIT kerberos ... even if setting LDFLAGS properly I could
not link binaries properly. As far as I can remember guys applied an
effort in their configure stuff to ignore all environmental settings ...

It is probably not possible to link MIT executables on solaris without
changing makefiles. Sorry.

Best regards, vadim tarassov.

On Thu, 2005-08-04 at 14:31 +0200, vadim wrote:
> Hallo,
> 
> setting LD_LIBRARY_PATH env variable you tell where to look for shared
> object libraries. It looks like you set it in your sheel, but once you
> su'ed, LD_LIBRARY_PATH became unset. Setting LD_LIBRARY_PATH is in
> general bad idea, because you will always have to care if it is set or
> not (what you have posted is the best example for what I am saying).
> Setting LD_LIBRARY_PATH for root is even worse idea for reasons, which
> should be explained in Solaris or UNIX security cources.
> 
> Best what you could do
> 
> 1) read man ld about -R option
> 2) set env variable LDFLAGS="-R/usr/local/lib" for configure, i.e.
> execute configure like
> 
> LDFLAGS="-R/usr/local/lib" ./configure --bla-bla
> 
> Best regards, vadim tarassov.
> 
> On Wed, 2005-08-03 at 17:02 -0700, Mike Friedman wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > I have an update to my earlier posting, because it was in error. (For one 
> > thing, after setting LD_LIBRARY_PATH in my configure script and compiling, 
> > I inadvertently tried the 'make install' without first becoming root).
> > 
> > Actually, these are my symptoms:
> > 
> > o  I build and install krb5-1.4.1 (this is Solaris 9)
> > 
> > o As root, I find that when I run the installed kinit, I get this message:
> > 
> >     ld.so.1: kinit: fatal: libgcc_s.so.1: open failed: No such file or directory
> > 
> > However, when I exit from my root shell, as my own userid, I don't get 
> > that error message.  Similarly, under my own userid, ldd shows everything 
> > as OK;  in particular, I get this entry:
> > 
> >     libgcc_s.so.1 =>         /usr/local/lib/libgcc_s.so.1
> > 
> > whereas, as root, ldd shows this:
> > 
> >     ...
> >     libgcc_s.so.1 =>         (file not found)
> >     libgcc_s.so.1 =>         (file not found)
> >     libgcc_s.so.1 =>         (file not found)
> >     libgcc_s.so.1 =>         (file not found)
> >     libgcc_s.so.1 =>         (file not found)
> >     libgcc_s.so.1 =>         (file not found)
> >     ...
> > 
> > So, why the error in resolving libgcc only when I'm root? (And why the 
> > multiple 'not found' messages?).
> > 
> > Mike
> > 
> > ===========================================================================
> > >>> OK, now I've built 1.4.1 on Solaris 9 and I have this problem:
> > >>> 
> > >>> The compile (and install) seems to have gone well.  But when I try to 
> > >>> run kinit, I'm told this:
> > >>> 
> > >>>  ld.so.1: kinit: fatal: libgcc_s.so.1: open failed: No such file or 
> > >>> directory
> > >>> 
> > >>> I subsequently ran 'make check' and also got a message about 
> > >>> libgcc_s.so.1 not being found.  But that library does exist and is in 
> > >>> /usr/local/lib.
> > >>> 
> > >>> ... 
> > >>> When I run ldd on, for example, the newly-installed kinit, I get this:
> > >>> 
> > >>>    libkrb4.so.2 =>  /usr/local/krb5-1.4.1/lib/libkrb4.so.2
> > >>>    libdes425.so.3 =>        /usr/local/krb5-1.4.1/lib/libdes425.so.3
> > >>>    libkrb5.so.3 =>  /usr/local/krb5-1.4.1/lib/libkrb5.so.3
> > >>>    libk5crypto.so.3 =>      /usr/local/krb5-1.4.1/lib/libk5crypto.so.3
> > >>>    libcom_err.so.3 =>       /usr/local/krb5-1.4.1/lib/libcom_err.so.3
> > >>>    libkrb5support.so.0 =>   /usr/local/krb5-1.4.1/lib/libkrb5support.so.0
> > >>>    libresolv.so.2 =>        /usr/lib/libresolv.so.2
> > >>>    libsocket.so.1 =>        /usr/lib/libsocket.so.1
> > >>>    libnsl.so.1 =>   /usr/lib/libnsl.so.1
> > >>>    libc.so.1 =>     /usr/lib/libc.so.1
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libgcc_s.so.1 =>         (file not found)
> > >>>    libdl.so.1 =>    /usr/lib/libdl.so.1
> > >>>    libmp.so.2 =>    /usr/lib/libmp.so.2
> > >>>    /usr/platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1
> > >>> 
> > >>> Notice that there's no problem resolving the Kerberos libraries. 
> > >>> Only libgcc seems to have a problem.
> > ...
> > 
> > _____________________________________________________________________
> > Mike Friedman                   System and Network Security
> > mikef at ack.Berkeley.EDU          2484 Shattuck Avenue
> > 1-510-642-1410                  University of California at Berkeley
> > http://ack.Berkeley.EDU/~mikef  http://security.berkeley.edu
> > _____________________________________________________________________
> > 
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGP 6.5.8
> > 
> > iQA/AwUBQvFbHa0bf1iNr4mCEQLCQQCeM037U2E6YoxxM72jUcIFgb6YN84Anjyb
> > PSgDqsLUwJlmBjWR3RMajbUb
> > =swwV
> > -----END PGP SIGNATURE-----
> > ________________________________________________
> > Kerberos mailing list           Kerberos at mit.edu
> > https://mailman.mit.edu/mailman/listinfo/kerberos
-- 
vadim <vadim.tarassov at swissonline.ch>