--- Begin Message ---
Subject: |
23.1; emacs is failing to build on Fedora 12 64 bit |
Date: |
Thu, 26 Nov 2009 19:45:59 +0530 |
Hi,
emacs build is failing on Fedora 12 GNU/Linux 64 bit due to what
appears to be missing end of line escape characters ('\') in the
Makefile.
I reported this to fedora bugzilla (
https://bugzilla.redhat.com/show_bug.cgi?id=540921 ), but I think it
is not specific to fedora packaging as
tarballs downloaded from gnu mirrors also fails to build.
Regards
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
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#5047: 23.1; emacs is failing to build on Fedora 12 64 bit |
Date: |
Mon, 30 Nov 2009 11:59:25 +0100 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 |
Ah, I tested with Emacs from CVS head. This has been fixed there:
2009-10-23 Jim Meyering <meyering@redhat.com>
* configure.in: Invoke $CPP with -P when creating Makefile and
src/Makefile. Without this, gcc 4.4.2 converts each
backslash-newline pair in the input to a bare newline, yielding
invalid Makefiles.
Running
% CPPFLAGS=-P ./configure ...
works. This is what you have to do until 23.2 comes out.
Jan D.
Praveen A skrev 2009-11-30 10.19:
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
--- End Message ---