3:13 a.m.
Adrian Aichner <adrian(a)xemacs.org> writes:
COMMIT
Vin, do packages build for you again now?
Yes, thank you - modulo the ps-print bug I just submitted a patch for
and the ilisp-mak.el patch I previously submitted.
Idle thought: when building ilisp, why does no one else see this
problem:
While compiling toplevel forms in file
/opt/build/xemacs-packages-2002-06-10/xemacs-packages/ilisp/ilisp-cl-easy-menu.el:
!! File error (("Cannot open load file" "thingatpt"))
Cannot open load file: thingatpt
xemacs exiting
This is the symptom that caused me to submit a patch for ilisp-mak.el:
http://list-archive.xemacs.org/xemacs-patches/200206/msg00021.html
'thingatpt' comes from fsf-compat, so somehow fsf-compat needs to be
loaded when ilisp-mak.el is run.
- Vin
4:58 a.m.
New subject: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout
|--==> "VS" == Vin Shelton <acs(a)xemacs.org> writes:
VS> Idle thought: when building ilisp, why does no one else see this
VS> problem:
VS> While compiling toplevel forms in file
/opt/build/xemacs-packages-2002-06-10/xemacs-packages/ilisp/ilisp-cl-easy-menu.el:
VS> !! File error (("Cannot open load file" "thingatpt"))
VS> Cannot open load file: thingatpt
VS> xemacs exiting
I'm really not sure why you are seeing this. I've just successfully
built ilisp with 21.1, 21.4, 21.5 (Mule and non-Mule for each
version).
Perhaps something has gone belly up in your workspace for some
reason. Try nuking your ilisp directory and check it out of CVS
again.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
2:05 p.m.
New subject: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout
Steve Youngs <youngs(a)xemacs.org> writes:
|--==> "VS" == Vin Shelton <acs(a)xemacs.org>
writes:
VS> Idle thought: when building ilisp, why does no one else see this
VS> problem:
VS> While compiling toplevel forms in file
/opt/build/xemacs-packages-2002-06-10/xemacs-packages/ilisp/ilisp-cl-easy-menu.el:
VS> !! File error (("Cannot open load file" "thingatpt"))
VS> Cannot open load file: thingatpt
VS> xemacs exiting
I'm really not sure why you are seeing this. I've just successfully
built ilisp with 21.1, 21.4, 21.5 (Mule and non-Mule for each
version).
Perhaps something has gone belly up in your workspace for some
reason. Try nuking your ilisp directory and check it out of CVS
again.
Highly unlikely. I'm seeing this both at work and at home (in
separate repositories). Do you build from scratch each time? I do.
Can you try a non-mule build from scratch?
Thanks,
Vin
12:35 a.m.
New subject: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout
|--==> "VS" == Vin Shelton <shelton(a)icd.teradyne.com> writes:
VS> Steve Youngs <youngs(a)xemacs.org> writes:
VS> Cannot open load file: thingatpt
VS> xemacs exiting
>I'm really not sure why you are seeing this. I've just
successfully
>built ilisp with 21.1, 21.4, 21.5 (Mule and non-Mule for each
>version).
VS> Do you build from scratch each time? I do.
As in "make distclean, make whatever"? From
/packages/xemacs-packages/pkgname/ - Yes, always. From /packages/ -
Hardly ever.
VS> Can you try a non-mule build from scratch?
In the tests that I did, 3 were from non-Mule XEmacsen, and 3 were
from Mule XEmacsen. All builds were done from
/packages/xemacs-packages/ilisp/ using 'make distclean; make
bindist'.
I'll try building from /packages/ in a virgin tree...
[ time passes ]
[ lots of time passes ] (I'd forgotten how long it takes to build
_all_ the packages from scratch).
Nope. No problems building ilisp, or any other standard package.
That was using XEmacs 21.1.14 non-Mule.
I can't think of any reason why it doesn't work for you, Vin. I still
think you should try:
cd /packages/xemacs-packages/
rm -rf ilisp/
cvs up -Pd
I know that it's not likely to help, but what have you got to lose.
And, besides, I can't think of anything else to suggest. :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
2:52 p.m.
New subject: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout
Steve Youngs <youngs(a)xemacs.org> writes:
|--==> "VS" == Vin Shelton
<shelton(a)icd.teradyne.com> writes:
VS> Steve Youngs <youngs(a)xemacs.org> writes:
VS> Cannot open load file: thingatpt
VS> xemacs exiting
>>I'm really not sure why you are seeing this. I've just successfully
>>built ilisp with 21.1, 21.4, 21.5 (Mule and non-Mule for each
>>version).
VS> Do you build from scratch each time? I do.
As in "make distclean, make whatever"? From
/packages/xemacs-packages/pkgname/ - Yes, always. From /packages/ -
Hardly ever.
I always make a copy of the entire CVS package source tree and build
from a brand spanking new hierarchy.
VS> Can you try a non-mule build from scratch?
In the tests that I did, 3 were from non-Mule XEmacsen, and 3 were
from Mule XEmacsen. All builds were done from
/packages/xemacs-packages/ilisp/ using 'make distclean; make
bindist'.
I'll try building from /packages/ in a virgin tree...
[ time passes ]
[ lots of time passes ] (I'd forgotten how long it takes to build
_all_ the packages from scratch).
Nope. No problems building ilisp, or any other standard package.
That was using XEmacs 21.1.14 non-Mule.
I can't think of any reason why it doesn't work for you, Vin. I still
think you should try:
cd /packages/xemacs-packages/
rm -rf ilisp/
cvs up -Pd
I know that it's not likely to help, but what have you got to lose.
And, besides, I can't think of anything else to suggest. :-)
OK. I did that. No luck. I even re-fetched the entire package
hierarchy via 'cvs checkout'. There were no differences in my ilisp
directory.
Let's try a different approach. When I go to the ilisp directory and
run:
- make distclean
- make -n
Here's the output from 'make -n':
echo Creating ./_pkg.el
echo ";;;###autoload" > ./_pkg.el
echo "(package-provide 'ilisp" >> ./_pkg.el
echo " :version 1.26" >> ./_pkg.el
echo " :type 'regular)" >> ./_pkg.el
xemacs -batch -l ilisp-mak.el
xemacs -no-autoloads -batch -l
/u/shelton2/software/build/xemacs-packages-2002-06-13/package-compile.el -- xemacs-base
mail-lib fsf-compat eterm -- -f batch-byte-compile extra/hyperspec.el extra/cltl2.el
xemacs -no-autoloads -batch -l
/u/shelton2/software/build/xemacs-packages-2002-06-13/package-compile.el -- xemacs-base
mail-lib fsf-compat eterm -- -f batch-byte-compile extra/hyperspec.el
xemacs -no-autoloads -batch -l
/u/shelton2/software/build/xemacs-packages-2002-06-13/package-compile.el -- xemacs-base
mail-lib fsf-compat eterm -- -f batch-byte-compile extra/cltl2.el
xemacs -vanilla -batch -no-autoloads \
-eval "(setq autoload-package-name \"ilisp\")" \
-eval "(setq generated-autoload-file
\"./auto-autoloads.el\")" \
-l autoload -f batch-update-autoloads ilisp.el bridge.el comint-ipc.el
completer.el ild.el ilisp-cl-easy-menu.el ilisp-imenu.el ilisp-scheme-easy-menu.el
ilisp-def.el ilisp-sym.el ilisp-inp.el ilisp-ind.el ilisp-prc.el ilisp-val.el ilisp-ccl.el
ilisp-openmcl.el ilisp-out.el ilisp-mov.el ilisp-key.el ilisp-prn.el ilisp-low.el
ilisp-doc.el ilisp-ext.el ilisp-mod.el ilisp-dia.el ilisp-cmt.el ilisp-rng.el ilisp-hnd.el
ilisp-utl.el ilisp-cmp.el ilisp-kil.el ilisp-snd.el ilisp-xfr.el ilisp-hi.el ilisp-aut.el
ilisp-cl.el ilisp-cmu.el ilisp-sbcl.el ilisp-acl.el ilisp-kcl.el ilisp-luc.el ilisp-sch.el
ilisp-hlw.el ilisp-xls.el ilisp-chs.el ilxemacs.el _pkg.el
rm -f ./auto-autoloads.el~
xemacs -no-autoloads -batch -l
/u/shelton2/software/build/xemacs-packages-2002-06-13/package-compile.el -- xemacs-base
mail-lib fsf-compat eterm -- -f batch-byte-compile auto-autoloads.el
makeinfo -o docs/ilisp.info docs/ilisp.texi
It is 'xemacs -batch -l ilisp-mak.el' that eventually gets the
following error:
Loading
/u/shelton2/software/build/xemacs-packages-2002-06-13/xemacs-packages/ilisp/ilisp-sch.elc...
Compiling
/u/shelton2/software/build/xemacs-packages-2002-06-13/xemacs-packages/ilisp/ilisp-cl-easy-menu.el...
Loading extra/hyperspec...
While compiling toplevel forms in file
/u/shelton2/software/build/xemacs-packages-2002-06-13/xemacs-packages/ilisp/ilisp-cl-easy-menu.el:
!! File error (("Cannot open load file" "thingatpt"))
Cannot open load file: thingatpt
xemacs exiting
.
make: *** [compile] Error 255
Compilation exited abnormally with code 2 at Thu Jun 13 09:35:55
thingatpt comes from fsf-compat. How does your
xemacs -batch -l ilisp-mak.el
load fsf-compat without my hack to modify the load-path?
Or is your $(XEMACS) macro defined to something other than 'xemacs'.
(Note: $(XEMACS) is not the same as $(BOOT_XEMACS), which sucks in
all the $(REQUIRES).)
Seeking enlightenment,
Vin
12:17 a.m.
New subject: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout
|--==> "VS" == Vin Shelton <shelton(a)icd.teradyne.com> writes:
VS> Cannot open load file: thingatpt
VS> xemacs exiting
OK, here's the answer...
In the Makefile target 'compile':
$(XEMACS) -batch -l ilisp-mak.el
Should be
$(BOOT_XEMACS) -l ilisp-mak.el
The reason that you were seeing the problem and I wasn't was because
you didn't have an installed fsf-compat package and I did.
The fix will be in CVS shortly.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
8011
days inactive
8014
days old
5 comments
3 participants
participants (3)
-
Steve Youngs -
Vin Shelton -
Vin Shelton