🚀 go-pugleaf

Keywords: 

versions: gcc 2.4.3.1 gas 2.1.1 binutils 2.2.1

 Okay, I posted a while ago about a cross compiling environment for a mips to
 m68k cross compiler. Anyways, since then I made some progress. Namely, since
 there happens to be an hp sitting around, I thought I would try a cross to 
 it first. Once again, I'm halfway through compiling gcc -- i.e. a working xgcc.
 xgcc produces okay assembly. gas produces an okay object file. the linker,
 however, bombs out with a message IOT Instruction. I traced it to an abort call
 inside the linker code (bfd/aoutx.h). It seems, though, that the reason it 
 aborted was that the entry cache_ptr->symbol.section was (nil), which the 
 condition for the abort. So I tried to link on an object file produced natively
 on the hp. That link only complained about an undefined symbol, but did not 
 trap out. So that leads me to believe the problem might be in the assembler,
 and taking a look at the hp native object file and the cross assembled file
 shows a few discrepencies (granted there should be anyway). yet both the 
 gas assembler and gld were configued for target=hp300hpux. Am I missing 
 something here? Is there something about the hp config files that's plain
 screwy?

--dan