Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Build 207 on xemacs21.5-linux - Build failed: failed compile on rev. 7eba7601cf458aa3e7bb0f49c57464dcee5958e4
Date: Thu, 30 Jun 2011 20:48:08 +0200	[thread overview]
Message-ID: <878vsjnok7.fsf@randomsample.de> (raw)
In-Reply-To: <m3liwjqhzp.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 30 Jun 2011 20:41:46 +0200")

Lars Magne Ingebrigtsen writes:
> David Engster <deng@randomsample.de> writes:
>
>> It does, but XEmacs is called with "-no-autoloads", that's why it cannot
>> find it. But Gnus ships with sha1.el... I'm don't really understand
>> it. If I remove the "-no-autoloads" from the Makefile, it compiles
>> auth-source.el just fine.
>
> Huh.  I wonder what the -no-autoloads thing is meant to achieve?

aclocal.m4 says:

dnl This will set the XEmacs command line options to be slightly different
dnl from the Emacs ones.  If building with XEmacs the options will be
dnl "-batch -no-autoloads..." to give a much cleaner build environment.

This just seems to be the XEmacs way of doing things:

(from: http://www.xemacs.org/Documentation/21.5/html/lispref_8.html)

"It is important to note that the XEmacs used to compile packages is the
bare minimum: it is called with the `-no-autoloads'. This means that
anything not dumped into XEmacs by default needs to be specified in the
`REQUIRES' variable (for packaged Lisp) or in some cases the `PRELOADS'
(autoloads used in libraries mentioned in `PRELOADS')."

-David



  reply	other threads:[~2011-06-30 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QcKpv-0003CU-2d@v3-1008.vxen.de>
2011-06-30 18:10 ` Lars Magne Ingebrigtsen
2011-06-30 18:37   ` David Engster
2011-06-30 18:41     ` Lars Magne Ingebrigtsen
2011-06-30 18:48       ` David Engster [this message]
2011-06-30 20:15         ` Lars Magne Ingebrigtsen

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=878vsjnok7.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    /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.
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 NNTP newsgroup(s).