Mail Archives: djgpp/2002/03/31/23:38:27
On Sun, 31 Mar 2002, deckerben wrote:
> I found that I had to change also my C:\WINNT\SYSTEM32\config.nt to echo the
> same parameters:
> FILES=255
> This made the real difference!
Thanks for the info, I will add it to the next edition of the FAQ.
> d:/user/djgpp/bin/sh.exe ../../../gcc/fixinc/genfixes machname.h
> -uDas System kann die angegebene Datei nicht finden.
> gcc -c -DIN_GCC -DHAVE_CONFIG_H -DIN_GCC -g -W -Wall -Wwrite-strings -Wstrict-pr
> ototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONF
> IG_H -DGENERATOR_FILE -DSEPARATE_FIX_PROC -W -Wall -Wwrite-strings -Wstrict-pro
> totypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -I. -I.. -I.
> ./../../gcc/fixinc -I../../../gcc/fixinc/.. -I../../../gcc/fixinc/../config -I..
> /../../gcc/fixinc/../../include ../../../gcc/fixinc/fixincl.c
> In file included from ../../../gcc/fixinc/fixincl.c:24:
> ../../../gcc/fixinc/fixlib.h:34:22: machname.h: No such file or directory (ENOENT)
> ...
>
> </output>
>
> I looked at the script "..gcc/fixinc/genfixes" ...and saw that it called for
> AUTOGEN. I looked for AUTOGEN but only found source code.
>
> I downloaded the source code for AUTOGEN.
No, no, no, this is a wrong way. You don't need autogen to build GCC:
the results of running autogen are already in the distribution. I don't
remember the details, but the fixincl program should just build and run,
using the files and scripts that are in the distribution.
So some other factor is at work here. Perhaps the time stamp of some
file is incorrect, and that causes the build process to want to remake
its dependencies. Please look closer at this step; there should be no
need to rerun genfixes at all.
- Raw text -