From: Glenn Morris <rgm@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: Steve Langasek <steve.langasek@canonical.com>, 8497@debbugs.gnu.org
Subject: bug#8497: Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS)
Date: Fri, 15 Apr 2011 21:51:00 -0400 [thread overview]
Message-ID: <rr8vvb2ccb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87sjtl4hbg.fsf@raven.defaultvalue.org> (Rob Browning's message of "Wed, 13 Apr 2011 22:56:03 -0500")
Rob Browning wrote:
> (If possible, please preserve the 620795-forwarded address in any replies.)
Sorry, not so long as bug#63995 exists.
>> The attached patch partially addresses this by undefining any macros that
>> happen to exist for the <cpu> portion of the architecture triplet.
Note the following in configure.in attempts to do this kind of thing already:
# Now get this: Some word that is part of the ${srcdir} directory name
# or the ${configuration} value might, just might, happen to be an
# identifier like `sun4' or `i386' or something, and be predefined by
# the C preprocessor to some helpful value like 1, or maybe the empty
# string. Needless to say consequent macro substitutions are less
# than conducive to the makefile finding the correct directory.
[cpp_undefs="`echo $srcdir $configuration $canonical unix |
sed -e 's/[^a-zA-Z0-9_]/ /g' -e 's/^/ /' -e 's/ *$//' \
-e 's/ */ -U/g' -e 's/-U[0-9][^ ]*//g'`"]
so it's not obvious to me why you need to do more (maybe $canonical is
i686-something but your directories are i386-something?).
next prev parent reply other threads:[~2011-04-16 1:51 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 ` bug#8497: " Eli Zaretskii
2011-04-16 1:51 ` Glenn Morris [this message]
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=rr8vvb2ccb.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8497@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.