Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: More Build Problems
Date: 10 Feb 1998 09:17:52 -0500	[thread overview]
Message-ID: <76d8gvr1bj.fsf_-_@clay.principia.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 10 Feb 1998 11:15:29 +0100

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:


    LMI> You probably have to add the location of the Custom package to the
    LMI> load-path in dgnushack.el.

OK. I did that and now I get the following after I do a make:


rm -f *.elc ; emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile
`cl.el' was compiled for Emacs 19.29 or later
*** Error code 255
make: Fatal error: Command failed for target `all'
Current working directory /am/washington/home/colman/site-lisp/qgnus-0.23/lisp
*** Error code 1
make: Fatal error: Command failed for target `lick'


As an aside, why does custom need to be explicitly specified on the load-path?
Isn't it dumped with Emacs?

-- 
Jake Colman                     

Principia Partners LLC          |        Phone: (201) 946-0300
Harborside Financial Center     |          Fax: (201) 946-0320
902 Plaza II                    |       Beeper: (800) 505-2795
Jersey City, NJ 07311           |       E-mail: colman@ppllc.com
                                |          web: http://www.ppllc.com



  reply	other threads:[~1998-02-10 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-09 15:59 New Tester: make errors on custom Jake Colman
1998-02-10 10:15 ` Lars Magne Ingebrigtsen
1998-02-10 14:17   ` Jake Colman [this message]
1998-02-10 19:11     ` More Build Problems Lars Magne Ingebrigtsen
1998-02-10 19:58       ` Jake Colman
1998-02-10 20:55         ` Lars Magne Ingebrigtsen
1998-02-10 22:22           ` Jake Colman

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=76d8gvr1bj.fsf_-_@clay.principia.com \
    --to=colman@ppllc.com \
    --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).