From: Sam Ravnborg <sam@ravnborg.org>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: unable to open limits.h
Date: Tue, 25 Nov 2008 13:27:32 +0100 [thread overview]
Message-ID: <20081125122732.GA2035@uranus.ravnborg.org> (raw)
In-Reply-To: <f19298770811250418p154bad86qf926c464d16aef02@mail.gmail.com>
On Tue, Nov 25, 2008 at 03:18:58PM +0300, Alexey Zaytsev wrote:
> On Tue, Nov 25, 2008 at 14:07, Christoph Hellwig <hch@infradead.org> wrote:
> > On Ubuntu 8.10 (glibc 2.8.90) I get the following warnings when
> > compiling any program using limits.h:
> >
> > /usr/include/limits.h:125:17: error: unable to open 'limits.h'
>
> This is probably fixed by
> http://git.zaytsev.su/git?p=sparse.git;a=commitdiff;h=6f089b22a222dd086d14c985c5a67f8b3afd2177
Is this the right fix?
We should not rely on that sparse is built with the same gcc as currently installed.
The fix should be that we automagically uses the right path which
is available on the system.
>
> Josh, please pull the gsoc2008-up branch from git://zaytsev.su/git/sparse.git
For a pull request itis prefarable that you always include:
- diffstat
- shortlog
- short intor what is contained
I assume patches has been on sparse ml.
Sam
next prev parent reply other threads:[~2008-11-25 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 11:07 unable to open limits.h Christoph Hellwig
2008-11-25 12:18 ` Alexey Zaytsev
2008-11-25 12:27 ` Sam Ravnborg [this message]
2008-11-25 13:03 ` Alexey Zaytsev
2008-11-25 12:36 ` Christoph Hellwig
2008-11-25 12:37 ` Christoph Hellwig
2008-11-25 13:04 ` Alexey Zaytsev
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=20081125122732.GA2035@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=alexey.zaytsev@gmail.com \
--cc=hch@infradead.org \
--cc=josh@kernel.org \
--cc=linux-sparse@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 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 NNTP newsgroup(s).