From: Rob Browning <rlb@defaultvalue.org>
Cc: eliz@is.elta.co.il, ats@acm.org, emacs-devel@gnu.org
Subject: Re: Building emacs with and without X -- packaging question.
Date: Mon, 24 Jun 2002 01:00:07 -0500 [thread overview]
Message-ID: <87hejt1ajc.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <200206231813.g5NID8m24504@aztec.santafe.edu> (Richard Stallman's message of "Sun, 23 Jun 2002 12:13:08 -0600 (MDT)")
Richard Stallman <rms@gnu.org> writes:
> Can you arrange to see the list of directories in both cases, and
> compare them? If they are different, can you find out where the
> difference originates from?
Sure.
I changed the lisp/Makefile.in custom-deps rule as follows. The only
difference it to write a timestamped file containing $$wins to /tmp.
The resulting files (one from the X build, and one from the no-X
build) were identical, but the cus-load.el files in the two resulting
build trees were still different.
custom-deps: cus-load.el doit
wd=$(lisp); $(setwins); \
echo Directories: $$wins; \
echo $$wins | sort | perl -pe 's/ /\n/gmo' > /tmp/cdep-$$(datestamp); \
$(EMACS) $(EMACSOPT) -l cus-dep -f custom-make-dependencies $$wins
If it matters, I perform the two builds in separate build directories
using the standard "${srcdir}/configure ..." approach, and I perform a
"make boostrap" for each.
However, before we go any further, let me try this again using the
unmodified upstream source. I should have thought to do that
initially, but I didn't. So let me make sure this isn't being caused
by any of the debian diffs.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
next prev parent reply other threads:[~2002-06-24 6:00 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 17:25 Building emacs with and without X -- packaging question Rob Browning
2002-05-31 18:41 ` Eli Zaretskii
2002-05-31 19:08 ` Alan Shutko
[not found] ` <7999-Sat01Jun2002102420+0300-eliz@is.elta.co.il>
2002-06-01 16:42 ` Alan Shutko
2002-06-01 16:50 ` Eli Zaretskii
2002-06-10 19:13 ` Rob Browning
2002-06-10 19:45 ` Alan Shutko
2002-06-10 19:52 ` Stefan Monnier
2002-06-10 20:17 ` Alan Shutko
2002-06-11 5:36 ` Eli Zaretskii
2002-06-11 12:37 ` Alan Shutko
2002-06-12 13:49 ` Juanma Barranquero
2002-06-13 5:21 ` Eli Zaretskii
2002-06-13 10:23 ` Juanma Barranquero
2002-06-13 11:42 ` Eli Zaretskii
2002-06-13 13:51 ` Juanma Barranquero
2002-06-13 14:03 ` Eli Zaretskii
2002-06-13 15:06 ` Juanma Barranquero
2002-06-13 15:16 ` Eli Zaretskii
2002-06-13 16:33 ` Juanma Barranquero
2002-06-14 15:47 ` Richard Stallman
2002-06-15 15:55 ` Eli Zaretskii
2002-06-13 21:47 ` Richard Stallman
2002-06-14 7:08 ` Juanma Barranquero
2002-06-15 15:54 ` Eli Zaretskii
2002-06-20 21:45 ` Rob Browning
2002-06-21 15:33 ` Eli Zaretskii
2002-06-21 17:16 ` Rob Browning
2002-06-22 16:02 ` Rob Browning
2002-06-23 18:13 ` Richard Stallman
2002-06-24 6:00 ` Rob Browning [this message]
2002-06-24 14:55 ` Rob Browning
2002-06-24 19:39 ` Richard Stallman
2002-06-24 19:44 ` Rob Browning
2002-06-24 20:16 ` Stefan Monnier
2002-06-25 4:23 ` Eli Zaretskii
2002-06-25 15:24 ` Rob Browning
2002-06-25 15:52 ` Eli Zaretskii
2002-06-26 22:24 ` Richard Stallman
2002-06-26 22:53 ` Rob Browning
2002-06-25 23:32 ` Richard Stallman
2002-07-31 20:03 ` Rob Browning
2002-08-01 16:52 ` Richard Stallman
2002-08-01 17:01 ` Rob Browning
2002-08-02 17:43 ` Richard Stallman
2002-08-02 6:11 ` Richard Stallman
2002-08-02 15:46 ` Rob Browning
2002-08-04 2:52 ` Richard Stallman
2002-09-14 21:16 ` Rob Browning
2002-09-17 15:32 ` Rob Browning
2002-09-20 4:18 ` Rob Browning
2002-08-09 6:54 ` Stefan Monnier
2002-06-10 20:01 ` Rob Browning
2002-06-01 21:04 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hejt1ajc.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=ats@acm.org \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).