Thanks for your reply David, >> Much easier for me would be to have access to the objects of >> libgortran.a compiled as PIC. I don't care for many parts of >> the .so because the code runs only as a library. >> >> >> Does it make sense? > > I understand what you are saying, but I don't necessarily > agree that it is the 'right thing to do'. It is the best solution I could find. I would love to hear a better idea because there is something illogical about this "fix", but still, it seems to be the smallest evil. >The object files you need exist somewhere in the gcc build > tree (but not in any archive), you need to figure out how > to get them out. It seems like they are in "objdir"/x86_64-xxx-gnu/libgfortran. Unfortunately, the .o do not seem to be build with as PIC and the .lo do not seem to be digestible by g++, gcc. So I don't know how to coax them into a dyn lib. This why I thought to rebuild the gfortran's .o with -fPIC, but got baffled by Makefiles and config files. I could not find any mention of it anywhere. Any ideas? Thanks again, and sorry for taking up so much bandwidth, I hope it is of some interest to other people as well. Lorenzo
