Re: Org-mode version 6.30trans (release_6.30d.5.gc125); make fails on org-ascii.el

From: Daniel Martins <danielemc@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
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	[thread overview]
Message-ID: <6ac505ad0909041954g25dce8eel73b793d38faa10b@mail.gmail.com> (raw)
In-Reply-To: <172E8752-1404-4B90-91ED-4B98A44A2914@gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 2827 bytes --]

>
> *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 <carsten.dominik@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:
>>>
>>>
>>>  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
>

[-- Attachment #1.2: Type: text/html, Size: 4638 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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