all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Antczak <marcin.antczak@orange.pl>
Subject: Re: [PATCH] my first patch for emacs
Date: Sun, 25 Sep 2005 22:49:54 +0200	[thread overview]
Message-ID: <1127681394.12649.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1126709585.12119.10.camel@localhost.localdomain>

Dnia 14-09-2005, śro o godzinie 16:54 +0200, Marcin Antczak napisał(a):
> Hi!
> 
> This is my first patch I created for emacs - so, be gentle...
> 
> This provides better test procedure when trying to build emacs from cvs
> without bootstrap.

RMS sent me mail with question about what my patch does better.
So, sorry for delay and here is my explanation.

With current code you can have _any single_ *.elc file in lisp directory
and make will think that everything is ok and you don't need to run make
bootstrap.

So, then emacs will not build because errors will show a while later.

With my code - Makefile will try to test if there is a minimal set
of .elc files available to build minimal emacs-bootstrap binary.

Of course after a little while I think that I should also add more files
to this list, because with files defined in ${lisp} variable you
propably will be able to build emacs-bootstrap but still face problems
when trying to build binaries from ./lib-src...

Anyway now you know what was my idea, and if I find a while to think
about again I'll try to prepare something better.


Marcin

  parent reply	other threads:[~2005-09-25 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 14:53 [PATCH] my first patch for emacs Marcin Antczak
2005-09-16 12:59 ` Richard M. Stallman
2005-09-25 20:49 ` Marcin Antczak [this message]
2005-09-26  4:49   ` Richard M. Stallman

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=1127681394.12649.18.camel@localhost.localdomain \
    --to=marcin.antczak@orange.pl \
    /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.