unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS
Date: Sat, 24 Jun 2023 19:02:13 +0200	[thread overview]
Message-ID: <864jmwvlnu.fsf@gnu.org> (raw)
In-Reply-To: <20230624072332.D0760C11CE0@vcs2.savannah.gnu.org> (Eli Zaretskii's message of "Sat, 24 Jun 2023 03:23:32 -0400 (EDT)")

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



       reply	other threads:[~2023-06-24 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168759141254.12117.13820565670920393730@vcs2.savannah.gnu.org>
     [not found] ` <20230624072332.D0760C11CE0@vcs2.savannah.gnu.org>
2023-06-24 17:02   ` Arash Esbati [this message]
2023-06-24 17:17     ` emacs-29 679e9d7c56e: ; Mention MinGW64 GCC 13.1 problems in PROBLEMS Eli Zaretskii
2023-06-24 17:30       ` Arash Esbati

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864jmwvlnu.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).