Article View: gnu.misc.discuss
Article #74908Re: SCO-GCC mailing list ??
From: Bill England
Date: Thu, 24 Jan 1991 20:13
Date: Thu, 24 Jan 1991 20:13
67 lines
3408 bytes
3408 bytes
In article <1991Jan23.173137.18956@vlsi.polymtl.ca> scoob@vlsi.polymtl.ca (Christian Marcotte) writes: > > I'm new to SCO world (was working with Sun before). > I was wondering if all the gnu stuff (mainly bison, gas, gcc/++, gdb) > compiled directly on SCO UNIX (or Xenix) ?? > > If not, where can I get the appropriate patches ? > Ideally SCO UNIX would be as generic as any other flavor of Unix and NOT require specific patchs and hoop jumping to make your favorite software (Gnu everything :-) ) work. Unfortunately this is not quite the case with SCO. There are several hurdles to get gcc to work. Then more problems getting g++ to work. To date I've been able to get gcc 1.37.1 working on ODT 1.0. I have not been able to make gas 1.36 work with the gcc compiler however. ( The 1.37 gcc compiler still sometimes produces instructions that the att assembler does not grok, you can work around it. - this is all SCO-ODT 1.0 ) I believe that latest version of gcc is 1.39, gas is 1.37, and g++ is 1.37.1. _Patches/Developments_ SCO specific ... Tim Iversion, uunet!xstor!iverson, 21 Jan 91, gnu.gcc.help; > patches to make gcc 1.39 work > under SCO with gas 1.37 exist and, pending approval from the authors of the > patches (I didn't write 'em, I just ported 'em), will be made available > soon (a week from now at the latest). Chip Salzenberg, chip@tct.uucp, 5 Jan 91, comp.unix.sysv386; > here is the NEW AND IMPROVED patch for GCC/G++ for > functions returning structures in the Microsoft style, for use with > SCO UNIX system libraries. Most of the smaller utilities (bison etc ) do not require any special changes. Use rcc (AT&T compiler) and not cc (Microsoft) because cc truncates variable and function names longer than about ~20 chars. Also, don't use -O with rcc. Once you get gcc compiled you can recompile your utilities with it. __ ODT/SCO versions __ The real meat of the problem is the SCO OS version you are running. ODT 1.0 has an OS '3.2 2 i386'. The latest SCO Unix (and the one included in the next ODT 1.1 release in march) is '3.2v2 i386'. The only difference in the name is the 'v'. This indicates significant improvements in the ODT software however. I believe that Chip's g++ patches are for a 3.2v2 release. I'm not sure if you can get g++/libg++ running on straight ODT 1.0. If anyone has I'd be interested in hearing about it. -- +- Bill England, wengland@stephsf.COM -----------------------------------+ | * * H -> He +24Mev | | * * * ... Oooo, we're having so much fun making itty bitty suns * | |__ * * ___________________________________________________________________|
Technical Details
Message-ID:
<463@stephsf.stephsf.com>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!stephsf!wenglandReferences:
<461@stephsf.stephsf.com> <1991Jan23.173137.18956@vlsi.polymtl.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,4e0ca0e1f198a2a4,start X-Google-Attributes: gid1025b4,public X-Google-ArrivalTime: 1991-01-25 02:13:35 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!stephsf!wengland From: wengland@stephsf.stephsf.com (Bill England) Newsgroups: gnu.misc.discuss Subject: Re: SCO-GCC mailing list ?? Message-ID: <463@stephsf.stephsf.com> Date: 24 Jan 91 20:13:36 GMT References: <461@stephsf.stephsf.com> <1991Jan23.173137.18956@vlsi.polymtl.ca> Organization: Stephen Software Systems, Inc., Tacoma WA Lines: 67