nhc@cbnewsj.ATT.COM (n.h.chandler) (02/01/90)
Help! I have uudecoded, unshared and checked the CRCs and file sizes for the 1.5.0 upgrade. I have accounted for all but one file in ASTs liborder list "_exit". Can some kind soul point me to it? I am having problems compiling the kernel and fs. "system.c" and "fsck.c" fail to compile. The compiler cannot find header files in the current directory and everything comes to a halt Any help in solving these problems wille elvis files and then asld bombs with an 'error writing code file -elvis removedd' message. The compiler also grinds through all the e appreciated. N. Chandler att.com!cbnewsnewsj!nhc asld bombs with 'error writing code file' '-elvis removed'
nhc@cbnewsj.ATT.COM (n.h.chandler) (02/02/90)
In article <3698@cbnewsj.ATT.COM>, nhc@cbnewsj.ATT.COM (n.h.chandler) writes: > > and "fsck.c" fail to compile. The compiler cannot find header > files in the current directory and everything comes to a halt > Any help in solving these problems wille elvis files and then > asld bombs with an 'error writing code file -elvis removedd' > message. > The compiler also grinds through all the e appreciated. > The plea for help was garbled. In fs, fsck.c failed to compile as did system.c in the kernel sub-directory. An 'out of memory' diagnostic was returned by the compiler. I also tried to compile elvis The compiler grinds through all the files, then asld bombs with '-error writing code file' ' elvis removed' Any help in resolving these problems will be greatly appreciated. N. Chandler
bc@ux1.cso.uiuc.edu (B.C.) (02/03/90)
In article <3709@cbnewsj.ATT.COM> nhc@cbnewsj.ATT.COM (n.h.chandler) writes: >> and "fsck.c" fail to compile. The compiler cannot find header >> files in the current directory and everything comes to a halt >> Any help in solving these problems wille elvis files and then >> asld bombs with an 'error writing code file -elvis removedd' >> message. >> The compiler also grinds through all the e appreciated. >> > >The plea for help was garbled. In fs, fsck.c failed to >compile as did system.c in the kernel sub-directory. >An 'out of memory' diagnostic was returned by the compiler. These are the *exact* same problems I had. Many many (many!) people told me to chmem various parts of the compiler, but that *did not help*. Anyone got any more suggestions? Ben b-cox2@uiuc.edu
linas@hpuarca.HP.COM (Linas Petras) (02/07/90)
Here are hopefully some answers to various questions that have been asked. The problem with the _exit.c function in lib/posix directory is one, that I beleive has been around for some time. If you look at the "run" script you will find that it is of the following format: for i in [a-z]*.c Just modify the run command to do an explict compile of _exit.c or just run the make command with the filename defined as follows: make f=_exit The problem with kernel/system.c and tools/fsck.c is that "cpp" and "cem" are running out of memory. You can increase their stack+heap areas with: chmem =45000 /lib/cpp chmem =45000 /lib/cem Note that this may cause problems for people with only 512K of memory as the programs now take up a little more memory when run. The problem with "elvis" from memory, is that the line in Makefile.pc should have seperate I&D during the link phase and it doesn't. Change the line to create the elvis target with the following two lines: elvis: $(OBJS) $(CC) -i -o elvis $(OBJS) $(EXTRA) $(LIBS) or just add the "-i" option in the above line to your version of the makefile. Hope this helps Linas Petras E-mail : linas@hparc0.HP.COM Standard Disclaimer......