unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: bug-gnu-emacs@gnu.org
Cc: Steve Langasek <steve.langasek@canonical.com>,
	620795@bugs.debian.org, 620795-forwarded@bugs.debian.org
Subject: Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS)
Date: Wed, 13 Apr 2011 22:56:03 -0500	[thread overview]
Message-ID: <87sjtl4hbg.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <20110404090605.9635.62532.reportbug@virgil.dodds.net> (Steve Langasek's message of "Mon, 04 Apr 2011 02:06:05 -0700")


(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, and with
multiarch, include paths will include strings like "i386" that cpp will
replace with nonsensical values. i.e.

  -I/usr/lib/i386-linux-gnu/glib-2.0 -> -I/usr/lib/1-linux-gnu/glib-2.0

Steve Langasek <steve.langasek@canonical.com> writes:

> Having begun to convert libraries over to multiarch in Ubuntu, we've found
> emacs23 among the packages which fails to build.  This is because the
> two-stage, autoconf+cpp generation of src/Makefile and lib-src/Makefile
> results in strings like "-I/usr/lib/i386-linux-gnu/glib-2.0" being seen as
> input to cpp... which has "i386" as a macro defined to "1".  So unless these
> macros are undefined, the path that winds up in the Makefile is broken and
> results in a build failure.
>
> The attached patch partially addresses this by undefining any macros that
> happen to exist for the <cpu> portion of the architecture triplet.  Only
> architectures for which Ubuntu currently builds are handled here, however;
> for Debian either a more comprehensive list or a generic fix is needed. 
> It's possible that passing -fdirectives-only to cpp would solve this, but I
> haven't tested.

Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620795 for
additional information.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4




       reply	other threads:[~2011-04-14  3:56 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 ` Rob Browning [this message]
2011-04-14  4:46   ` bug#8497: Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS) Eli Zaretskii
2011-04-16  1:51   ` 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

  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=87sjtl4hbg.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=620795-forwarded@bugs.debian.org \
    --cc=620795@bugs.debian.org \
    --cc=bug-gnu-emacs@gnu.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 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).