linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
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 16:03:24 +0300	[thread overview]
Message-ID: <f19298770811250503w3692ebf6nb3026ba551da4523@mail.gmail.com> (raw)
In-Reply-To: <20081125122732.GA2035@uranus.ravnborg.org>

On Tue, Nov 25, 2008 at 15:27, Sam Ravnborg <sam@ravnborg.org> wrote:
> 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.
>
I see no magic way to find the right path, except specifying which gcc version
sparse would have to follow. Probably cgcc could pass it to sparse, but anyway,
this would probably be an other patch. Mine does not change the way
sparse works,
only adds the new include dir, which should not harm the

>>
>> 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

The branch contains cleanups and other straight-forward changes gained as as a
side-effect of my sparse linker work this summer. Josh has already agreed on the
patches, but was too busy and pobably forgot to pull. Anyway, there is
the shortlog:

Alexey Zaytsev (9):
      Make show_symbol newline-consistent
      Looks more evident this way.
      Handle a terminal -o option properly.
      Mark handle_switch as static and don't export it from lib.h
      Handle missing argument to -D.
      Gdb macros to get a better look at some sparse data structures.
      A slightly edited irc discussion with Josh Triplett.
      Add $GCC_BASE/include-fixed to the include list.
      Warning should be enough for an unhandled transparent union

The patches seem to be too trivial to discuss. For the non-trivial
patches from the
gsoc2008-linker branch I got constructive feedback and will probably
rework the idea.

  reply	other threads:[~2008-11-25 13:03 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
2008-11-25 13:03     ` Alexey Zaytsev [this message]
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=f19298770811250503w3692ebf6nb3026ba551da4523@mail.gmail.com \
    --to=alexey.zaytsev@gmail.com \
    --cc=hch@infradead.org \
    --cc=josh@kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sam@ravnborg.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).