From: Praveen A <pravi.a@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 5047@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#5047: 23.1; emacs is failing to build on Fedora 12 64 bit
Date: Mon, 30 Nov 2009 14:49:16 +0530 [thread overview]
Message-ID: <3f2beab60911300119h502dc5caxce5c16c5b0e8e2fd@mail.gmail.com> (raw)
In-Reply-To: <4B124669.2010306@swipnet.se>
2009/11/29 Jan Djärv <jan.h.d@swipnet.se>:
> I've tried this on Fedora 12 and I do not get the error.
> Please show us the exact commands you do, and the output from
> gcc --version.
>
> Also check if you have any environment variable that may have impact on
> configure, such as CFLAGS, CPPFLAGS, GCC. To make sure environment isn't
> the cause, try something like:
>
> % env -i HOME="$HOME" PATH="$PATH" SHELL="$SHELL" TERM="$TERM" ./configure
> ...
>
> I haven't tried that, so you may have to add some variables if configure
> complains.
>
> Thanks,
>
> Jan D.
>
See https://bugzilla.redhat.com/show_bug.cgi?id=540921#c4
It is an issue with cpp 4.4.2, it does not happen with older version of cpp.
- Praveen
--
പ്രവീണ് അരിമ്പ്രത്തൊടിയില്
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
Join The DRM Elimination Crew Now!
http://fci.wikia.com/wiki/Anti-DRM-Campaign
next prev parent reply other threads:[~2009-11-30 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 14:15 bug#5047: 23.1; emacs is failing to build on Fedora 12 64 bit Praveen A
2009-11-27 16:42 ` Jan Djärv
2009-11-28 7:12 ` Praveen A
2009-11-28 8:22 ` Praveen A
2009-11-28 11:39 ` Jan Djärv
2009-11-28 14:15 ` Praveen Arimbrathodiyil
2009-11-29 10:01 ` Jan Djärv
2009-11-30 9:19 ` Praveen A [this message]
2009-11-30 10:59 ` Jan Djärv
2009-11-30 11:05 ` bug#5047: marked as done (23.1; emacs is failing to build on Fedora 12 64 bit) Emacs bug Tracking System
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=3f2beab60911300119h502dc5caxce5c16c5b0e8e2fd@mail.gmail.com \
--to=pravi.a@gmail.com \
--cc=5047@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=jan.h.d@swipnet.se \
/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.