unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Re: emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
       [not found] ` <20230624072332.D0760C11CE0@vcs2.savannah.gnu.org>
@ 2023-06-24 17:02   ` Arash Esbati
  2023-06-24 17:17     ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Arash Esbati @ 2023-06-24 17:02 UTC (permalink / raw)
  To: emacs-devel; +Cc: Eli Zaretskii

Eli Zaretskii <eliz@gnu.org> writes:

> branch: emacs-29
> commit 679e9d7c56e2296e3a218290d941e28002bf7722
> Author: Eli Zaretskii <eliz@gnu.org>
> Commit: Eli Zaretskii <eliz@gnu.org>
>
>     ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
>     
>     * etc/PROBLEMS: Mention the problems building with MinGW64 GCC
>     13.1.  (Bug#63365)
> ---
> [...]
> +  . Use non-default optimization flags.  For example, configuring the
> +    build like this will avoid the problem:
> +
> +     CFLAGS='-O1 -gdwarf-4 -g3' ./configure ...

Thanks for adding this entry.  This is probably a nit, but Emacs default
is '-gdwarf-2'.  Maybe the entry should stick to that and shouldn't open
up a new possible source of confusion?

Best, Arash



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
  2023-06-24 17:02   ` emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS Arash Esbati
@ 2023-06-24 17:17     ` Eli Zaretskii
  2023-06-24 17:30       ` Arash Esbati
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2023-06-24 17:17 UTC (permalink / raw)
  To: Arash Esbati; +Cc: emacs-devel

> From: Arash Esbati <arash@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Sat, 24 Jun 2023 19:02:13 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > branch: emacs-29
> > commit 679e9d7c56e2296e3a218290d941e28002bf7722
> > Author: Eli Zaretskii <eliz@gnu.org>
> > Commit: Eli Zaretskii <eliz@gnu.org>
> >
> >     ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
> >     
> >     * etc/PROBLEMS: Mention the problems building with MinGW64 GCC
> >     13.1.  (Bug#63365)
> > ---
> > [...]
> > +  . Use non-default optimization flags.  For example, configuring the
> > +    build like this will avoid the problem:
> > +
> > +     CFLAGS='-O1 -gdwarf-4 -g3' ./configure ...
> 
> Thanks for adding this entry.  This is probably a nit, but Emacs default
> is '-gdwarf-2'.

I know.

> Maybe the entry should stick to that and shouldn't open up a new
> possible source of confusion?

If you think this could cause confusion.  I thought it won't, and
"-gdwarf-4" gives you a better debug info.  (We don't use that by
default because I don't know which version of MinGW GCC started
supporting it.)



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
  2023-06-24 17:17     ` Eli Zaretskii
@ 2023-06-24 17:30       ` Arash Esbati
  0 siblings, 0 replies; 3+ messages in thread
From: Arash Esbati @ 2023-06-24 17:30 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

Eli Zaretskii <eliz@gnu.org> writes:

> I thought it won't, and "-gdwarf-4" gives you a better debug info.
> (We don't use that by default because I don't know which version of
> MinGW GCC started supporting it.)

Ah, that was intentional, so let's keep it that way.

Best, Arash



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-06-24 17:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <168759141254.12117.13820565670920393730@vcs2.savannah.gnu.org>
     [not found] ` <20230624072332.D0760C11CE0@vcs2.savannah.gnu.org>
2023-06-24 17:02   ` emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS Arash Esbati
2023-06-24 17:17     ` Eli Zaretskii
2023-06-24 17:30       ` Arash Esbati

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).