home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!iggy.GW.Vitalink.COM!cs.widener.edu!eff!sol.ctr.columbia.edu!usc!rpi!utcsri!newsflash.concordia.ca!mizar.cc.umanitoba.ca!access.usask.ca!kakwa.ucs.ualberta.ca!ee.ualberta.ca!charro
- From: charro@ee.ualberta.ca (Dan Charrois)
- Subject: GCC and streams
- Message-ID: <charro.722049463@ee.ualberta.ca>
- Keywords: GCC stderr streams
- Sender: news@kakwa.ucs.ualberta.ca
- Nntp-Posting-Host: bode.ee.ualberta.ca
- Organization: University Of Alberta, Edmonton Canada
- Date: Wed, 18 Nov 1992 01:17:43 GMT
- Lines: 22
-
- I have a question regarding the gcc compiler (2.2.2).
-
- Since no include files came with gcc, I told it to use those which
- came with Lattice C.. but I have a small problem...
-
- When trying to compile a simple program that just printed a message to
- stderr using fprintf, I got the message (during linking, I believe),
- that __iob wasn't defined anywhere. Looking at the stdio.h which came
- with Lattice, I see that stderr is &_iob[2], and _iob[] is itself
- declared as external. Therefore, I assume that Lattice is finding out
- where the standard streams are kept and returning the pointers through
- _iob. What's gcc's method?
-
- If anyone has any information on how to get gcc to understand what I
- mean by stderr, It would be great if you could help me out. (I
- imagine it has problems with stdin and stdout as well, though I
- haven't checked to be sure...)
-
- Thanks! Dan
- --
- Dan Charrois - University of Alberta, Electrical Engineering
- INTERNET: charro@bode.ee.ualberta.ca
-