linux-kernel - Re: What's up with wireless drivers?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 May 2010 14:53:19 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	piotr@...owicz.com
Cc:	Jiri Slaby <jirislaby@...il.com>,
	"Justin P. Mattock" <justinmattock@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: What's up with wireless drivers?

On Sun, 23 May 2010 20:28:53 +0200 Piotr Hosowicz wrote:

> On 23.05.2010 19:50, Jiri Slaby wrote:
> > On 05/23/2010 03:54 PM, Piotr Hosowicz wrote:
> >> And they had built flawlessly. But main build with make-kpkg
> >> kernel_image nevertheless still fails. I don;t know what to do. I don't
> >> want to do those strace's, because it will take awfully long.
> >
> > Why don't you just look at the actual error which is likely somewhere
> > above because of parallel build? And when you are posting outputs, first
> > switch your locale to en so that we can parse the output.
> 
> I tried again and the error is about CEPH. I attach the typescript. I am 
> totaly confused, now build breakse in yet another place than before.
> 
> Regards,
> 
> Piotr Hosowicz
> 
> PS: I ordered make modules without calling make first, I on't know if 
> it's ok.


  CC [M]  fs/ceph/msgpool.o
fs/ceph/msgpool.c: In function ___ceph_msgpool_put___:
fs/ceph/msgpool.c:173: error: implicit declaration of function ___kref_set___
make[2]: *** [fs/ceph/msgpool.o] B____d 1
make[1]: *** [fs/ceph] B____d 2
make: *** [fs] B____d 2


Known problem, but I haven't seen a fix for it yet.

And note how it says Error 1, not just Error 2.
Error 1 is the primary error.  Just showing us Error 2 is mostly useless.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/