Thread View: gnu.gcc.help
1 messages
1 total messages
Started by Willard S. Akers
Tue, 29 Dec 1992 06:19
Compiling GCC on SYSVr3.2 (att i386)
Author: Willard S. Akers
Date: Tue, 29 Dec 1992 06:19
Date: Tue, 29 Dec 1992 06:19
24 lines
1873 bytes
1873 bytes
I'm having problems making GCC on our AT&T SYSV machine. I ran configure with this system arguement: i386-att-sysvr3 Then I got the first stage compiled using cc. Then when I tried to use xgcc to compile itself, it gave me some symbol referencing errors in the link stage. It could not find the symbols putc() and fseek(). It had the same problem when it try to compile the enquire.c program. I solved that problem by using CC to compile enquire instead of GCC. Unfortunately I can't get by with that at this point. When xgcc compiled itself, it does appear to link in the C library (I'm using the ld linker), so I *THINK* there error is in the stdio.h files declarations. I think the GCC must be defining some symbols that CC does not and therefore missing the declarations of fseek() and putc(). I just can't figure out what symbols these are! It could be __STDC__ or it might be __POSIX__ but I thought maybe someone else might have had this problem. I'm not sure what version of CC we have installed. If anyone could help me, I would greatly appreciate it. I got the dern compiler to compile things like tinymud which require an ANSI compliant compiler (as CC is not compliant). Now I am stuck trying to get GCC to compile when what I really want to compile can't be until I'm successful with GCC. Steve
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads