On Mon, 24 May 2004 11:04:58 -0500, Rolly wrote:
> Thx Methis, it's so kind of you giving me these info. As a newbie to
> Linux(FC2), I forgot to mention that I have not installed every rpms on
> the 4 CDs of Fedora Core 2 into my PC because of space concern. I have
> checked my system that glibc-2.3.3-27 and glibc-devel-2.3.3-27 are
> present.
Not a problem. I'm still learning too 😉 In regard to missing Fedora
packages, I wouldn't worry about it. If you weren't satisfying a labview
dependency, we would have seen it with the ldd command.
My concern is that you may have too much - as in too much new stuff. From
my limited knowledge of Fedora, I suggest you stay away from it unless you
like being a beta teste
r, constantly. This is why I prefer Slackware.
They make a new release approx every 6 months. The packages they use are
usually quite mature too.
> Do you mean "broken", I missed some rpm packages which is necessary to
> run LV70?
Nope, it looks like you have everything you need. I was thinking there
could be two problems:
1) Fedora has given you a version of glibc that is still
experimental and just simply doesn't work
2) This new version of glibc works fine (most likely) but is
incompatible with labview
> Do you mind listing all the relevant rpms you have on your system so I
> can compare and install the ones I missed? Hope this can solve the
> problem.
I can't do that coz I a dont' use rpms on Slackware 😉 Besides, I think
what you really need is a different version of glibc and glibc-solibs. I
recall trying to do this some time back... not very easy. I would try a
different Linux distribution, like Slackware or Debian.
Hmm, one possible solution ... to use
LV in it's most basic form, all you
have to install is the labview70-core package. Try uninstalling all the
other LV packages and only leaving this one. Then run LV and see if it
gives a similar error. I should have told you this in the beginning.
