All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Ludovic Brenta <ludovic@ludovic-brenta.org>
Cc: linux-sparse@vger.kernel.org, debian-gcc@lists.debian.org,
	multiarch-devel@lists.alioth.debian.org
Subject: Re: sparse and multiarch include paths
Date: Wed, 24 Aug 2011 20:16:02 -0700	[thread overview]
Message-ID: <20110825031602.GA1944@leaf> (raw)
In-Reply-To: <87zkiy1ld2.fsf@ludovic-brenta.org>

On Thu, Aug 25, 2011 at 12:43:37AM +0200, Ludovic Brenta wrote:
> Josh Triplett <josh@joshtriplett.org> writes:
> > When trying to use sparse on some low-level userspace code, I ran into
> > the following error:
> >
> > /usr/include/bits/socket.h:381:11: error: unable to open 'asm/socket.h'
> 
> See http://bugs.debian.org/638418
> 
> Hope this helps

Thanks!  That does seem to explain the problem; I removed and
reinstalled gcc-multilib, and now I have a /usr/include/asm symlink and
sparse seems happy.

- Josh Triplett

      reply	other threads:[~2011-08-25  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 21:42 sparse and multiarch include paths Josh Triplett
2011-08-24 21:48 ` Chris Forbes
2011-08-24 22:43 ` Ludovic Brenta
2011-08-25  3:16   ` Josh Triplett [this message]

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=20110825031602.GA1944@leaf \
    --to=josh@joshtriplett.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ludovic@ludovic-brenta.org \
    --cc=multiarch-devel@lists.alioth.debian.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.