On Tue, Nov 05, 2013 at 01:40:17PM -0700, Ian Lepore wrote: I> On Tue, 2013-11-05 at 19:12 +0400, Gleb Smirnoff wrote: I> > On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote: I> > I> > I> You were just unlucky that your updates bracketed my checkin that I> > I> > I> changed the build process for the aicasm tool so that it gets built as I> > I> > I> part of the toolchain rather than as part of the kernel now. I> > I> > I> > I> > Before this change, the toolchain was not required for kernel build if you I> > I> > aren't cross building. And now it is. This breaks the kernel build procedure I> > I> > documented in handbook for years, and brings a lot of discomfort to I> > I> > developers. I> > I> > I> > I> > Now to test a trivial change to kernel I need first to compile clang. I> > I> > I> > I> I> > I> I didn't realize the change would have that effect. Building aicasm I> > I> using the kernel build machinery just isn't an option anymore, it builds I> > I> in the wrong environment with the wrong header files and sometimes the I> > I> wrong toolchain when cross-building. But there should be a solution I> > I> that doesn't require building clang, I'll see what can be done. I> > I> > Thanks, Ian. While you are seekign solution we can sustain with depending I> > on toolchain build. I> > I> I> Okay, I think I've got a potential solution, please try the attached I> patch. Now the "make buildkernel" when the objdir is empty should build I> just the aicasm tool. (In retrospect, WTF was I thinking adding it to I> the cross-build tools? I guess cross-building is just too central to my I> world these days.) I> I> Maybe for testing you should rename your existing objdir rather than I> cleaning it out, just in case this doesn't work you can rename it back I> instead of building clang all over again. :) That worked for me. Thanks! -- Totus tuus, Glebius.Received on Tue Nov 05 2013 - 19:57:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:44 UTC