Article View: gnu.gcc.bug
Article #6352Strange behaviour during build of 2.7.2
From: Colin Eric Johnson
Date: Sat, 02 Dec 1995 00:00
Date: Sat, 02 Dec 1995 00:00
53 lines
3032 bytes
3032 bytes
While doing the stage 1 build of GCC I got the following from make which didn't seem "normal." the first section is the last actual command that make executed before printing the middle section about 20-30 times. Finally it stopped printing the message about processing header files and completed the build starting with the third section below. Is this normal behaviour? This build is happening on a NeXT 68040 running NS 3.2. # #This is the last visible act of compilation before the "strange #behaviour" started # cc -traditional-cpp -DIN_GCC -g -o fix-header fix-header.o scan-decls.o scan.o cpplib.o cpphash.o cppalloc.o version.o cppexp.o ` case "obstack.o" in ?*) echo obstack.o ;; esac ` ` case "cc -traditional-cpp"@"" in "CC -traditional-cpp"@?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` if [ -f fixhdr.ready ] ; then true; else touch fixhdr.ready; fi Various warnings and error messages from fixproto are normal if [ -d include ] ; then true; else mkdir include; fi if [ -f include/fixed ] ; then true; else : This line works around a 'make' bug in BSDI 1.1.; FIXPROTO_DEFINES=""; export FIXPROTO_DEFINES; /bin/sh ./fixproto include include /usr/include; touch include/fixed; fi fixproto: populating `include' # #This is the message that was printed ~20-30 times # The fact that a certain header file need not be processed more than once should be indicated in the header file, not where it is used. The best way to do this is with a conditional of this form: #ifndef _FOO_H_INCLUDED #define _FOO_H_INCLUDED ... <real contents of file> ... #endif /* Not _FOO_H_INCLUDED */ Then users can use `#include' any number of times. GNU C automatically avoids processing the file more than once when it is equipped with such a conditional. # #Once it stopped it continued on in what seemed to be a sane manner #is this "normal" behaviour that isn't documented? # Adding missing unistd.h fix-header: fixing unistd.h touch stmp-fixproto rm -f cxxmain.c ln -s ./cplus-dem.c cxxmain.c > /dev/null 2>&1 || cp ./cplus-dem.c cxxmain.c cc -traditional-cpp -c -DMAIN -DIN_GCC -g -I. -I. -I./config -DVERSION=\"2.7.2\" cxxmain.c -- "As Jun [Murai] explains it, `I can go to the bar and drink beer. I go to a phone and ping my routers, and if they are still working, I go back and drink more beer.'" Carl Malamud _Exploring_the_Internet_ Colin Johnson | colinj@umich.edu | http://www.itd.umich.edu/~colinj/
Technical Details
Message-ID:
<49q682$bht@lastactionhero.rs.itd.umich.edu>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 113d02,f438b49c8c024dd6,start X-Google-Attributes: gid113d02,public From: colinj@stimpy.us.itd.umich.edu (Colin Eric Johnson) Subject: Strange behaviour during build of 2.7.2 Date: 1995/12/02 Message-ID: <49q682$bht@lastactionhero.rs.itd.umich.edu> X-Deja-AN: 120710888 distribution: gnu sender: daemon@cis.ohio-state.edu organization: University of Michigan, Operations Management reply-to: "Colin E. Johnson" <colinj@umich.edu> newsgroups: gnu.gcc.bug