Mailinglist Archive: opensuse (1983 mails)

[hekate@xxxxxxxxxxxxxxx (Michael Johnson)]

Hi, 

On Fri, 11 Dec 1998, W.D.McKinney wrote:
> Except that there has yet to be an e-mail with instructions on how to load
> SO5 with SuSE 5.3 and not hose ld.so ? If you follow the instructions it writes over
> you ld.so config and hoses compiling capabilities. 

_No it doesn't_ hose compiling capabilities. I have running SO5 here and I
have compiled and linked with perfect success tons of apps since then,
namely cvs E, new leafnode,
new licq, new fetchmail, esd, etc etc etc. It says if you have
incompatible
^^^^^^^^^^^^
glibc2 versions and you don't, cause S.u.S.E. is a libc5 system 
^^^^^^
...the only glibc stuff you would have
is the shlibs stuff which isn't even a compiling and liking lib is it? All
that does is support running binaries already made that were linked with
glibc. 

I think they were referrring to systems with older native glibc2 as
the default breaking- not libc5 systems.

Look at this: 

blaze # cd /lib 
blaze # ls -al ld-li*
blaze # 
ld-linux.so.1 ->ld-linux.so.1.9.9.
ld-linux.so.2 ->ld-2.0.7.so

blaze # rpm -qf ld-linux.so.1.9.9
blaze # ldso-1.9.9-6
blaze # rpm -qf ld-2.0.7.so
blaze # file ld-2.0.7.so is not owned by any package

On my system I still have the ld stuff that came with S.u.S.E.
_and_ the ld-2.0.7.so that came with SO5.  These ( so far ) simply
coexisting. The SO5 linker didn't _replace_ the other one at all nor did
it rewrite ld.so.conf, which required me to add the libs _manually_ for it
to work

I think you are confusing what would happen if you had two glibc2's
installed and you don't. If you read the first README  the only systems
that would have glibc already on board  are RH and Deb and not a single
dist is listed ( even the glibc
ones ) as having conflicting glibc2 problems during installation.

If I'm wrong then I will eat crow, but I think you just
misunderstood/misread what was in the docs. You can't have a glibc2
linking conflict because you don't have a glibc2 system or a glibc2 linker
already onboard to create the conflict between the two glibc2's. You will
end up with their linker for glibc2 there, and having to add the libs to
your libpath through LD_LIBRARY_PATH or through adding the path of where
you installed them to ld.so.conf and then running ldconfig.  

Bye, 

M

-
To get out of this list, please send email to majordomo@xxxxxxxx with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/";><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html";><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>