From: Svante Signell <svante.signell@telia.com>
To: Glenn Morris <rgm@gnu.org>
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: Mon, 02 Jul 2012 23:10:28 +0200 [thread overview]
Message-ID: <1341263428.16363.14.camel@x60> (raw)
In-Reply-To: <t8txxryosp.fsf@fencepost.gnu.org>
On Sun, 2012-07-01 at 20:44 -0400, Glenn Morris wrote:
> 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...
My question should be read: Where in the build log can I find where cpp
modifies the Makefile?
> 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
Yes, 24.1 builds and even the upcoming Debian version does (when
libselinux1-dev dependency is removed) :) There are still 34 packages
biuld-depending on 23.4, but that might change in due time too.
> > 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:
I have removed the debian patches one at a time. No difference. And
these patches touch other files, compared to the ones causing the
problems. The only way to get a successful build is to remove the patch
where GNU is replaced for NEWS to find etc, and make a symlink of the
build etc/charsets directory to /usr/share/emacs/23.4/etc. (or use an
installed emacs-23.4).
> > 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
They use cp -a, but that is the same isn't it?
>
>
> The loaddefs difference looks like it could be an Emacs bug; but it
> ought to be harmless in itself.
I think the problem lies in the loaddefs.el being regenerated by the
autoloads. My problem is that I don't know why it happens, compared to
the tarball.
next prev parent reply other threads:[~2012-07-02 21:10 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
2012-07-02 4:30 ` Glenn Morris
2012-07-02 21:15 ` Svante Signell
2012-07-02 21:10 ` Svante Signell [this message]
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
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=1341263428.16363.14.camel@x60 \
--to=svante.signell@telia.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=schwab@linux-m68k.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).