sparse and multiarch include paths

sparse and multiarch include paths

[Josh Triplett]

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'

It looks like that file lives in
/usr/include/x86_64-linux-gnu/asm/socket.h , and gcc has
/usr/include/x86_64-linux-gnu in its default include path.  This relates
to Debian's multiarch efforts, moving such headers to paths which
include the architecture to allow simultaneous installation of the
headers for multiple architectures.  I don't know how gcc ends up with
that directory in its include path, but sparse needs to follow suit to
compile any code which includes these architecture-specific
headers.

I've CCed the Debian GCC maintainers and multiarch developers, in the
hopes of getting some additional details that might help resolve this
problem.

- Josh Triplett

Re: sparse and multiarch include paths

[Chris Forbes]

I've hit this as well. The ubuntu-packaged sparse seems to get this
right; building from git sources gives busted paths -- suspect they
have patches that need to come upstream?

-- Chris

On Thu, Aug 25, 2011 at 9:42 AM, Josh Triplett <josh@joshtriplett.org> wrote:
> 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'
>
> It looks like that file lives in
> /usr/include/x86_64-linux-gnu/asm/socket.h , and gcc has
> /usr/include/x86_64-linux-gnu in its default include path.  This relates
> to Debian's multiarch efforts, moving such headers to paths which
> include the architecture to allow simultaneous installation of the
> headers for multiple architectures.  I don't know how gcc ends up with
> that directory in its include path, but sparse needs to follow suit to
> compile any code which includes these architecture-specific
> headers.
>
> I've CCed the Debian GCC maintainers and multiarch developers, in the
> hopes of getting some additional details that might help resolve this
> problem.
>
> - Josh Triplett
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: sparse and multiarch include paths

[Ludovic Brenta]

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

-- 
Ludovic Brenta.

Re: sparse and multiarch include paths

[Josh Triplett]

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