9:20 p.m.
If I do "make install" in a package that doesn't have an
auto-autoloads file, it fails.
To reproduce, I guess it would be enough to remove auto* from disk and
the Makefile on an existing package and try to compile it.
bash-2.05b$ make install
(if test -d /home/jas/lib/xemacs/xemacs-packages/; then \
cd /home/jas/lib/xemacs/xemacs-packages/; \
if test -f pkginfo/MANIFEST.sasl; then \
rm -rf `cat pkginfo/MANIFEST.sasl`; \
fi; \
fi;)
cp --force --recursive --symbolic-link
/data4/jas/laptop/src/packages/unsupported/simon/sasl/ChangeLog
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-def.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-md5.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-sha1.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/ntlm.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-cram.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-digest.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-ntlm.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-scram.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-def.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-md5.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/hmac-sha1.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/ntlm.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-cram.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-digest.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-ntlm.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/sasl-scram.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/./auto-autoloads.elc
/data4/jas/laptop/src/packages/unsupported/simon/sasl/./auto-autoloads.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/./_pkg.el
/data4/jas/laptop/src/packages/unsupported/simon/sasl/README \
/home/jas/lib/xemacs/xemacs-packages//lisp/sasl
cp: cannot stat
`/data4/jas/laptop/src/packages/unsupported/simon/sasl/./auto-autoloads.elc': No such
file or directory
cp: cannot stat
`/data4/jas/laptop/src/packages/unsupported/simon/sasl/./auto-autoloads.el': No such
file or directory
make: *** [binkit-common] Error 1
bash-2.05b$
10:08 p.m.
On Fri, 2002-08-02 at 23:20, Simon Josefsson wrote:
If I do "make install" in a package that doesn't have
an
auto-autoloads file, it fails.
[...]
A couple of suggestions:
1) Invent some autoloads :)
2) Remove auto-autoloads.elc from Makefile (all::) and use
"GENERATED = ..." instead of the normal "GENERATED += ..." in
Makefile. This may break sometime, though.
--
\/ille Skyttä
ville.skytta at xemacs.org
10:30 p.m.
Ville Skyttä <ville.skytta(a)xemacs.org> writes:
On Fri, 2002-08-02 at 23:20, Simon Josefsson wrote:
> If I do "make install" in a package that doesn't have an
> auto-autoloads file, it fails.
[...]
A couple of suggestions:
1) Invent some autoloads :)
I did that on ecrypto, but I couldn't really invent good ones on
SASL..
2) Remove auto-autoloads.elc from Makefile (all::) and use
"GENERATED = ..." instead of the normal "GENERATED += ..." in
Makefile. This may break sometime, though.
Doesn't help, that's why I complained. It solves the problem for
"make", but "make install" seems to hard code auto-autoloads.el*
somewhere. I guess I will do the following if it isn't to fix
otherwise.
3) Put "touch auto-autoloads.el auto-autoloads.elc" in makefile
11:01 p.m.
On Sat, 2002-08-03 at 00:30, Simon Josefsson wrote:
>> If I do "make install" in a package that
doesn't have an
>> auto-autoloads file, it fails.
> [...]
>
> A couple of suggestions:
>
> 1) Invent some autoloads :)
I did that on ecrypto, but I couldn't really invent good ones on
SASL..
Ok...
> 2) Remove auto-autoloads.elc from Makefile (all::) and use
> "GENERATED = ..." instead of the normal "GENERATED += ..." in
> Makefile. This may break sometime, though.
Doesn't help, that's why I complained. It solves the problem for
"make", but "make install" seems to hard code auto-autoloads.el*
somewhere.
Ahem, you _don't_ have the "GENERATED =" in sasl/Makefile. GENERATED
contains $(AUTOLOAD_PATH)/auto-autoloads.elc by default, from
XEmacs.rules, so it needs to be emptied... here's the patch:
Index: simon/sasl/Makefile
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/unsupported/simon/sasl/Makefile,v
retrieving revision 1.2
diff -a -u -r1.2 Makefile
--- simon/sasl/Makefile 2002/08/02 20:45:13 1.2
+++ simon/sasl/Makefile 2002/08/02 22:00:08
＠＠ -35,6 +35,8 ＠＠
include ../../XEmacs.rules
+GENERATED =
+
all:: $(ELCS) $(INFO_FILES)
srckit: srckit-std
--
\/ille Skyttä
ville.skytta at xemacs.org
11:22 p.m.
Ville Skyttä <ville.skytta(a)xemacs.org> writes:
> > 2) Remove auto-autoloads.elc from Makefile (all::) and use
> > "GENERATED = ..." instead of the normal "GENERATED +=
..." in
> > Makefile. This may break sometime, though.
>
> Doesn't help, that's why I complained. It solves the problem for
> "make", but "make install" seems to hard code auto-autoloads.el*
> somewhere.
Ahem, you _don't_ have the "GENERATED =" in sasl/Makefile. GENERATED
contains $(AUTOLOAD_PATH)/auto-autoloads.elc by default, from
XEmacs.rules, so it needs to be emptied... here's the patch:
Ouch, you are right, I thought removing was enough. It works, thanks.
3:41 p.m.
|--==> "SJ" == Simon Josefsson <jas(a)extundo.com> writes:
SJ> If I do "make install" in a package that doesn't have an
SJ> auto-autoloads file, it fails.
Can't happen. Every package will have an auto-autoloads.el file
because _pkg.el has an autoload cookie in it.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
5:21 p.m.
Steve Youngs <youngs(a)xemacs.org> writes:
|--==> "SJ" == Simon Josefsson <jas(a)extundo.com>
writes:
SJ> If I do "make install" in a package that doesn't have an
SJ> auto-autoloads file, it fails.
Can't happen. Every package will have an auto-autoloads.el file
because _pkg.el has an autoload cookie in it.
The automatically generated _pkg.el file doesn't have any autoload
cookies, at least not when I try it ("make distclean" + "make" in
e.g. unsupported/simon/sasl/).
The hint to put "GENERATED=" in Makefile worked though.
8143
days inactive
8148
days old
6 comments
3 participants
participants (3)
-
Simon Josefsson -
Steve Youngs -
Ville Skyttä