* New Tester: make errors on custom
@ 1998-02-09 15:59 Jake Colman
1998-02-10 10:15 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 7+ messages in thread
From: Jake Colman @ 1998-02-09 15:59 UTC (permalink / raw)
Trying to build qgnus-0.23, I get a build failure on lpath.el because of
custom. Below is the make output:
cd lisp; gmake EMACS=emacs all
gmake[1]: Entering directory `/am/washington/home/colman/site-lisp/qgnus-0.23/lisp'
rm -f *.elc ; emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile
Loading ./lpath.el...
Cannot open load file: custom
gmake[1]: *** [all] Error 255
gmake[1]: Leaving directory `/am/washington/home/colman/site-lisp/qgnus-0.23/lisp'
gmake: *** [lick] Error 2
I am running the following version of Emacs:
GNU Emacs 20.2.1 (sparc-sun-solaris2.4, X toolkit)
of Mon Dec 1 1997 on clay.principia.com
I know that custom is installed properly on my system because it is used
throughout Emacs 20.2 and it works fine. What, presumably obvious, thing am I
missing?
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: New Tester: make errors on custom
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 ` More Build Problems Jake Colman
0 siblings, 1 reply; 7+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-02-10 10:15 UTC (permalink / raw)
Jake Colman <colman@ppllc.com> writes:
> Trying to build qgnus-0.23, I get a build failure on lpath.el because of
> custom. Below is the make output:
[...]
> Cannot open load file: custom
You probably have to add the location of the Custom package to the
load-path in dgnushack.el.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 7+ messages in thread
* More Build Problems
1998-02-10 10:15 ` Lars Magne Ingebrigtsen
@ 1998-02-10 14:17 ` Jake Colman
1998-02-10 19:11 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 7+ messages in thread
From: Jake Colman @ 1998-02-10 14:17 UTC (permalink / raw)
Cc: ding
>>>>> "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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: More Build Problems
1998-02-10 14:17 ` More Build Problems Jake Colman
@ 1998-02-10 19:11 ` Lars Magne Ingebrigtsen
1998-02-10 19:58 ` Jake Colman
0 siblings, 1 reply; 7+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-02-10 19:11 UTC (permalink / raw)
Jake Colman <colman@ppllc.com> writes:
> 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
This means that your cl.el was compiled for Emacs 19.29 or later. So
you should use Emacs 19.29 or later when compiling.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: More Build Problems
1998-02-10 19:11 ` Lars Magne Ingebrigtsen
@ 1998-02-10 19:58 ` Jake Colman
1998-02-10 20:55 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 7+ messages in thread
From: Jake Colman @ 1998-02-10 19:58 UTC (permalink / raw)
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Jake Colman <colman@ppllc.com> writes:
>> 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
LMI> This means that your cl.el was compiled for Emacs 19.29 or later. So
LMI> you should use Emacs 19.29 or later when compiling.
Look at my email header: X-Mailer: Gnus v5.5/Emacs 20.2
My initial posting including the output of (emacs-version):
GNU Emacs 20.2.1 (sparc-sun-solaris2.4, X toolkit)
of Mon Dec 1 1997 on clay.principia.com
Am I missing something obvious? 'cause I'm starting to feel really dumb!
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: More Build Problems
1998-02-10 19:58 ` Jake Colman
@ 1998-02-10 20:55 ` Lars Magne Ingebrigtsen
1998-02-10 22:22 ` Jake Colman
0 siblings, 1 reply; 7+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-02-10 20:55 UTC (permalink / raw)
Jake Colman <colman@ppllc.com> writes:
> LMI> This means that your cl.el was compiled for Emacs 19.29 or later. So
> LMI> you should use Emacs 19.29 or later when compiling.
>
> Look at my email header: X-Mailer: Gnus v5.5/Emacs 20.2
>
> My initial posting including the output of (emacs-version):
>
> GNU Emacs 20.2.1 (sparc-sun-solaris2.4, X toolkit)
> of Mon Dec 1 1997 on clay.principia.com
>
> Am I missing something obvious? 'cause I'm starting to feel really dumb!
Apparently the Emacs you're using when compiling isn't the same as
you're using when reading. For some reason or other.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: More Build Problems
1998-02-10 20:55 ` Lars Magne Ingebrigtsen
@ 1998-02-10 22:22 ` Jake Colman
0 siblings, 0 replies; 7+ messages in thread
From: Jake Colman @ 1998-02-10 22:22 UTC (permalink / raw)
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Jake Colman <colman@ppllc.com> writes: This means that your cl.el was
LMI> compiled for Emacs 19.29 or later. So you should use Emacs 19.29 or
LMI> later when compiling.
>> Look at my email header: X-Mailer: Gnus v5.5/Emacs 20.2
>>
>> My initial posting including the output of (emacs-version):
>>
>> GNU Emacs 20.2.1 (sparc-sun-solaris2.4, X toolkit) of Mon Dec 1 1997 on
>> clay.principia.com
>>
>> Am I missing something obvious? 'cause I'm starting to feel really dumb!
LMI> Apparently the Emacs you're using when compiling isn't the same as
LMI> you're using when reading. For some reason or other.
For reasons that totally escape me, unless I fully qualify EMACS to point to
the emacs in my ~/bin directory, it is finding the SA-installed version which
is an earlier version. This is happening even though my version of emacs is in
my PATH prior to the SA version.
Go figure...
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~1998-02-10 22:22 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` More Build Problems Jake Colman
1998-02-10 19:11 ` 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
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).