From: Ivan Shmakov <ivan@siamics.net>
To: 20141@debbugs.gnu.org
Subject: bug#20141: 24.4.91; Helm is broken after last changes in eieio
Date: Thu, 19 Mar 2015 07:20:20 +0000 [thread overview]
Message-ID: <87zj79wj0r.fsf@violet.siamics.net> (raw)
In-Reply-To: <87d245plc1.fsf@gmail.com> (Thierry Volpiatto's message of "Thu, 19 Mar 2015 07:12:14 +0100")
>>>>> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>> Frankly, I wasn’t even able to build Emacs as of 8dfff871bdf0
>> (2015-03-18 14:49:55Z), although the error for me is different
>> (MIMEd. Please note that I do not bootstrap – I /always/ build in a
>> freshly created build directory; lndir-ed.) Going two commits back
>> (to fd93edbb1cab) resolved the issue.
> Building fine for me
As of 8dfff871bdf0 or (the more recent) 50c117fe86d9?
> even without bootstrapping.
That’s the point: the build procedure I follow effectively does
‘bootstrap’ for each and every build; that is: no .elc of one
build is available for use to another. Think of, say:
$ git clone emacs emacs-build \
&& cd emacs-build \
&& autoreconf -v -i -I m4 \
&& ./configure --prefix="$HOME" --disable-silent-rules … \
&& LC_ALL=C nice -n+19 ionice -c 3 nohup /usr/bin/time \
make -j 2 -- lib lib-src src lisp &
--
FSF associate member #7257 np. One Leaf — Elk … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-03-19 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 5:17 bug#20141: 24.4.91; Helm is broken after last changes in eieio Thierry Volpiatto
2015-03-19 6:05 ` Ivan Shmakov
2015-03-19 6:12 ` Thierry Volpiatto
2015-03-19 7:20 ` Ivan Shmakov [this message]
2015-03-19 6:11 ` Thierry Volpiatto
2015-03-19 6:53 ` Tassilo Horn
2015-03-19 7:19 ` Michael Heerdegen
2015-03-19 8:10 ` Michael Heerdegen
2015-03-19 14:20 ` Stefan Monnier
2015-03-19 15:46 ` Tassilo Horn
2015-03-19 19:22 ` Stefan Monnier
2015-03-19 18:37 ` Thierry Volpiatto
2015-03-19 20:00 ` Stefan Monnier
2015-03-19 6:55 ` Tassilo Horn
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=87zj79wj0r.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=20141@debbugs.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.