unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Sven Joachim <svenjoac@gmx.de>, emacs-devel@gnu.org
Subject: Re: Build failure on Debian unstable
Date: Wed, 23 May 2007 14:53:59 -0400	[thread overview]
Message-ID: <tbqgb8j7c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87odkbfsbb.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 23 May 2007 11:55:20 -0400")

Chong Yidong wrote:

> From reading the bug report, it seems that many software packages,
> including the Sendmail and Postfix mail transport agents, do the same
> thing.  So this should not be urgent enough to block the Emacs 22.1
> release.

Perhaps Debian will revert this problematic change. For now, we could
add a PROBLEMS entry about it. I know the version number could be
worked out more elegantly, I tried to find a portable way. Maybe there
is a better way.


*** Compiling on a GNU/Linux system fails with a missing left operand in gnu-linux.h

The actual error messages have the form:

  ../src/s/gnu-linux.h:49:24: error: operator '>' has no left operand

This error occurs because your system defines LINUX_VERSION_CODE in
the standard header file linux/version.h but does not give it a value.
As a workaround, you can edit the file src/s/gnu-linux.h to add the
needed definition.  On the line after "#include <linux/version.h>",
add a line as shown below:

#include <linux/version.h>
#define LINUX_VERSION_CODE 132626

The number to use depends on your kernel version (the example shown
is for kernel 2.6.18).  The number can be obtained by running this
command in the shell:

uname -r | sed -e 's/\./ /g' -e 's/-.*//' | awk '{print $1*(2^16) + $2*(2^8) + $3}'

  reply	other threads:[~2007-05-23 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 15:20 Build failure on Debian unstable Sven Joachim
2007-05-23 15:55 ` Chong Yidong
2007-05-23 18:53   ` Glenn Morris [this message]
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=tbqgb8j7c.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=svenjoac@gmx.de \
    /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).