unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Charles A. Roelli" <charles@aurox.ch>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: Alan Third <alan@idiocy.org>,
	27736@debbugs.gnu.org,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#27736: OSX 10.6.8: Building from master branch fails.
Date: Sun, 5 Nov 2017 21:54:19 +0100	[thread overview]
Message-ID: <CD856D62-56A1-4AAD-A2CF-C08ACD61E022@aurox.ch> (raw)
In-Reply-To: <m2a800ve9b.wl%esq@lawlist.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Could you please show a backtrace as posted here:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27736#49


> On 5 Nov 2017, at 18:14, Keith David Bershatsky <esq@lawlist.com> wrote:
> 
> I realize that this bug was closed some time ago and I apologize for not speaking up sooner.  I am still unable to build current versions of Emacs 26 or the master branch on OSX 10.6.8 (server edition) absent using an earlier version of org-mode.
> 
> The same symptoms as described in the initial bug report still persist -- i.e., build freezes when byte-compiling org-timer.el:
> 
>  ELC      org/org-timer.elc
> 
> For those who have reported that the previous attempted fix was successful, perhaps there is a difference between retail OSX 10.6.8 and the server edition.  But, that's just a guess on my part.
> 
> Thanks,
> 
> Keith

[-- Attachment #2: Type: text/html, Size: 1371 bytes --]

       reply	other threads:[~2017-11-05 20:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2a800ve9b.wl%esq@lawlist.com>
2017-11-05 20:54 ` Charles A. Roelli [this message]
2017-07-17 15:18 bug#27736: OSX 10.6.8: Building from master branch fails Keith David Bershatsky
2017-07-17 15:29 ` Noam Postavsky
2017-07-17 16:10 ` Keith David Bershatsky
2017-07-17 16:38   ` Noam Postavsky
2017-07-17 18:05 ` Keith David Bershatsky
2017-07-17 18:48   ` Noam Postavsky
2017-07-17 19:43 ` Alan Third
2017-07-17 20:48   ` Charles A. Roelli
2017-07-17 21:37 ` Keith David Bershatsky
2017-07-18  5:08   ` Charles A. Roelli
2017-07-18  6:56 ` Keith David Bershatsky
2017-07-18 14:34   ` Eli Zaretskii
2017-07-18 16:07 ` Keith David Bershatsky
2017-07-18 18:42   ` Charles A. Roelli
2017-07-19 19:58     ` Charles A. Roelli
2017-07-19 22:48       ` Alan Third
2017-07-23  9:28         ` Charles A. Roelli
2017-07-24 15:50           ` Glenn Morris
2017-07-30 16:32             ` Charles A. Roelli
2017-11-05 18:03 ` Keith David Bershatsky
2017-11-05 18:15   ` Noam Postavsky
2017-11-05 20:01 ` Keith David Bershatsky
2017-11-06  2:20 ` Keith David Bershatsky
2017-11-06 19:41   ` Charles A. Roelli
2017-11-06 20:41     ` Charles A. Roelli
2017-11-07  2:13 ` Keith David Bershatsky
2017-11-07 20:20   ` Charles A. Roelli
2017-11-08  5:18 ` Keith David Bershatsky
2017-11-08 19:55   ` Charles A. Roelli
2018-03-27 21:19 ` Paul Eggert
2018-03-28 17:15   ` Glenn Morris
2018-03-28 19:02     ` Charles A. Roelli
2018-03-28 19:33     ` Paul Eggert
2018-03-28 22:08       ` Paul Eggert
2018-03-28 18:54   ` Charles A. Roelli
2018-03-28 21:29     ` Paul Eggert
     [not found]     ` <805d95e1-bfc0-bb40-ced7-c10bb5a7256e@cs.ucla.edu>
2018-03-31 15:02       ` Charles A. Roelli
     [not found]       ` <m21sg02sr4.fsf@aurox.ch>
2018-04-01 20:32         ` Paul Eggert

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=CD856D62-56A1-4AAD-A2CF-C08ACD61E022@aurox.ch \
    --to=charles@aurox.ch \
    --cc=27736@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=esq@lawlist.com \
    --cc=npostavs@users.sourceforge.net \
    /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).