From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Drop OS X 10.4
Date: Tue, 14 Oct 2014 07:08:41 +0200 [thread overview]
Message-ID: <8BBA848D-F715-4284-AC3B-DFC96B103D57@swipnet.se> (raw)
In-Reply-To: <n97g03vrtg.fsf@fencepost.gnu.org>
Hello.
13 okt 2014 kl. 18:48 skrev Glenn Morris <rgm@gnu.org>:
> Jan Djärv wrote:
>
>> I don't think so. After all, if you are building for X or no toolkit,
>> it is basically just UNIX with an unexec that works on Intel. I don't
>> think that we should prevent configurations that we in principle
>> support (X, no-X, unexmacosx.c). A check for PowerPC might be in order
>> though as we don't support that.
>>
>> I could add that, but I don't have any PowerPC to test it on.
>
> Oh, but all the other points still apply:
>
> OS X 10.4 itself is unsupported for 5+ years.
> No Emacs developer has it to test on.
> All the bug reports about it come from one person (who seems to be doing
> an "explore the compilation parameter space" thing rather than actually
> wanting to use it).
> All the bug reports are about PPC;
> http://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3A10.4;package=emacs
> (whether this means it is working fine on non-ppc, I have no data for! :) )
>
> So personally I see no value to pretending it is still supported, and
> think it might as well be explicitly dropped.
>
I have to do some other test, because the test relies on Cocoa dev environment being present.
Stand by.
>> A check for PowerPC might be in order though as we don't support that.
>
> Should be easy?
>
> *** configure.ac 2014-10-12 22:56:45 +0000
> --- configure.ac 2014-10-13 16:47:29 +0000
> ***************
> *** 557,563 ****
> *-apple-darwin* )
> case "${canonical}" in
> i[3456]86-* ) ;;
> ! powerpc-* ) ;;
> x86_64-* ) ;;
> * ) unported=yes ;;
> esac
> --- 557,563 ----
> *-apple-darwin* )
> case "${canonical}" in
> i[3456]86-* ) ;;
> ! powerpc-* ) unported=yes ;;
> x86_64-* ) ;;
> * ) unported=yes ;;
> esac
Thanks, I checked that in.
Jan D.
next prev parent reply other threads:[~2014-10-14 5:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 15:59 Drop OS X 10.4 Glenn Morris
2014-10-10 16:18 ` Paul Eggert
2014-10-10 16:21 ` Glenn Morris
2014-10-10 16:31 ` Paul Eggert
2014-10-10 17:13 ` Jan Djärv
2014-10-10 17:57 ` Harald Hanche-Olsen
2014-10-11 7:24 ` Jan Djärv
2014-10-11 9:20 ` Bozhidar Batsov
2014-10-11 12:59 ` Juergen Fenn
2014-10-11 17:30 ` Bozhidar Batsov
2014-10-11 18:25 ` Glenn Morris
2014-10-12 8:37 ` Jan Djärv
2014-10-12 15:02 ` Paul Eggert
2014-10-12 16:06 ` Jan Djärv
2014-10-12 18:27 ` Glenn Morris
2014-10-12 23:10 ` Glenn Morris
2014-10-13 5:01 ` Jan Djärv
2014-10-13 5:04 ` Jan Djärv
2014-10-13 16:48 ` Glenn Morris
2014-10-14 5:08 ` Jan Djärv [this message]
2014-10-14 17:11 ` Jan Djärv
2014-10-14 17:26 ` Glenn Morris
2014-10-15 17:42 ` Jan Djärv
2014-10-10 16:28 ` Jan Djärv
2014-10-19 9:04 ` Ivan Kanis
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=8BBA848D-F715-4284-AC3B-DFC96B103D57@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).