Kevin Ryde <[EMAIL PROTECTED]> writes: > Andreas Vögele <[EMAIL PROTECTED]> writes: >> >> gen-scmconfig.$(OBJEXT): gen-scmconfig.c >> $(CC_FOR_BUILD) $(DEFS) $(INCLUDES) -c -o $@ $<; > > Yep, I'd been meaning to do that. But probably omitting $INCLUDES, > since they're likely to be host-system things, not build-system. > $DEFS probably only has -DHAVE_CONFIG_H, and may be unnecessary too. > > One thing for a proper cross-compile is to figure out > $OBJEXT_FOR_BUILD, which may be different from the host system. I'd > planned to go straight to an executable rather than through an obj.
I can't recall offhand. Is CC_FOR_BUILD for executables that will be run on the host system? If not, then we shouldn't be using it at all. gen-scmconfig has to be run at build time by the host to generate the header, so it needs to be built by the host's compiler. Note that gen-scmconfig.c doesn't (and must not) depend on any target specific computations like sizeof(foo), etc. It is solely used as a portable way to generate scmconfig.h, taking into account the contents of config.h. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Bug-guile mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-guile