problem building pg 7.3 beta 3 on solaris 8 -m64

make[2]: Entering directory  
`/data/aja96/postgresql-7.3b3/src/backend/utils/mb/conversion_procs'
make[3]: Entering directory  
`/data/aja96/postgresql-7.3b3/src/backend/utils/mb/conversion_procs/ 
ascii_and_mic'
gcc -shared -h libascii_and_mic.so.0 ascii_and_mic.o  
-L../../../../../../src/port   -o libascii_and_mic.so.0.0
ld: fatal: library -lgcc_s: not found
ld: fatal: library -lgcc_s: not found
ld: fatal: File processing errors. No output written to  
libascii_and_mic.so.0.0
collect2: ld returned 1 exit status
make[3]: *** [libascii_and_mic.so.0.0] Error 1
make[3]: Leaving directory  
`/data/aja96/postgresql-7.3b3/src/backend/utils/mb/conversion_procs/ 
ascii_and_mic'
make[2]: *** [all] Error 2
make[2]: Leaving directory  
`/data/aja96/postgresql-7.3b3/src/backend/utils/mb/conversion_procs'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/data/aja96/postgresql-7.3b3/src'
make: *** [all] Error 2

Darcy explained that it might be a problem with gcc 3.1, and that i  
should upgrade to 3.2. The compile line from the makefile  is actually:

gcc -shared -h libascii_and_mic.so.0 ascii_and_mic.o  
-L../../../../../../src/port   -o libascii_and_mic.so.0.0

While attempting to compile gcc 3.2, I found a bug in the build process  
(which i have corrected, bug report to gcc folks on its way). I'll  
report back after that. I think however, this is a gcc bug (that will  
because of the bug I just found) be present in 3.2. The problem is that  
when gcc is built, the directory $build_dir/gcc/sparcv9 does not  
include the following two symlinks:

lrwxrwxrwx   1 aja96    atd           13 Nov  6 16:23 libgcc_s.so ->  
libgcc_s.so.1
lrwxrwxrwx   1 aja96    atd           13 Nov  6 16:25  
libgcc_s_sparcv9.so -> libgcc_s.so.1

(note:  -rwxr-xr-x   1 aja96    atd       512136 Nov  6 14:12  
libgcc_s.so.1)

creating those symlinks (and adding the dir to LD_LIBRARY_PATH, but in  
retrospect i think it was unnecessary) allows it to continue compiling  
(gcc). I havent figured out where those are fubar on the system yet,  
I'm sure somebody here does; I'm going to get gcc 3.2 built and see if  
this fix fixes the pg compile. Some sort of logic understanding this  
buggery should probably incorporated into the release.

i've included my home address on CC, please maintain that CC. my  
contract here is up in a couple weeks, and i will have limited access  
to the address currently subscribed to hackers.

thanks
alex