Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

On Tue, 2013-11-05 at 11:01 +0400, Gleb Smirnoff wrote:
> On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote:
> I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq
> I> > > > make[2]: exec(aicasm) failed (No such file or directory)
> I> > > > *** Error code 1
> I> > > >
> I> > > > Stop.
> I> > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
> I> > > > *** Error code 1
> I> > > >
> I> > > > Stop.
> I> > > > make[1]: stopped in /usr/src
> I> > >
> I> > > Did you update your source and then "make buildkernel" without
> I> > > buildworld?  If so, a "make kernel-toolchain" should create the aicasm
> I> > > tool and get you back on track.
> I> > >
> I> > 
> I> > really odd as i built a kernel this morning no problem, then updated the
> I> > tree and went to build another kernel and got that.
> I> > working through it, thanks for the input..........
> I> > 
> I> 
> I> You were just unlucky that your updates bracketed my checkin that
> I> changed the build process for the aicasm tool so that it gets built as
> I> part of the toolchain rather than as part of the kernel now.
> 
> Before this change, the toolchain was not required for kernel build if you
> aren't cross building. And now it is. This breaks the kernel build procedure
> documented in handbook for years, and brings a lot of discomfort to
> developers.
> 
> Now to test a trivial change to kernel I need first to compile clang.
> 

I didn't realize the change would have that effect.  Building aicasm
using the kernel build machinery just isn't an option anymore, it builds
in the wrong environment with the wrong header files and sometimes the
wrong toolchain when cross-building.  But there should be a solution
that doesn't require building clang, I'll see what can be done.

-- Ian