5:33 a.m.
I noticed this the other day while building XEmacs...
Loading /usr/local/lib/xemacs-21.5-b12/i586-pc-linux/modules/auto-autoloads...
...doesn't look right to me. Why are we loading an installed file at
build time?
Jerry, could you please fix this up.
Thanks.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
7:08 p.m.
Sorry for the delay, Steve. I'm just starting to come up for air after
a very hairy semester. :-)
Steve Youngs <youngs(a)xemacs.org> wrote:
I noticed this the other day while building XEmacs...
Loading /usr/local/lib/xemacs-21.5-b12/i586-pc-linux/modules/auto-autoloads...
...doesn't look right to me. Why are we loading an installed file at
build time?
I just built --with-modules and --with-modules=no, and I did not get
this message in either case. How did you configure XEmacs?
--
Jerry James
http://www.ittc.ku.edu/~james/
1:44 a.m.
|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> Sorry for the delay, Steve. I'm just starting to come up for
JJ> air after a very hairy semester. :-)
That's cool, I've been busy too.
JJ> Steve Youngs <youngs(a)xemacs.org> wrote:
>...doesn't look right to me. Why are we loading an installed
file at
>build time?
JJ> I just built --with-modules and --with-modules=no, and I did not get
JJ> this message in either case. How did you configure XEmacs?
Do you have 21.5 installed or do you run in place? Mine is installed.
`M-x describe-installation'
uname -a: Linux eicq 2.4.20 #1 Mon May 19 13:41:41 EST 2003 i586 unknown
./configure '--extra-verbose'
'--site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1'
'--dynamic=yes' '--with-athena=next' '--with-menubars=lucid'
'--with-scrollbars=athena' '--with-dialogs=athena'
'--with-widgets=athena' '--with-site-lisp=no'
'--with-site-modules' '--with-mule' '--with-xfs' '--debug'
'--error-checking=all' '--memory-usage-stats'
'--with-clash-detection' '--external-widget'
XEmacs 21.5-b13 "cauliflower" (+CVS-20030528) configured for
`i586-pc-linux'.
Compilation / Installation:
Source code location: /usr/local/src/xemacs
Installation prefix: /usr/local
Additional prefixes: /usr/local/pgsql /usr/local/BerkeleyDB.4.1
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -Wall -Wno-switch -Winline -Wmissing-prototypes
-Wsign-compare -Wundef -Wstrict-prototypes -Wshadow -Wmissing-declarations -O1 -ggdb3
-march=k6
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/neXtaw
- Athena library to link: neXtaw
Using Lucid menubars.
Using Athena scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
5:55 a.m.
Steve Youngs <youngs(a)xemacs.org> wrote:
|--==> "JJ" == Jerry James <james(a)xemacs.org>
writes:
JJ> Steve Youngs <youngs(a)xemacs.org> wrote:
>>...doesn't look right to me. Why are we loading an installed file at
>>build time?
JJ> I just built --with-modules and --with-modules=no, and I did not get
JJ> this message in either case. How did you configure XEmacs?
Do you have 21.5 installed or do you run in place? Mine is installed.
I'm confused. Aren't we talking about a build time problem? Why is
installed vs. run-in-place relevant?
./configure '--extra-verbose'
'--site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1'
'--dynamic=yes' '--with-athena=next' '--with-menubars=lucid'
'--with-scrollbars=athena' '--with-dialogs=athena'
'--with-widgets=athena' '--with-site-lisp=no'
'--with-site-modules' '--with-mule' '--with-xfs' '--debug'
'--error-checking=all' '--memory-usage-stats'
'--with-clash-detection' '--external-widget'
XEmacs 21.5-b13 "cauliflower" (+CVS-20030528) configured for
`i586-pc-linux'.
I used the latest CVS sources, too, and basically your configure options
above (plus a few tweaks I have to have to build here), and I still
don't see the modules/auto-autoloads getting loaded. Here's my
configure line:
../xemacs-21.5/configure --prefix=/usr/local/test --mail-locking=flock --extra-verbose
--dynamic=yes --with-dialogs=athena --with-widgets=athena --with-site-lisp=no
--with-site-modules --with-mule --with-xfs --debug --error-checking=all
--memory-usage-stats --with-clash-detection --external-widget
Oh, wait a minute. There *is* a difference here. You are building in
the source tree and I'm not. Sorry, but I *have* to go get some sleep
now. Can you try building elsewhere and see if the problem goes away?
If so, I'll see what I can do about fixing the source tree build
tomorrow. If you don't have time for that experiment, I'll try it
myself in the morning.
By the way, speaking of needing sleep, I'm going in for minor surgery
next Wednesday to (hopefully) fix the problem that has kept me from
sleeping properly at nights for the last 10 years. Hopefully I'll start
getting sufficient rest for a change, which should improve my sharpness,
but I'll also be laid up for about a week while my brain is fogged by
all the pain killers they're going to pump into me. Whee!
--
Jerry "I'm lots of fun when I'm on pain killers" James
http://www.ittc.ku.edu/~james/
6:05 p.m.
I wrote:
I used the latest CVS sources, too, and basically your configure
options
above (plus a few tweaks I have to have to build here), and I still
don't see the modules/auto-autoloads getting loaded. Here's my
configure line:
../xemacs-21.5/configure --prefix=/usr/local/test --mail-locking=flock --extra-verbose
--dynamic=yes --with-dialogs=athena --with-widgets=athena --with-site-lisp=no
--with-site-modules --with-mule --with-xfs --debug --error-checking=all
--memory-usage-stats --with-clash-detection --external-widget
Oh, wait a minute. There *is* a difference here. You are building in
the source tree and I'm not. Sorry, but I *have* to go get some sleep
now. Can you try building elsewhere and see if the problem goes away?
If so, I'll see what I can do about fixing the source tree build
tomorrow. If you don't have time for that experiment, I'll try it
myself in the morning.
I just configured and built inside the source tree with the configure
options above. I'm still not getting the line you saw, Steve. The only
relevant part of the build I can see is this:
Wrote /usr/src/xemacs/build-steve/modules/auto-autoloads.el
Wrote /usr/src/xemacs/build-steve/modules/auto-autoloads.el
Compiling /usr/src/xemacs/build-steve/modules/auto-autoloads.el...
Wrote /usr/src/xemacs/build-steve/modules/auto-autoloads.elc
Loading /usr/src/xemacs/build-steve/lisp/auto-autoloads...
Loading /usr/src/xemacs/build-steve/lisp/mule/auto-autoloads...
Now my configure options aren't *exactly* the same as yours, but the
differences shouldn't affect modules at all. I don't know why the
modules/auto-autoloads.el file is getting written twice. I'll check
that out. But so far I haven't been able to reproduce the behavior
you're seeing. In what part of the build does it happen?
--
Jerry James
http://www.ittc.ku.edu/~james/
10:47 p.m.
|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> In what part of the build does it happen?
,----[ building outside the source tree ]
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.el
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.el
| Compiling /usr/local/src/xemacs/lisp/auto-autoloads.el...
| Wrote /usr/local/src/xemacs/lisp/auto-autoloads.elc
| Compiling /usr/local/src/xemacs/lisp/mule/auto-autoloads.el...
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.elc
| Loading /usr/local/src/bld-xemacs/lisp/auto-autoloads...
| Loading /usr/local/src/bld-xemacs/lisp/mule/auto-autoloads...
| Loading /usr/local/lib/xemacs-21.5-b13/i586-pc-linux/modules/auto-autoloads...
| Compiling /usr/local/src/bld-xemacs/lisp/backquote.el...
| Wrote /usr/local/src/bld-xemacs/lisp/backquote.elc
| Compiling /usr/local/src/bld-xemacs/lisp/bytecomp-runtime.el...
| Wrote /usr/local/src/bld-xemacs/lisp/bytecomp-runtime.elc
| Compiling /usr/local/src/bld-xemacs/lisp/find-paths.el...
| Wrote /usr/local/src/bld-xemacs/lisp/find-paths.elc
`----
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
4:30 p.m.
Steve Youngs <youngs(a)xemacs.org> wrote:
,----[ building outside the source tree ]
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.el
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.el
| Compiling /usr/local/src/xemacs/lisp/auto-autoloads.el...
| Wrote /usr/local/src/xemacs/lisp/auto-autoloads.elc
| Compiling /usr/local/src/xemacs/lisp/mule/auto-autoloads.el...
| Wrote /usr/local/src/xemacs/lisp/mule/auto-autoloads.elc
| Loading /usr/local/src/bld-xemacs/lisp/auto-autoloads...
| Loading /usr/local/src/bld-xemacs/lisp/mule/auto-autoloads...
| Loading /usr/local/lib/xemacs-21.5-b13/i586-pc-linux/modules/auto-autoloads...
| Compiling /usr/local/src/bld-xemacs/lisp/backquote.el...
| Wrote /usr/local/src/bld-xemacs/lisp/backquote.elc
| Compiling /usr/local/src/bld-xemacs/lisp/bytecomp-runtime.el...
| Wrote /usr/local/src/bld-xemacs/lisp/bytecomp-runtime.elc
| Compiling /usr/local/src/bld-xemacs/lisp/find-paths.el...
| Wrote /usr/local/src/bld-xemacs/lisp/find-paths.elc
`----
Here's what I did. I got a fresh checkout from CVS. I configured using as
close a set of configure flags to yours as I could. The differences are in
the GUI (I don't have the NeXT libs), I specified --prefix (I don't have an
XEmacs installed under /usr), and I did not use --site-prefixes (both
PostgreSQL and LDAP are in the normal places). My build log still does not
show the modules auto-autoloads being loaded. Mine goes like this:
Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el
Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el
Compiling /usr/src/xemacs-21.5/lisp/auto-autoloads.el...
Wrote /usr/src/xemacs-21.5/lisp/auto-autoloads.elc
Compiling /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el...
Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.elc
Loading /usr/src/xemacs-21.5/lisp/auto-autoloads...
Loading /usr/src/xemacs-21.5/lisp/mule/auto-autoloads...
Compiling /usr/src/xemacs-21.5/lisp/backquote.el...
Wrote /usr/src/xemacs-21.5/lisp/backquote.elc
I wonder if this code near the bottom of startup.el has anything to do with
it:
;; Hey! Let's use a packages-* function for a non-package purpose!
(when (and (not inhibit-autoloads) (featurep 'modules))
(packages-load-package-auto-autoloads module-load-path))
If you comment that out, does the problem go away? If so, this means that
your temacs is somehow setting its module-load-path to an installed
directory.
--
Jerry James
http://www.ittc.ku.edu/~james/
2:23 a.m.
|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
Just letting you know, Jerry, that I haven't forgotten about this.
And I will get to it RSN[tm], I promise. :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
11:38 a.m.
|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> I just configured and built inside the source tree with the configure
JJ> options above. I'm still not getting the line you saw, Steve.
Here's another piece of the puzzle:
If I build using a virgin source tree (one that has never been built
or configured before), which is what I usually do, I see the installed
modules auto-autoloads file being loaded.
If I build in a tree that has lost its virginity, no installed files
get loaded at build time.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
10:19 p.m.
|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> Steve Youngs <youngs(a)xemacs.org> wrote:
JJ> I just built --with-modules and --with-modules=no, and I did not get
JJ> this message in either case. How did you configure XEmacs?
>
>Do you have 21.5 installed or do you run in place? Mine is installed.
JJ> I'm confused. Aren't we talking about a build time problem? Why is
JJ> installed vs. run-in-place relevant?
Well, if you were running-in-place you wouldn't see the "installed"
version of a file being loaded because when r-i-p the "installed" and
"source" versions are the same.
JJ> Oh, wait a minute. There *is* a difference here. You are building in
JJ> the source tree and I'm not. Sorry, but I *have* to go get some sleep
JJ> now. Can you try building elsewhere and see if the problem goes away?
No it doesn't make any difference. I get the same thing both inside
and outside the source tree.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs(a)xemacs.org>---|
7765
days inactive
7902
days old
9 comments
2 participants
participants (2)
-
Jerry James -
Steve Youngs