djones@decwrl.dec.com (Dave Jones) (11/21/90)
I hope someone can help me with a problem I'm having porting software from Sun's release-3 running on mc68020's to release-4 running on same. I have a couple of compilers, one derived from the original BSD compiler, the other written in-house. (No, we can't just use the Sun compilers. -- It's a long story.) Anyway, they both produce dot-o files which the release-3 linker likes just fine. But according to accounts of fellow engineers, Sun's release-4 linker sometimes complains about them and crashes. I've heard of messages about a "pc-relative symbol botch" and also "symx botch". We can link these files with the release-3 linker using the release-4 libraries and they run fine under release-4. (I've requested example programs which demonstrate the problem. None yet. Soon.) I have been aware for some time that the same binaries will not necessarily run under both releases. That is bad enough if you have machines running both releases. But this is even worse: I can't convert to release-4 because the new linker breaks my compilers. What the heck is going on? What changed? Is it a bug in the release-4 linker? (I would say, yes.) If so, will it be fixed? In any case, how do I build the .o's differently so that the new linker will take them? If you have a clue on this, please give me a call or drop me a line. I will be more than happy to return a favor. We might even work out some kind of consulting deal if you know where all the bodies are buried. -- Dave (408) 437 9700 Ext 3227 sun!megatest!djones