unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Antczak <marcin.antczak@gmail.com>
Subject: [PATCH] my first patch for emacs
Date: Wed, 14 Sep 2005 16:53:05 +0200	[thread overview]
Message-ID: <1126709585.12119.10.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 205 bytes --]

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.

I hope you will like it.


Regards,
Marcin



[-- Attachment #2: makefile.elc.test.diff --]
[-- Type: text/x-patch, Size: 1751 bytes --]

? makefile.elc.test.diff
Index: Makefile.in
===================================================================
RCS file: /cvsroot/emacs/emacs/Makefile.in,v
retrieving revision 1.304
diff -c -r1.304 Makefile.in
*** Makefile.in	26 Jul 2005 21:43:11 -0000	1.304
--- Makefile.in	14 Sep 2005 14:30:31 -0000
***************
*** 742,754 ****
  .PHONY: maybe_bootstrap
  
  maybe_bootstrap:
! 	@bar="`echo $(srcdir)/lisp/*.elc`"; \
! 	if [ \( "$$bar" = '$(srcdir)/lisp/*.elc' \) -o \( "$$bar" = '' \) ]; then \
! 	  echo "Your tree does not include the compiled Lisp files."; \
! 	  echo "You need to do \`make bootstrap' to build Emacs."; \
! 	  echo "Emacs now requires Texinfo version 4.2."; \
! 	  exit 1;\
! 	fi
  
  bootstrap: bootstrap-clean-before info bootstrap-build FRC
  
--- 742,748 ----
  .PHONY: maybe_bootstrap
  
  maybe_bootstrap:
! 	(cd src; $(MAKE) $(MFLAGS) bootstrap-maybe)
  
  bootstrap: bootstrap-clean-before info bootstrap-build FRC
  
Index: src/Makefile.in
===================================================================
RCS file: /cvsroot/emacs/emacs/src/Makefile.in,v
retrieving revision 1.313
diff -c -r1.313 Makefile.in
*** src/Makefile.in	7 Aug 2005 12:33:16 -0000	1.313
--- src/Makefile.in	14 Sep 2005 14:30:37 -0000
***************
*** 1340,1345 ****
--- 1340,1355 ----
  
  /* Bootstrapping.  */
  
+ bootstrap-maybe:
+ 	@for file in ${lisp}; do \
+ 	    if [ ! -f $$file ]; then \
+ 		echo "Your tree does not include the compiled Lisp file: $$file"; \
+ 		echo "You need to do \'make bootstrap' to build Emacs."; \
+ 		echo "Emacs now requires Texinfo version 4.2."; \
+ 		exit 1; \
+ 	    fi; \
+ 	done
+ 
  bootstrap: bootstrap-emacs${EXEEXT}
  
  /* Dump an Emacs executable named bootstrap-emacs containing the

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

             reply	other threads:[~2005-09-14 14:53 UTC|newest]

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

  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=1126709585.12119.10.camel@localhost.localdomain \
    --to=marcin.antczak@gmail.com \
    /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).