home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!munnari.oz.au!uniwa!cujo!cc.curtin.edu.au!smackinl01
- From: smackinl01@cc.curtin.edu.au
- Subject: Re: GCC2.1 problems
- Message-ID: <1992Sep4.102238.1@cc.curtin.edu.au>
- Lines: 18
- Sender: news@cujo.curtin.edu.au (News Manager)
- Organization: Curtin University of Technology
- References: <1992Sep3.143004.9353@murdoch.acc.Virginia.EDU>
- Date: Fri, 4 Sep 1992 01:22:38 GMT
-
- Bill Pearson's problems may be related to the command line switches he was
- using. From memory, his problem was that "GCC filename" would fail. With the
- non-emx port, you need to use instead "GCC -c filename.c" to produce a x86
- specific object file instead of the unix .o format. GCCv2.2.1 seems to have
- difficulties creating object files in the .o format, so perhaps someone could
- clarify this?
-
- A suggestion also is to get the GCCv2.2.2 port - via anonymous ftp to
- ftp-os2.nmsu.edu in /pub/os2/2.0/programming if memory serves - as this has a
- few fixes for some serious bugs.
-
- BTW: Has anyone noticed that the GCCv2.2.2 present on hobbes is lacking some of
- its header files? These are (again, my memory isn't the best) the ones in the
- gcc-include/machine directory.
- --
- Simon.
- Have you got a form 27/b?
-
-