Chris Carlen wrote:
2. The eagle program is installed in /opt/eagle/bin:
~ $ ls -l /opt/eagle/bin/eagle -rwxr-xr-x 1 root root 3924300 May 30 1999 /opt/eagle/bin/eagle
3. Trying to run the program using the direct path also fails:
~ $ /opt/eagle/bin/eagle bash: /opt/eagle/bin/eagle: No such file or directory
The error messages above were very puzzling, sending me on a wild goose chase. The cause of the problem was that I satisfied lib deps for eagle when installing the software by installing the package shlibs5 from a Suse 6.2 onto the Suse 7.0 distro. Since no error messages ever occured indicating that libraries were missing, I didn't suspect anything was wrong with the shlibs5. In fact, I verified by hand that every lib eagle wants was indeed present and in the ld.so.cache on Suse 7.0. So why didn't eagle work??? The reason is that the Suse 7.0 linker/ldd programs don't recognize the libc5 stuff. The shlibs5 package from Suse 7.0 contains special stubs for ldd and an additional ldd-libc5 binary that make it all work. Installing the shlibs5 from 6.2 onto 7.0 was a recipe for extreme confusion. Major oops--but I'm happy as hell that I can run my program now! _____________________ Christopher R. Carlen crcarl@inreach.com Linux 2.2.10