emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#46495: closed (28.0.50; [native-comp] Build fails for 32bit --with-w


From: GNU bug Tracking System
Subject: bug#46495: closed (28.0.50; [native-comp] Build fails for 32bit --with-wide-int)
Date: Sat, 10 Apr 2021 17:40:01 +0000

Your message dated Sat, 10 Apr 2021 20:38:39 +0300
with message-id <837dla59b4.fsf@gnu.org>
and subject line Re: bug#46495: 28.0.50; [native-comp] Build fails for 32bit 
--with-wide-int
has caused the debbugs.gnu.org bug report #46495,
regarding 28.0.50; [native-comp] Build fails for 32bit --with-wide-int
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
46495: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46495
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int Date: Sat, 13 Feb 2021 17:57:09 +0000 User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
On Windows with the mingw64 32bit toolchain, the native branch build
fails when configured with "--with-nativecomp --with-wide-int".

Emacs crashes during .eln compilation. Attaching gdb to the crashing
emacs process does not produce a backtrace.

I suspect that this problem may not be Windows-specific, and should be reproducable on Linux, but I have not tried that.

    AndyM



--- End Message ---
--- Begin Message --- Subject: Re: bug#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int Date: Sat, 10 Apr 2021 20:38:39 +0300
> From: Andrea Corallo <akrl@sdf.org>
> Cc: andrewjmoreton@gmail.com, 46495@debbugs.gnu.org
> Date: Sat, 10 Apr 2021 16:49:15 +0000
> 
> > Okay dc393517ca adds the warning emittion.  I've also added a customize
> > `comp-warning-on-missing-source' to silence that in case.
> >
> >   Andrea
> 
> Not an expert of the bug tracker here but I think this is still open.
> In case should we close it?

Right, closing.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]