all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Issue building on MSWindows + msys
Date: Wed, 15 Nov 2023 12:18:05 -0600	[thread overview]
Message-ID: <CAJf-WoQFSxPbwPN4JOkCpkBSiwwU55xzP9Guc6Ds9zVOR_bMLg@mail.gmail.com> (raw)
In-Reply-To: <83il63q82s.fsf@gnu.org>

On Wed, Nov 15, 2023 at 10:45 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Wed, 15 Nov 2023 15:57:17 +0100
> > From: Ergus <spacibba@aol.com>
> >
> > make[2]: *** [Makefile:330: erc/erc-goodies.elc] Error 3
> >
> > -------------------------
> >
> > And a similar message (including backtrace) a bit latter:
> >
> > make[2]: *** [Makefile:330: org/ob-eshell.elc] Error 3
> >
> > -------------------------
> >
> > I made a clean build, make boostrap, git clean, rebuild from scratch etc
> > etc... and everytime I get the same error.
> >
> > Anybody knows what's going on?? Did I something wrong or is there some
> > known issue related with this??
>

I'm not able to reproduce this.   One thing I do between builds that
you don't mention is:
  git clean -xfd

I'm not sure why that should be needed, but it replaces having to run
clean (or a variant), at the cost of having to run autogen.sh each
time.

In any case, grepping a log of my successful build, just now, for
error or warning messages I see only:

w32heap.c:853:14: warning: 'm' may be used uninitialized [-Wmaybe-uninitialized]

Which is expected on Windows.

> Did you update any of your system utilities (like Grep) or libraries
> lately?
>

I didn't, FTR.



  reply	other threads:[~2023-11-15 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pq5oqtzlurtwkspcesdvk7rtrtdu6ye6t6wnioto6wzx257vsm.ref@jdinp4e6ahna>
2023-11-15 14:57 ` Issue building on MSWindows + msys Ergus
2023-11-15 16:45   ` Eli Zaretskii
2023-11-15 18:18     ` Corwin Brust [this message]
2023-11-15 22:00     ` Ergus
2023-11-16  5:45       ` 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

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

  git send-email \
    --in-reply-to=CAJf-WoQFSxPbwPN4JOkCpkBSiwwU55xzP9Guc6Ds9zVOR_bMLg@mail.gmail.com \
    --to=corwin@bru.st \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.