Re: Native compilation on Windows, was Re: Bootstrap Compilation Speed

[Phillip Lord]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Phillip Lord <phillip.lord@russet.org.uk>
>> Cc: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>,  corwin@bru.st,
>>   emacs-devel@gnu.org
>> Date: Mon, 17 Jan 2022 09:39:34 +0000
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> I could build Gnu-Emacs-28.0.91 when I used the archived sources
>> >> 
>> >>   $ ./configure --with-native-compilation
>> >> 
>> >> The difference to the build-zips.sh seems to me some more options from
>> >> the script (and that is build from the git tree):
>> >> 
>> >>         echo [build] Configuring Emacs
>> >>         $REPO_DIR/$BRANCH/configure \
>> >>             --without-dbus \
>> >>             --without-compress-install \
>> >>             --with-native-compilation \
>> >>             $CACHE \
>> >>             CFLAGS="$CFLAGS"
>> >> 
>> >> Could it be that these additional options are spoiling the build?
>> >> (CACHE=-C , I think.)
>> >
>> > I'd drop the CACHE part, so that the configure script starts from a
>> > clean state.
>> 
>> I wouldn't!
>> 
>> CACHE=-C is used only on a snapshot build. These were always built
>> incrementally from the previous version because I judged that the risk
>> of a broken build was small compared to the significant time and cost
>> saving that the incremental build provided.
>
> AFAIU, Dieter said he did more than one build in the same tree for
> several different configurations, so I suggested to eliminate the
> cache as a possible factor for the problems he saw in the second
> build.  Apologies if I misunderstood.


Oh, sure, that's fine. Just saying that the `CACHE=-C` is there for
mostly good reasons!

Phil