All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: nfs@lists.sourceforge.net
Subject: Build failure
Date: Fri, 8 Jun 2007 12:24:57 +0200	[thread overview]
Message-ID: <20070608102457.GA3154@uio.no> (raw)

Hi,

Today nfs-utils stopped building for me, probably due to a libc update or
something. The failed part was, from support/include/nfs/nfs.h:

   #include <linux/version.h>
   #if LINUX_VERSION_CODE > KERNEL_VERSION(2,5,70)
   # define __nfsd_dev_t  __kernel_old_dev_t
   #else
   # define __nfsd_dev_t  __kernel_dev_t
   #endif

The failure from gcc was:

   gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I../../support/include -D_GNU_SOURCE -Wall  -pipe -g -O2 -Wall -MT client.o -MD -MP -MF .deps/client.Tpo -c -o client.o client.c
   In file included from ../../support/include/nfslib.h:22,
                    from client.c:22:
   ../../support/include/nfs/nfs.h:73:24: error: operator '>' has no left operand
   In file included from ../../support/include/nfslib.h:22,
                    from client.c:22:
   ../../support/include/nfs/nfs.h:83: error: expected specifier-qualifier-list before '__kernel_dev_t'
   ../../support/include/nfs/nfs.h:104: error: expected specifier-qualifier-list before '__kernel_dev_t'

Is userspace allowed to assume that a symbol such as LINUX_VERSION_CODE
exists at all?

/* Steinar */
-- 
Homepage: http://www.sesse.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-06-08 10:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 10:24 Steinar H. Gunderson [this message]
2007-06-08 10:47 ` Build failure Steinar H. Gunderson
  -- strict thread matches above, loose matches on Subject: below --
2008-07-30  9:29 build failure Christoph Egger
2008-07-30  9:49 ` Keir Fraser
2008-07-30 11:01   ` Christoph Egger
2009-02-18 22:42 Build failure jonr
2009-02-18 23:47 ` Jeremy Fitzhardinge
2009-02-19  0:50   ` jonr
2010-08-05  5:32 [linux-next] build failure divya
2010-08-05 16:48 ` John Fastabend
2011-01-24 21:36 Build failure Gary Thomas
2011-01-24 21:52 ` Tom Zanussi
2011-01-24 23:05   ` Gary Thomas
2011-01-25  0:00     ` Tian, Kevin
2011-01-25 22:51       ` Richard Purdie
     [not found] <BANLkTikBm0gmNd8oQ6CN+cAEbYhWEGvWPA@mail.gmail.com>
2011-04-30 14:31 ` Build Failure Colin Minihan
2011-04-30 16:10   ` Andy Walls
2011-05-01  1:28     ` Mauro Carvalho Chehab
2011-05-01 11:50   ` Vincent McIntyre
2012-11-14  9:15 Build failure Andreas Müller
2012-11-14  9:30 ` Andreas Müller

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=20070608102457.GA3154@uio.no \
    --to=sgunderson@bigfoot.com \
    --cc=nfs@lists.sourceforge.net \
    /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.
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.