linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: piotr@hosowicz.com
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org
Subject: Re: What's up with wireless drivers?
Date: Fri, 21 May 2010 23:31:28 +0200	[thread overview]
Message-ID: <4BF6FBB0.6060407@example.com> (raw)
In-Reply-To: <4BF6F959.5040401@example.com>

On 21.05.2010 23:21, Piotr Hosowicz wrote:
> On 21.05.2010 23:07, John W. Linville wrote:
>> On Fri, May 21, 2010 at 10:53:56PM +0200, Piotr Hosowicz wrote:
>>> Hello,
>>>
>>> I try to build kernel from git source. Now n-th build try is
>>> performing, each time it failed on wireless drivers - Atheros,
>>> Marvel etc. Did I miss something?
>>>
>>> Regards,
>>>
>>> Piotr Hosowicz
>>
>> Perhaps you should post your actual output from the build failure?
>
> I dont have it right now, I disabled wireless at all and started build.
> The output to the console was make-kpkg ordinary message - saying that
> sub build finished with error code 2 AFAIR, it stopped each time on
> wireless drivers.

Zonk! It seems that the problem is not only with wireless, now it broke 
here:

(snip)
   CC [M]  drivers/net/usb/int51x1.o
   CC [M]  drivers/net/usb/cdc-phonet.o
   CC [M]  drivers/net/wan/lmc/lmc_media.o
   CC [M]  drivers/net/wan/lmc/lmc_main.o
   CC [M]  drivers/net/wan/wanxl.o
   CC [M]  drivers/net/usb/ipheth.o
   LD [M]  drivers/net/wan/cyclomx.o
   CC [M]  drivers/net/usb/sierra_net.o
   CC [M]  drivers/net/wan/lmc/lmc_proto.o
   LD [M]  drivers/net/wan/lmc/lmc.o
make[1]: Opuszczenie katalogu `/usr/src/linus/linux-2.6-20100521-2044'
make: *** [debian/stamp/build/kernel] Błąd 2

Opuszczenie katalogu `/usr/src/linus/linux-2.6-20100521-2044' is 
"leaving directory", Błąd is error.

I give up for now, I must go to sleep.

Regards and good night.

Piotr Hosowicz


-- 
TV: "W tej chwili, że się tak wyrażę, zaliczonych mamy 17 zawodniczek."
NP: Rage Against The Machine - Know Your Enemy
NB: 2.6.34-20100521-1728

  reply	other threads:[~2010-05-21 21:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 20:53 What's up with wireless drivers? Piotr Hosowicz
2010-05-21 21:07 ` John W. Linville
2010-05-21 21:21   ` Piotr Hosowicz
2010-05-21 21:31     ` Piotr Hosowicz [this message]
2010-05-21 22:12       ` Randy Dunlap
2010-05-21 22:20         ` Piotr Hosowicz
2010-05-22  8:40           ` Piotr Hosowicz
2010-05-22 12:43             ` Piotr Hosowicz
2010-05-22 13:13               ` Piotr Hosowicz
2010-05-22 13:35                 ` Justin P. Mattock
2010-05-22 13:40                   ` Piotr Hosowicz
2010-05-22 13:44                     ` Justin P. Mattock
2010-05-22 14:04                       ` Piotr Hosowicz
2010-05-22 14:17                         ` Justin P. Mattock
2010-05-22 14:21                           ` Piotr Hosowicz
2010-05-23 13:54                           ` Piotr Hosowicz
2010-05-23 17:50                             ` Jiri Slaby
2010-05-23 18:28                               ` Piotr Hosowicz
2010-05-23 21:53                                 ` Randy Dunlap
2010-05-24  2:54                                   ` Piotr Hosowicz
2010-05-23 17:53                             ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BF6FBB0.6060407@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).