All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Larson <kergoth@handhelds.org>
To: linux-hotplug@vger.kernel.org
Subject: Build failure - missing linux/limits.h include?
Date: Mon, 24 Nov 2003 23:12:06 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106971565807462@msgid-missing> (raw)

Greetings,

udev fails to compile here unless I'm doing a KLIBC build.  The reason
appears to be that the normal limits.h in the gcc inc dir doesn't pull
in linux/limits.h, whereas the limits.h out in the klibc include dirs
does.  I'd think it'd be best to add a #include <linux/limits.h> to
udev.h directly, since it uses PATH_MAX.

--
Chris Larson - kergoth at handhelds dot org
Embedded Linux Developer - clarson at ti dot com
OpenZaurus Project Maintainer - http://openzaurus.org/


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2003-11-24 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 23:12 Chris Larson [this message]
2003-11-25  0:18 ` Build failure - missing linux/limits.h include? Arnd Bergmann
2003-11-25  0:29 ` Chris Larson
2003-12-02  0:30 ` Greg KH

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=marc-linux-hotplug-106971565807462@msgid-missing \
    --to=kergoth@handhelds.org \
    --cc=linux-hotplug@vger.kernel.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.
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.