unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: emacs-devel@gnu.org
Subject: Re: build failures in mingw64
Date: Sun, 09 Jul 2023 11:51:29 +0300	[thread overview]
Message-ID: <83351xbh7y.fsf@gnu.org> (raw)
In-Reply-To: <1089214782.2847848.1688889913507@mail1.libero.it> (message from Angelo Graziosi on Sun, 9 Jul 2023 10:05:13 +0200 (CEST))

> Date: Sun, 9 Jul 2023 10:05:13 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> 
> I just noticed this in configure:
> 
>    checking whether MB_CUR_MAX is correct... ./configure: line 33322: test: !=: unary operator expected

Please show the relevant part of the configure script.  Since the
configure is generated on each user's system as part of the build, it
is hard to guess what you have there without seeing the actual code
you get.  For example, on my system, line 33322 of the configure
script is an empty line, and I see no "!=" anywhere around that.

So more data is needed to investigate this.

Thanks.



  reply	other threads:[~2023-07-09  8:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09  8:05 build failures in mingw64 Angelo Graziosi
2023-07-09  8:51 ` Eli Zaretskii [this message]
2023-07-09  9:33   ` Angelo Graziosi
2023-07-09 10:01     ` Angelo Graziosi
2023-07-09 11:22       ` Eli Zaretskii
2023-07-09 11:19     ` Eli Zaretskii
2023-07-09 20:57       ` Paul Eggert
2023-07-09 22:48         ` Angelo Graziosi
2023-07-10 12:28         ` Eli Zaretskii
2023-07-10 17:00           ` Paul Eggert
2023-07-10 23:40             ` Angelo Graziosi
2023-07-09 16:17 ` Stephen Leake
  -- strict thread matches above, loose matches on Subject: below --
2023-07-08 21:50 Stephen Leake
2023-07-09  5:58 ` Eli Zaretskii

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=83351xbh7y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.g0@libero.it \
    --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).