Bug 163078

Description of problem:
This appears to be an older problem that continues to exist in RHEL4 (U1) for 
x86_64 (I found similar problems from a google search on "lgnat-3.4").

When trying to compile ADA code, I get a /usr/bin/ld error when gnatlink runs.

The easiest way to recreate the error is by using gnatmake.
i.e.

>gnatmake hello.adb
gcc -c hello.adb
gnatbind -x hello.ali
gnatlink hello.ali
/usr/bin/ld: cannot find -lgnat-3.4
collect2: ld returned 1 exit status
gnatlink: cannot call /usr/bin/gcc
gnatmake *** link failed


I believe one problem might be that /usr/lib/gcc/x86_64_redhat-
linux/3.4.3/adalib/libgnat-3.4.so (and libgnarl-3.4.so) are symbolically 
linked to /usr/lib64/libgnat-3.4.so.1 (and libgnarl-3.4.so.1), but these files 
don't exist in /usr/lib64.  The files do exist in /usr/lib, but if I relink 
the files to the /usr/lib location, I receive an incompatibility error 
(saying "/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64_redhat-
linux/3.4.3/adalib/libgnat-3.4.so when searching for -lgnat-3.4")


Version-Release number of selected component (if applicable):
Standard for RHEL4 (U1)
gcc-3.4.3-22.1
gcc-gnat-3.4.3-22.1

How reproducible:
Everytime

Steps to Reproduce:
1.Load RHEL4 (U1) - x86_64
2.Set up gcc to run ADA (gcc-gnat, etc.)
3.Try to build an executable from ADA.  

Actual results:

>gnatmake hello.adb
gcc -c hello.adb
gnatbind -x hello.ali
gnatlink hello.ali
/usr/bin/ld: cannot find -lgnat-3.4
collect2: ld returned 1 exit status
gnatlink: cannot call /usr/bin/gcc
gnatmake *** link failed

Expected results:
Should have created an executable

Additional info:
Although this issue doesn't cause "crashes, loss of data, or severe memory 
leaks", I placed this bug in high severity because we are unable to use these 
servers until ADA is working properly.