From: Sven Joachim <svenjoac@gmx.de>
To: emacs-devel@gnu.org
Subject: Build failure on Debian unstable
Date: Wed, 23 May 2007 17:20:28 +0200 [thread overview]
Message-ID: <87646jr2gz.fsf@gmx.de> (raw)
Please have a look at http://bugs.debian.org/423462, it says that
Emacs currently fails to build:
[Quoting from the bug report]
,----
| In file included from ./config.h:979,
| from dispnew.c:23:
| ./s/gnu-linux.h:49:24: error: operator '>' has no left operand
| ./s/gnu-linux.h:52:24: error: operator '>=' has no left operand
| ./s/gnu-linux.h:55:24: error: operator '>=' has no left operand
|
| The offending code in gnu-linux.h references LINUX_VERSION_CODE,
|
| #if LINUX_VERSION_CODE > 0x10200
| #define LINUX_SIGIO_DOES_WORK
| #endif /* LINUX_VERSION_CODE > 0x10200 */
| #if LINUX_VERSION_CODE >= 0x20000
| #define LINUX_MAP_SHARED_DOES_WORK
| #endif /* LINUX_VERSION_CODE >= 0x20000 */
| #if LINUX_VERSION_CODE >= 0x20400
|
| ... which is defined in /usr/include/linux/version.h:
|
| #define LINUX_VERSION_CODE
| #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
`----
I verified that this does indeed happen. While it is an incompatible
change that the Debian maintainers did not give LINUX_VERSION_CODE a
version, I tend to agree Steve Langasek that it is very unreliable to
check LINUX_VERSION_CODE to determine the version of the Linux kernel,
since the kernel version is not really related to what
/usr/include/linux/version.h states about it (and it's entirely
possible to build Emacs with a new kernel but run it under an older
one).
next reply other threads:[~2007-05-23 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 15:20 Sven Joachim [this message]
2007-05-23 15:55 ` Build failure on Debian unstable Chong Yidong
2007-05-23 18:53 ` Glenn Morris
2007-05-23 20:15 ` Chong Yidong
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=87646jr2gz.fsf@gmx.de \
--to=svenjoac@gmx.de \
--cc=emacs-devel@gnu.org \
/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).