all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Build failure in nsterm.m
Date: Wed, 30 Jun 2021 19:41:27 +0100	[thread overview]
Message-ID: <YNy614qQ6f5SGmRH@breton.holly.idiocy.org> (raw)
In-Reply-To: <0f96081c-5bd4-7076-2f83-decb2bcbb785@gmx.at>

On Wed, Jun 30, 2021 at 09:38:16AM +0200, martin rudalics wrote:
> > I've pushed a fix. I think this is a shorthand way of writing an ObjC
> > array that GCC doesn't understand.
> 
> It's fixed now.

Thanks!

> > I'm using a version of GNUstep built from git and I can no longer
> > build Emacs with GCC at all,
> 
> In which sense does it fail?

configure fails to find GNUstep requirements. There's a script to
source which sets up the environment for GNUstep builds, but it makes
no difference. The only thing that allows it to continue is to use
"CC=clang".

I imagine it's my build environment, but I followed the GNUstep
instructions from their wiki and I can't work out how to get it to
work.

I should probably ask them.

> > only clang, so these sorts of things slip
> > through quite easily.
> >
> > I'm not sure why GCC doesn't work, I'm sure it's not the Emacs code
> > that's at fault, so I have to assume that the GNUstep devs have given
> > up waiting for GCC to catch up.
> 
> Maybe we should drop a note about this somewhere.

I'd rather be sure it's not just me being useless before making any
official notice.
-- 
Alan Third



      reply	other threads:[~2021-06-30 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  8:28 Build failure in nsterm.m martin rudalics
2021-06-29 21:23 ` Alan Third
2021-06-30  7:38   ` martin rudalics
2021-06-30 18:41     ` Alan Third [this message]

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=YNy614qQ6f5SGmRH@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.