From mboxrd@z Thu Jan 1 00:00:00 1970 From: hjl@lucon.org (H.J. Lu) To: ghazi@caip.rutgers.edu (Kaveh R. Ghazi) Cc: egcs@cygnus.com Subject: Re: egcs needs a system.h? Date: Fri, 13 Feb 1998 10:58:00 -0000 Message-id: References: <199802131522.KAA04835@caip.rutgers.edu> X-SW-Source: 1998-02/msg00628.html > > > Any binaries generated during the stage 0 and executed during the > > stage 0 are for the build machine. Some binaries may have > > 2 copies, one for the host machine and the other for the > > build machine. They have to be compiled twice. It is very tricky. > > It took me a while to get it working. Read gcc/build-make may > > help a little bit. > > > > Here is my old patch. > > > > -- > > H.J. Lu (hjl@gnu.org) > > --- > > Fri Aug 15 17:47:14 1997 H.J. Lu (hjl@gnu.ai.mit.edu) > > > > * configure.in (--with-auto-config.h): New argument. Create > > auto-config.h and exit. > > (build-auto-config.h): Create it if the build machine is not > > the same as the host machine. > > (hconfig.h): Include build-auto-config.h if the build machine > > is not the same as the host machine. Otherwise include > > auto-config.h. > > HJ, > > I read gcc/build-make and I'm still not sure how a system.h > would conflict with anything you've mentioned. Let me be more explicit > about what I propose. Given any source file in gcc, they could do the > following: > > #include "the-appropriate-gcc-config-file.h" > #include "gansidecl.h" > #include "system.h" > #include "whatever-local-gcc-includes-you-want.h" > > I don't see this conflicting with your patch. Remember I'm not > proposing any *config.h file (host or build) include system.h directly, > (is that possibility what bothered you?) I'm saying that each individual > C source file would include the appropriate *config.h file and after > that would include system.h. I hope this allays your concerns. > It can work. H.J.