From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: compilation issues of new export framework Date: Sat, 09 Feb 2013 18:50:39 +0100 Message-ID: <877gmhs7f4.fsf@gmail.com> References: <876229nrxf.fsf@gmail.com> <87a9rd3odf.fsf@Rainer.invalid> <87y5ex5rwa.fsf_-_@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52632) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4EZm-0007hN-LP for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 12:50:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4EZl-00010J-Fa for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 12:50:58 -0500 Received: from mail-wg0-f45.google.com ([74.125.82.45]:36436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4EZl-000101-9Z for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 12:50:57 -0500 Received: by mail-wg0-f45.google.com with SMTP id dq12so3786331wgb.12 for ; Sat, 09 Feb 2013 09:50:56 -0800 (PST) In-Reply-To: <87y5ex5rwa.fsf_-_@Rainer.invalid> (Achim Gratz's message of "Sat, 09 Feb 2013 18:16:53 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Hello, Achim Gratz writes: > an oddity occurs since the new exporter moved into core (I don't think I > had seen this before, so maybe you can relate to what is different now): > > Compiling /lisp/org-mode/lisp/org.el... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... > Loading org-element... Yes, I noticed this one too, but I don't know yet from where it could come from. > This only happens when using byte-recompile-directory, which means > org-element has already been loaded in that session and is present as a > byte-compiled file. I haven't yet found where in org.el these loads are > triggered, but it seems that this might be related to macro expansion. > In any case, the resulting org.elc file therefore depends on the > compilation method, which is highly undesirable. I haven't been able to > analyse this further. > > Another sticky point is your use of declare-function: some of these are > actually defsubst, not defun: > > org-element-{contents,nested-p,element-property,put-property} > > I don't think they will be inlined unless their definition has been > interned, declaration alone will not suffice. I don't know either how inline functions behave in this situation. > I don't see an easy way to factor out those parts from org-element > that are needed by org, but I suggest that we should find one. It is always possible to make them regular functions. Some profiling may be necessary, though. > There are more errors when doing a "make ORGCM=slint2 compile" in the > last pass. These files are probably all just missing an > > (eval-when-compile (require 'cl)) > > but I only checked ox-md. Indeed. Fixed. Thank you. Regards, -- Nicolas Goaziou