From: Michael Albinus <michael.albinus@gmx.de>
To: Alan Third <alan@idiocy.org>
Cc: chad <yandros@gmail.com>, 62210@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#62210: Status uf NS port?
Date: Tue, 04 Apr 2023 13:05:18 +0200 [thread overview]
Message-ID: <87cz4jykk1.fsf__24303.4064582147$1680606388$gmane$org@gmx.de> (raw)
In-Reply-To: <ZCtCwYOSlcp3YMNX@idiocy.org> (Alan Third's message of "Mon, 3 Apr 2023 22:18:57 +0100")
Alan Third <alan@idiocy.org> writes:
Hi Alan,
> I never managed to work out how to build against gnustep with GCC.
> Clang worked absolutely fine.
>
> FWIW, gnustep != macOS. Gnustep has very few users, and in all the
> years the gnustep port of Emacs was entirely broken we didn't receive
> a single bug report about it. Except maybe from Martin, but he was
> only using it as a test bed.
Thanks for the feedback. I've commented out the GNUSTEP jobs on EMBA
(again), until somebody provides running build instructions.
Best regards, Michael.
next prev parent reply other threads:[~2023-04-04 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 17:42 Status uf NS port? Michael Albinus
[not found] ` <877cv4xtiv.fsf@yahoo.com>
2023-03-26 12:24 ` bug#62210: Job build-image-gnustep does not run anymore on EMBA Michael Albinus
2023-03-27 15:53 ` Michael Albinus
[not found] ` <87355pyc7y.fsf@yahoo.com>
2023-03-28 7:23 ` Michael Albinus
2023-03-28 16:55 ` Michael Albinus
2023-03-27 17:03 ` Status uf NS port? chad
2023-03-28 7:22 ` Michael Albinus
2023-04-03 21:18 ` Alan Third
2023-04-04 11:05 ` Michael Albinus [this message]
2023-04-04 11:05 ` Michael Albinus
2023-04-04 12:20 ` bug#62210: " Robert Pluim
2023-04-04 18:03 ` Michael Albinus
2023-04-05 7:18 ` Robert Pluim
2023-09-12 0:19 ` bug#62210: Job build-image-gnustep does not run anymore on EMBA Stefan Kangas
2023-09-12 17:38 ` Michael Albinus
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='87cz4jykk1.fsf__24303.4064582147$1680606388$gmane$org@gmx.de' \
--to=michael.albinus@gmx.de \
--cc=62210@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=yandros@gmail.com \
/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.