all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Caldwell <david@porkrind.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 11548@debbugs.gnu.org
Subject: bug#11548: Mac Intel/PowerPC doesn't build due to recent commit
Date: Wed, 23 May 2012 17:53:20 -0700	[thread overview]
Message-ID: <4FBD8680.9000507@porkrind.org> (raw)
In-Reply-To: <e9sjeq1lac.fsf@fencepost.gnu.org>

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

On 5/23/12 5:21 PM, Glenn Morris wrote:
> David Caldwell wrote:
> 
>> I'm not sure what the solution is, I'm just reporting that I can't build
>> on the Mac (PPC or Intel) any more.
> 
> Does it work if you start from a clean state? Eg
> 
> make maintainer-clean
> configure
> make

I am doing a clean checkout from bzr, which should be very clean:

bzr checkout --lightweight --hardlink emacs-bzr/trunk emacs-bzr/xxx-test
cd emacs-bzr/xxx-test
./autogen/copy_autogen
./configure --with-ns
make

Interestingly, I tried this locally on my laptop and could not duplicate
the problem. My laptop is running Mac OS X 10.7.4 and Xcode 4.3.2.

However, my Emacs build machine is consistently failing (the one that
builds Emacs for http://emacsformacosx.com). That machine is running
10.6.8 and Xcode 3.2.6 (the last version that worked on that OS, I
think). It needs to run on an older OS because that is the last OS that
supported building Emacs for PowerPC.

-David


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4446 bytes --]

  reply	other threads:[~2012-05-24  0:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 23:34 bug#11548: Mac Intel/PowerPC doesn't build due to recent commit David Caldwell
2012-05-24  0:21 ` Glenn Morris
2012-05-24  0:53   ` David Caldwell [this message]
2012-05-24  1:03     ` Glenn Morris
2012-05-24  1:58       ` David Caldwell
2012-05-24  2:06         ` Glenn Morris
2012-05-24  2:25           ` David Caldwell

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=4FBD8680.9000507@porkrind.org \
    --to=david@porkrind.org \
    --cc=11548@debbugs.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 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.