From: Dave Jones <davej@redhat.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Sun, 26 Feb 2006 14:31:21 -0500 [thread overview]
Message-ID: <20060226193121.GG7851@redhat.com> (raw)
In-Reply-To: <9a8748490602260835l2430e841p2bf02c1f99e55b91@mail.gmail.com>
On Sun, Feb 26, 2006 at 05:35:49PM +0100, Jesper Juhl wrote:
> And for those who want to see a list of the unique errors, here they are :
>
> make: *** [.tmp_vmlinux1] Error 1
> make: *** [arch/i386/kernel] Error 2
> make: *** [drivers] Error 2
> make: *** [sound] Error 2
> make: *** [vmlinux] Error 1
> make[1]: *** [arch/i386/kernel/irq.o] Error 1
> make[1]: *** [drivers/acpi] Error 2
> make[1]: *** [drivers/atm] Error 2
> make[1]: *** [drivers/isdn] Error 2
> make[1]: *** [drivers/media] Error 2
> make[1]: *** [drivers/mtd] Error 2
> make[1]: *** [drivers/scsi] Error 2
> make[1]: *** [drivers/usb] Error 2
> make[1]: *** [sound/isa] Error 2
> make[1]: *** [sound/oss] Error 2
> make[2]: *** [drivers/acpi/numa.o] Error 1
> make[2]: *** [drivers/acpi/numa.o] Error 1 LD [M] fs/ext3/ext3.o
> make[2]: *** [drivers/acpi/osl.o] Error 1
> make[2]: *** [drivers/atm/fore200e_pca_fw.c] Error 254
> make[2]: *** [drivers/isdn/hysdn] Error 2
> make[2]: *** [drivers/media/dvb] Error 2
> make[2]: *** [drivers/mtd/maps] Error 2
> make[2]: *** [drivers/scsi/aic7xxx] Error 2
> make[2]: *** [drivers/usb/net] Error 2
> make[2]: *** [sound/isa/opti9xx] Error 2
> make[3]: *** [drivers/isdn/hysdn/hysdn_net.o] Error 1
> make[3]: *** [drivers/media/dvb/ttpci] Error 2
> make[3]: *** [drivers/mtd/maps/nettel.o] Error 1
> make[3]: *** [drivers/scsi/aic7xxx/aicasm/aicasm] Error 2
> make[3]: *** [drivers/usb/net/cdc_subset.o] Error 1
> make[3]: *** [sound/isa/opti9xx/opti92x-ad1848.o] Error 1
> make[3]: *** [sound/isa/opti9xx/opti93x.o] Error 1
> make[4]: *** [aicasm] Error 1
> make[4]: *** [drivers/media/dvb/ttpci/av7110_firm.h] Error 255
You snipped out the interesting parts, which is 1-2 lines before this
(Grepping for Error: should do it)
Dave
next prev parent reply other threads:[~2006-02-26 19:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 16:21 Building 100 kernels; we suck at dependencies and drown in warnings Jesper Juhl
2006-02-26 16:31 ` Jesper Juhl
2006-02-26 16:35 ` Jesper Juhl
2006-02-26 19:31 ` Dave Jones [this message]
2006-02-26 19:43 ` Jesper Juhl
2006-02-26 20:11 ` Jesper Juhl
2006-02-26 23:45 ` Nigel Cunningham
2006-02-27 2:02 ` Pavel Machek
2006-02-26 19:30 ` Dave Jones
2006-02-26 17:00 ` Adrian Bunk
2006-02-26 17:29 ` Jesper Juhl
2006-02-26 17:41 ` Adrian Bunk
2006-02-26 18:08 ` Jesper Juhl
2006-02-26 17:38 ` Jesper Juhl
2006-02-26 18:21 ` Diego Calleja
2006-02-26 18:45 ` Jesper Juhl
2006-02-26 19:03 ` Diego Calleja
2006-02-26 20:42 ` Lee Revell
2006-02-26 20:44 ` Jesper Juhl
2006-02-26 21:46 ` Nix
2006-02-26 21:49 ` Jesper Juhl
2006-02-26 21:53 ` Lee Revell
2006-02-26 21:56 ` Jesper Juhl
2006-02-26 22:08 ` Lee Revell
2006-02-26 22:12 ` Jesper Juhl
2006-02-27 17:25 ` Stephen Hemminger
2006-02-26 22:14 ` Al Viro
2006-02-26 22:32 ` Nix
2006-02-26 22:50 ` Lee Revell
2006-02-26 21:14 ` Grant Coady
2006-02-27 12:56 ` David Greaves
2006-02-28 10:30 ` Roman Zippel
2006-02-26 22:43 ` Sam Ravnborg
2006-03-02 20:25 ` Jesper Juhl
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=20060226193121.GG7851@redhat.com \
--to=davej@redhat.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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