all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: emacs-devel@gnu.org
Subject: Re: trunk not building on OSX
Date: Wed, 16 May 2012 11:33:29 -0700	[thread overview]
Message-ID: <86likskmbq.fsf@red.stonehenge.com> (raw)
In-Reply-To: 0D7BCAD4-304D-403D-88A5-85E079259720@swipnet.se

>>>>> "Jan" == Jan Djärv <jan.h.d@swipnet.se> writes:

Jan> Hello.
Jan> I do not have this problem. How do you configure Emacs?

This was a weird problem, and I think there's still a problem somehow.

I did a git bisect between the version the day before, and the broken
version.  Each time, I did a "git clean -f -x" which wipes everything
but the commit, and:

  ./autogen.sh
  ./configure --with-ns --without-x --without-dbus \
  --with-jpeg=no --with-gif=no --with-tiff=no --prefix=/tmp/emacs

to configure, followed by "make clean bootstrap install" to build.

Now the weird part.  Every single one I did, worked just fine.
So the bisect told me the "last good commit" was in fact the one before
the origin/master.

On a whim, I built origin/master again... and this time it worked.

It should not have.  I was unable to get it to *fail* as it had earlier,
even though I was building exactly the same way.

Is there some part of the build running in parallel, and I was running
into timing issues?  I've actually seen this error before, but only
sporadically.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion




  reply	other threads:[~2012-05-16 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:10 trunk not building on OSX Randal L. Schwartz
2012-05-16 10:24 ` Jan Djärv
2012-05-16 18:33   ` Randal L. Schwartz [this message]
2012-05-17  8:11     ` Jan Djärv
2012-05-17 13:08       ` Randal L. Schwartz

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=86likskmbq.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=emacs-devel@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.