home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!munnari.oz.au!metro!ipso!runxtsa!bde
- From: bde@runx.oz.au (Bruce Evans)
- Subject: Re: About the ACK ANSI compiler... [not the
- Message-ID: <1992Dec31.000517.11452@runx.oz.au>
- Organization: RUNX Un*x Timeshare. Sydney, Australia.
- References: <1992Dec30.052435.28478@udel.edu>
- Date: Thu, 31 Dec 92 00:05:17 GMT
- Lines: 28
-
- In article <1992Dec30.052435.28478@udel.edu> Damian McGuckin <damianm@eram.esi.com.au> writes:
- >
- >We just got GCC 2.3.2 and LIBG++ 2.3 off the Internet. It works beautifully
- >on our SUN and when we sort out the include directories in between all the
- >Christmas drinks, we have been told it should work quite well on BSDI.
- >
- >I noticed that minix on a 386 is one of the supported systems. Are we a chance
- >to getting 1.6.?? up and running with GCC? I think I have that quaint technique
-
- The 386 (in 32-bit mode) is not officially supported. However, I have been
- using gcc-1.39 through gcc-2.3.2 under Minix 1.6.1 through 1.6.16 over the
- last 2 years. It works better than on Suns because the headers are already
- mostly ANSI conformant. There is an old port of gcc-1.39 or 1.40 in the
- Minix archives (a complete package with binaries. The old binaries should
- still work under 1.6.any).
-
- >called ARLD on my 1.5 system - yuk! I think I read that the new release uses
-
- asld.
-
- >the more conventional way of handling libraries and loading objects, - ar & ld.
- >Does the new minix come with the source of both its AS (assembler), AR
- >(archiver) and LD (loader) or will I have to get the GNU equivalents
-
- The ANSI compiler (available at extra cost) uses a separate as and ld. These
- are completely incompatible with gnu as and ld (being for 16-bit code).
- --
- Bruce Evans (bde@runx.oz.au)
-