From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Martins Subject: Re: Org-mode version 6.30trans (release_6.30d.5.gc125); make fails on org-ascii.el Date: Fri, 4 Sep 2009 23:54:50 -0300 Message-ID: <6ac505ad0909041954g25dce8eel73b793d38faa10b@mail.gmail.com> References: <87k50fdk7d.fsf@gmx.de> <877hwfq6m8.fsf@gmx.de> <172E8752-1404-4B90-91ED-4B98A44A2914@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0211529179==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MjlQU-00074X-4D for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 22:54:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MjlQS-00074J-7t for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 22:54:53 -0400 Received: from [199.232.76.173] (port=45657 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MjlQS-00074G-3t for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 22:54:52 -0400 Received: from qw-out-1920.google.com ([74.125.92.145]:42551) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MjlQR-0005Dg-Jq for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 22:54:51 -0400 Received: by qw-out-1920.google.com with SMTP id 5so485371qwf.24 for ; Fri, 04 Sep 2009 19:54:50 -0700 (PDT) In-Reply-To: <172E8752-1404-4B90-91ED-4B98A44A2914@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org --===============0211529179== Content-Type: multipart/alternative; boundary=000feaf5b02980f3170472cbbd5c --000feaf5b02980f3170472cbbd5c Content-Type: text/plain; charset=ISO-8859-1 > > *On the other hand: Shouldn't a simple `make' do everything needed to > succeed?* > On "How do I keep current with Org mode development?" http://orgmode.org/worg/org-faq.php#keeping-current-with-Org-mode-development it is suggested the following commands git pull && make clean && make && make doc && make install I've put together with a command which updaes a bunch of svn repositories from my students. The problem is: make clean before make FORCES recompiling the same files again and not only the updated files! As org-mode is updated very often and the the compiling process is a bit slow and always annoying I decide to change the comand to git pull & && make && make install I dropped make doc because it seems that there is som problem with texinfo files of these new version. The problem of omitting make clean isthat: if a file disappears its compiled maybe will not disappear and cause problems. Therefore I repeat Sebastien request: *Shouldn't a simple `make' do everything needed to succeed?* Daniel 2009/9/4 Carsten Dominik > > On Sep 4, 2009, at 1:41 PM, Sebastian Rose wrote: > > Sebastian Rose writes: >> >>> Trying to `make' org-mode fails with the following error message: >>> >>> >>> In toplevel form: >>> lisp/org-ascii.el:29:1:Error: Symbol's function definition is void: >>> org-float-time >>> make: *** [lisp/org-ascii.elc] Fehler 1 >>> >>> >>> >>> >>> Opening the org-mode/lisp/ directory in dired and marking all *.el files >>> (`% m el$ RET) and byte-compiling them (`B') works for >>> org-ascii.el. >>> There it just failes for org-xoxo.el for the same reason. >>> >> >> >> sh$ make clean >> sh$ make >> >> does the trick... >> >> >> Or even (if not clean): >> >> sh$ make autoloads >> sh$ make >> >> >> I think we can live with it, as this is not unusual at all. >> >> On the other hand: Shouldn't a simple `make' do everything needed to >> succeed? >> > > In principle I would agree, and if you download a zip or tar distribution, > it works just like that. However, in the git distro, you do > create new files which stick around when you update. > > Of course we could add a "make clean" to the ALL target, but it seems to me > that this is different from other uses of make. Maybe the make update > should contain it? > > - Carsten > > > > >> >> >> Sebastian >> >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > --000feaf5b02980f3170472cbbd5c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On the other h= and: Shouldn't a simple `make' do everything needed to succeed?=


On "How do I keep current with Org mode development?"
=
http://orgmode.org/worg/org-faq.php#keeping-current-with= -Org-mode-development

it is suggested the following commands

gi=
t pull && make clean && make && make doc &&=
 make install

I've put together with a command which updae= s a bunch of svn repositories from my students.

The problem is: make clean before make FORCES recompiling the same file= s again and not only the updated files!

As org-mode is updated very = often and the the compiling process is a bit slow and always annoying
I decide to change the comand to 

git pull &a=
mp; && make  && make install
I dropped make doc because it seems that there is som problem with texinfo = files of these new version.



The problem of omitting make cle= an isthat: if a file disappears its compiled maybe will not disappear and c= ause problems.

Therefore I repeat Sebastien request:

Shouldn't a simple = `make' do everything needed to succeed?

Daniel

2009/9/4 Carsten Dominik <carsten.domin= ik@gmail.com>

On Sep 4, 2009, at 1:41 PM, Sebastian Rose wrote:

Sebastian Rose <sebastian_rose@gmx.de> writes:
Trying to `make' org-mode fails with the following error message:


=A0In toplevel form:
=A0lisp/org-ascii.el:29:1:Error: Symbol's function definition is void:<= br> =A0org-float-time
=A0make: *** [lisp/org-ascii.elc] Fehler 1




Opening the org-mode/lisp/ directory in dired and marking all *.el files (`% m el$ RET) and byte-compiling them (`B') works for
org-ascii.el.
There it just failes for org-xoxo.el for the same reason.


sh$ make clean
sh$ make

does the trick...


Or even (if not clean):

sh$ make autoloads
sh$ make


I think we can live with it, as this is not unusual at all.

On the other hand: Shouldn't a simple `make' do everything needed t= o succeed?

In principle I would agree, and if you download a zip or tar distribution,<= br> it works just like that. =A0However, in the git distro, you do
create new files which stick around when you update.

Of course we could add a "make clean" to the ALL target, but it s= eems to me
that this is different from other uses of make. =A0Maybe the make update sh= ould contain it?

- Carsten






=A0Sebastian


_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

--000feaf5b02980f3170472cbbd5c-- --===============0211529179== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============0211529179==--