unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: compilation failure
Date: Wed, 30 Mar 2011 15:41:33 +0200	[thread overview]
Message-ID: <87hbaku3n6.fsf@rho.meyering.net> (raw)
In-Reply-To: <E1Q4tgp-0007cI-Ff@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 30 Mar 2011 07:35:55 -0400")

Eli Zaretskii wrote:
>> From: Jim Meyering <jim@meyering.net>
>> Date: Wed, 30 Mar 2011 09:42:42 +0200
>> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
>>
>> This command,
>>   env MALLOC_PERTURB_=0 MALLOC_CHECK_=0 make -j9 bootstrap
>> has succeeded for me on each of the last three mornings (Mar 28-30).
>>
>> I manually set those two MALLOC_*_ variables to 0 because
>> when I don't, emacs fails to bootstrap.
>
> It's a pity this problem was not reported to the bug tracker.  (At
> least I couldn't find it; apologies if I missed it.)

I thought I reported it to some emacs development list months ago,
but a quick search didn't find it.

>> I suspect that emacs is using free'd memory containing
>> values that would normally be unoffensive, but when you set
>> those envvars (esp MALLOC_PERTURB_) to nonzero, it makes
>> glibc scribble on free'd buffers, and that makes emacs
>> exhibit an actual failure.
>
> Can you use bisect to find the guilty commit?

Finding a commit for which a perturbed "make bootstrap" succeeds
was a challenge.

I bootstrapped 8 or 10 times, going back to 2009
in steps of 500, then 1500 commits.  Same failure
each time, until I started getting link errors:

  /usr/bin/ld: xftfont.o: undefined reference to symbol 'XRenderQueryExtension'
  /usr/bin/ld: note: 'XRenderQueryExtension' is defined in DSO /usr/lib64/libXrender.so.1 so try adding it to the linker command line
  /usr/lib64/libXrender.so.1: could not read symbols: Invalid operation

I worked around that by inserting -lXrender into the generated Makefile:

    perl -pi -e 's/(-lfreetype )/$1-lXrender /' src/Makefile

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

If not, I'll get to it, eventually.



  reply	other threads:[~2011-03-30 13:41 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 [this message]
2011-03-30 18:16           ` Eli Zaretskii
2011-03-30 18:16           ` Eli Zaretskii
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

  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=87hbaku3n6.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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 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).