Error running Maple 7 on Fedora 10

[William M. Quarles]

Ed Greshko wrote:
> William M. Quarles wrote:
>> Tony Nelson wrote:
>>> On 09-06-22 17:49:47, William M. Quarles wrote:
>>>> Tony Nelson wrote:
>>>>> On 09-06-22 04:36:52, William M. Quarles wrote:
>>>>>> Mike Cloaked wrote:
>>>>>>> William M. Quarles-2 wrote:
>>>>>  ...
>>>>>>>> OK, yes, I know this technically shouldn't work but a hack or
>>>>>>>> two on thescripts that start Maple 7 and installing
>>>>>>>> compat-libstdc++-296-2.96-135 from Fedora Core 5 make it work I
>>>>>>>> understand.
>>>>>>> Possibly packages compat-libstdc++-33 and libXp may be needed?
>>>>>> Did you read the error message that I had posted? The files that
>>>>>> cannot be found are from glibc-2.9-3, yet they are installed.
>>>>> Possibly it is a library search path problem?  See `man ldconfig`
>>>>> and ld.so.conf and ld.so.conf.d/.
>>>>>
>>>> I think that you are right, but I'm not exactly sure what to do about
>>>> it.
>>>>
>>>> I ran '/sbin/ldconfig', no help. I tried adding /usr/local/lib/ to
>>>> that command line in order to be sure that my relocated compat
>>>> libraries were found.
>>>>
>>>> [root at quarlewm2 bin]# cat /etc/ld.so.conf
>>>> include ld.so.conf.d/*.conf
>>>  ...
>>>
>>> FWIW, when I needed to I just added "/usr/local/lib" at the top of
>>> /etc/ld.so.conf, like the various files in /etc/ld.so.conf.d/, and
>>> then ran `ldconfig` (no options or paths).
>>>
>> I don't know what "FWIW" means (for what it's worth?), but thanks for
>> the info. However, the error message "dirname: error while loading
>> shared libraries: libc.so.6: cannot open shared object file: No such
>> file or directory" still appears no matter what I try. Also since this
>> error started, I cannot get Gnome-Package-Kit Application
>> (gpk-application) to get past "Waiting for service to start" once I
>> have told it which packages to install.
>>
>> Peace,
>> William
>>
> If you know what binary is issuing the error message you can....
> 
> readelf -d <binary> | grep RPATH
> 
> to determine the library path of the binary.
> 
> I've also found that "ldd -v <binary>" is helpful in tracking down
> problems in that area.
> 

I'm not exactly sure what definition you are using for "binary" in this 
case. The binary programs that are issuing the error messages are bash 
and dirname. The binary libraries that are mentioned in the error 
messages are libc.so.6 and libdl.so.2. Could you be more specific as to 
what you mean by "binary" in this case?

Thanks,
William