On Mon, May 30, 2011 at 06:15:51PM -0000, D wrote:
> I'm not sure what happened here exactly. But the missing asm dir breaks
> a lot of builds for me, e.g. ufraw for my own system as well. And my
> thought was also that I need to get just build-essential....
You do only need build-essential. If you are using the standard Ubuntu
gcc, it will find headers in this subdirectory without any problems. The
only problems arise when you use either
- a non-Ubuntu compiler which doesn't know about multiarch paths
- a build system that inspects the filesystem directly, bypassing the
compiler's built-in include path.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Mon, May 30, 2011 at 06:15:51PM -0000, D wrote:
> I'm not sure what happened here exactly. But the missing asm dir breaks
> a lot of builds for me, e.g. ufraw for my own system as well. And my
> thought was also that I need to get just build-essential....
You do only need build-essential. If you are using the standard Ubuntu
gcc, it will find headers in this subdirectory without any problems. The
only problems arise when you use either
- a non-Ubuntu compiler which doesn't know about multiarch paths
- a build system that inspects the filesystem directly, bypassing the
compiler's built-in include path.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>