On Mon, Sep 7, 2015 at 7:01 AM, David Laight wrote:
> On Sat, Sep 05, 2015 at 09:39:43AM +0900, Masao Uebayashi wrote:
>> The reason of this is that config(1) have no idea of library at this
>> moment. Makefile.kern.inc has also a convention that all *.o files
>> have to be built under the top of
On Sat, Sep 05, 2015 at 09:39:43AM +0900, Masao Uebayashi wrote:
> The reason of this is that config(1) have no idea of library at this
> moment. Makefile.kern.inc has also a convention that all *.o files
> have to be built under the top of kernel build directory. libkern &
> libcompat have speic
The reason of this is that config(1) have no idea of library at this
moment. Makefile.kern.inc has also a convention that all *.o files
have to be built under the top of kernel build directory. libkern &
libcompat have speicalized make(1) rules, that work but look ugly.
I'd consider to extend con
