From: Glenn Morris <rgm@gnu.org>
To: svante.signell@telia.com
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Need help with upstream vs Debian emacs-23.4 build differences
Date: Sun, 01 Jul 2012 20:44:38 -0400 [thread overview]
Message-ID: <t8txxryosp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 1340956879.32095.215.camel@hp.my.own.domain
Dropping help-gnu-emacs since there is no point discussing this on two
lists.
Svante Signell wrote:
> Is cpp used to process the Makefiles, if so where to find it?
In 23.4, yes. Where to find cpp? I don't understand the question...
The latest release is 24.1, which does not use cpp. I would encourage
you to try that and not worry about 23.4.
http://packages.qa.debian.org/e/emacs24.html
> Another piece of information is that when replacing the dumped emacs
> from Debian with the one from the tarball, build is OK! So it seem that
> the differences are in temacs or the dumped emacs.
IIUC, Debian includes several patches to the Emacs sources.
You might start by selectively removing them.
Also, I never understood what this means:
> However, on Debian the whole source tree is copied to debian/build-?
> where ?=x,nox,lucid.
You mean;
tar zvxf emacs-23.4.tar.gz
cp -pr emacs-23.4 debian/build-x
etc
?
The loaddefs difference looks like it could be an Emacs bug; but it
ought to be harmless in itself.
next prev parent reply other threads:[~2012-07-02 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 23:09 Need help with upstream vs Debian emacs-23.4 build differences Svante Signell
2012-06-29 6:49 ` Andreas Schwab
2012-06-29 8:01 ` Svante Signell
2012-07-02 0:44 ` Glenn Morris [this message]
2012-07-02 4:30 ` Glenn Morris
2012-07-02 21:15 ` Svante Signell
2012-07-02 21:10 ` Svante Signell
2012-07-05 11:47 ` Need help with upstream vs Debian emacs-23.4 + emacs-24.1 " Svante Signell
2012-07-05 16:06 ` Glenn Morris
2012-07-01 20:58 ` Need help with upstream vs Debian emacs-23.4 " Svante Signell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=t8txxryosp.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=svante.signell@telia.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.