unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: idlwave won't byte compile
Date: Fri, 03 Sep 2004 11:41:23 -0600	[thread overview]
Message-ID: <4138ACC3.7020000@yahoo.com> (raw)
In-Reply-To: ch9t1v$phm$1@panix5.panix.com

Jeff Berry wrote:
 > I'm trying to install idlwave-5.3 for a user at my site, and it
 > won't byte compile.  I'm running AIX4.3 and emacs-21.3, and when
 > I try to make idlwave, I get this:
 > ===================
 > emacs-21.3 -batch -no-init-file -l lpath.el -f batch-byte-compile idlwave.el idlw-help.el idlw-shell.el idlw-rinfo.el idlw-toolbar.el idlw-complete-structtag.el idlw-roprompt.el
 > While compiling toplevel forms in file /mnt/src/idlwave-5.3/idlwave.el:
 >   !! error (("Required feature idlw-help was not provided"))
 > Wrote /mnt/src/idlwave-5.3/idlw-help.elc
 > While compiling toplevel forms in file /mnt/src/idlwave-5.3/idlw-shell.el:
 >   !! error (("Required feature idlw-help was not provided"))
 > Wrote /mnt/src/idlwave-5.3/idlw-rinfo.elc
 > Wrote /mnt/src/idlwave-5.3/idlw-toolbar.elc
 > Wrote /mnt/src/idlwave-5.3/idlw-complete-structtag.elc
 > Wrote /mnt/src/idlwave-5.3/idlw-roprompt.elc
 > Done
 > gmake: *** [lisp] Error 1
 > ===================
 >
 > The file idlw-help.el is in the local directory and the file lpath.el
 > looks like this:
 > =============
 > ;; IDLWAVE helper file for batch compiles -- Make sure we get the right files.
 > (setq load-path (cons "." load-path)
 >       byte-compile-warnings nil)
 > ===============
 >
 > Am I, not being a lisp programmer or much of emacs user, missing something
 > obvious here?

No, idlwave's author did: idlwave.el and idlw-shell.el must have
(require 'idlw-help), but idlw-help.el does not have (provide 'idlw-help);
so add it at the end of the file.

-- 
Kevin Rodgers

  reply	other threads:[~2004-09-03 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 13:54 idlwave won't byte compile Jeff Berry
2004-09-03 17:41 ` Kevin Rodgers [this message]
2004-09-07 12:08   ` Jeff Berry

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=4138ACC3.7020000@yahoo.com \
    --to=ihs_4664@yahoo.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.
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).