Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!wuarchive!texbell!texsun!pollux!txsil!steve From: steve@txsil.lonestar.org (Steve McConnel) Newsgroups: gnu.gcc.bug Subject: Re: porting GCC to SCO UNIX V/386 (3.2) Summary: tm-i386v.h works okay without gas Message-ID: <265@txsil.lonestar.org> Date: 2 Jan 90 01:56:38 GMT References: <8912312116.AA12256@ucscc.UCSC.EDU> Reply-To: steve@txsil.lonestar.org (Steve McConnel) Distribution: gnu Organization: Summer Institute of Linguistics, Dallas TX Lines: 37 In article <8912312116.AA12256@ucscc.UCSC.EDU> sef@kithrup.com (Sean Eric Fagan) writes: >>Has anyone successfully ported gcc to SCO UNIX V/386? i've spent this week >>working on it, learning more about COFF (and a.out) format than i ever wanted >>to know, but still nothing works. > >Yes, I have (and also moved the resultant binary to my xenix machine). As >you point out, I compiled it with the AT&T compiler (rcc), for various >reasons (didn't trust cvtomf at the time, mostly). i don't trust cvtomf at all -- the only use i make of the Microsoft compiler (cc) is to cross-compile for MSDOS. (the cross-compiler is one of the major reason the department that owns the system bought SCO UNIX rather than any of the alternatives they considered when our 68020 BSD box died last summer.) > . . . > Something else you may have run into, but >didn't mention, was that one of the sys files (/usr/include/sys/???.h) >defines FFS: in this case, it means 'Fast File System,' but gcc wants the >same symbol for Find-First-Set-bit. Anyway, I *think* it's one of the files >in , but I'm not sure which one. I sent RMS off a note about it, >saying that I thought it was happening because of , but it's >been a while, so I'm not sure. Thanks for the response (thanks also to those who replied via email). I did have to fiddle with the definition of FFS, now that you mention it. It turns out that i was using the tm-i386v.h configuration, and trying to use gas. Silly me. At the moment, I'm using COFF all the way, with the AT&T assembler and linker. This seems to work okay. Of course, as i understand the installation instructions, this also precludes gdb :-(. If i have time, i'll see if the COFF encapsulation works any better with tm-i386gas.h, but at least now i have a working gcc, and can take a look at g++ now. -- Stephen McConnel Summer Institute of Linguistics PHONE: 214-709-2418 7500 W. Camp Wisdom Road UUCP: ...!{texbell|convex|pollux}!txsil!steve Dallas, TX 75236 Internet: steve@txsil.lonestar.org