From: Eli Zaretskii <eliz@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 620795-forwarded@bugs.debian.org, 8497-done@debbugs.gnu.org,
steve.langasek@canonical.com, 620795@bugs.debian.org
Subject: bug#8497: Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS)
Date: Thu, 14 Apr 2011 00:46:06 -0400 [thread overview]
Message-ID: <E1QAERS-0001lU-4f__24672.1248412088$1302757654$gmane$org@fencepost.gnu.org> (raw)
In-Reply-To: <87sjtl4hbg.fsf@raven.defaultvalue.org> (message from Rob Browning on Wed, 13 Apr 2011 22:56:03 -0500)
> From: Rob Browning <rlb@defaultvalue.org>
> Date: Wed, 13 Apr 2011 22:56:03 -0500
> Cc: 620795-forwarded@bugs.debian.org,
> Steve Langasek <steve.langasek@canonical.com>, 620795@bugs.debian.org
>
>
> (If possible, please preserve the 620795-forwarded address in any replies.)
>
> Debian is likely to migrate to multiarch, and it appears that the
> transition will probably break the Emacs build process.
>
> The problem is that Emacs uses cpp to process the Makefiles
It no longer does in the development trunk. However, that change is
not (and probably will not be) in the emacs-23 release branch, only in
Emacs 24 when that is released.
So I'm closing this bug.
next prev parent reply other threads:[~2011-04-14 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110404090605.9635.62532.reportbug@virgil.dodds.net>
2011-04-14 3:56 ` Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS) Rob Browning
2011-04-14 4:46 ` Eli Zaretskii [this message]
2011-04-16 1:51 ` bug#8497: " Glenn Morris
2011-04-16 2:12 ` Steve Langasek
2011-04-16 16:29 ` Rob Browning
2011-04-17 17:35 ` Rob Browning
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='E1QAERS-0001lU-4f__24672.1248412088$1302757654$gmane$org@fencepost.gnu.org' \
--to=eliz@gnu.org \
--cc=620795-forwarded@bugs.debian.org \
--cc=620795@bugs.debian.org \
--cc=8497-done@debbugs.gnu.org \
--cc=rlb@defaultvalue.org \
--cc=steve.langasek@canonical.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.