From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: compilation failure
Date: Wed, 30 Mar 2011 20:16:49 +0200 [thread overview]
Message-ID: <83pqp8qxri.fsf@gnu.org> (raw)
In-Reply-To: <87hbaku3n6.fsf@rho.meyering.net>
> From: Jim Meyering <jim@meyering.net>
> Cc: wl@gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Wed, 30 Mar 2011 15:41:33 +0200
>
> > Can you use bisect to find the guilty commit?
>
> Finding a commit for which a perturbed "make bootstrap" succeeds
> was a challenge.
Thanks for your efforts.
> With that, I finally found a successful build at this git commit:
>
> commit 84655cfe88efb24c256302d016cd037d22544cca
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri Nov 6 18:47:48 2009 +0000
>
> Let integers use up 2 tags to give them one extra bit and double their range.
> * lisp.h (USE_2_TAGS_FOR_INTS): New macro.
> (LISP_INT_TAG, case_Lisp_Int, LISP_STRING_TAG, LISP_INT_TAG_P): New macros.
> ...
>
> Maybe someone else will do the actual bisection:
>
> Bisecting: 4164 revisions left to test after this (roughly 12 steps)
>
> This is the command to run:
>
> env MALLOC_PERTURB_=44 MALLOC_CHECK_=3 make -j9 bootstrap
I hope someone else can reproduce the problem.
In any case, please report this to the bug tracker with all the
details, so it doesn't get forgotten.
next prev parent reply other threads:[~2011-03-30 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 6:13 compilation failure Werner LEMBERG
2011-03-30 6:31 ` Paul Eggert
2011-03-30 6:52 ` Werner LEMBERG
2011-03-30 7:42 ` Jim Meyering
2011-03-30 8:04 ` Werner LEMBERG
2011-03-30 11:37 ` Eli Zaretskii
2011-03-30 12:29 ` Werner LEMBERG
2011-03-30 11:35 ` Eli Zaretskii
2011-03-30 13:41 ` Jim Meyering
2011-03-30 18:16 ` Eli Zaretskii
2011-03-30 18:16 ` Eli Zaretskii [this message]
2011-03-30 11:25 ` Eli Zaretskii
2011-03-30 13:00 ` Werner LEMBERG
2011-03-30 18:17 ` Eli Zaretskii
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=83pqp8qxri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.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 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.