* John Polstra ([EMAIL PROTECTED]) [990731 09:28]:
> Jeroen Ruigrok/Asmodai wrote:
> > * John Polstra ([EMAIL PROTECTED]) [990729 18:49]:
> >>
> >> Right. So the problem must be that you have LD_LIBRARY_PATH set.
> >
> > Yes I have, but this hasn't been a problem for the last 5-6 months.
> > In what way could it interfere with my ldconfig then? (I read man 1aout ld)
>
> It won't intefere with ldconfig, but it will affect what the dynamic
> linker does. If you have "/usr/lib" in your LD_LIBRARY_PATH then the
> dynamic linker will find libc there, rather than in "/usr/lib/aout" as
> it should.
Ah, ok, I was thinking in the wrong direction.
The main reason I stuck LD_LIBRARY_PATH in there is because of Qt.
If ldconfig paths are configured ok, will these replace LD_LIBRARY_PATH
or would I have to adjust Makefiles/configures in order to point to the
libraries present on this system?
> I don't know why it didn't cause problems for you earlier.
Well, I am glad it broke... Because else I would still be using this.
> This was netscape, right? If so, there's an easy fix. The command
> that you execute for netscape is really a shell script which does
> some stuff and then executes a big binary somewhere else. You could
> add "unset LD_LIBRARY_PATH" to that shell script to work around the
> problem.
Mayhaps, but I would rather tackle the whole of this challenge instead
of just a subset. I mean if this LD_LIBRARY_PATH I set is a bad thing
to do I want to learn the ways how to best do it instead.
--
Jeroen Ruigrok van der Werven asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist BSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
