From: Adrian Bunk <bunk@fs.tum.de>
To: John Cherry <cherry@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.73 compile results
Date: Tue, 24 Jun 2003 20:23:07 +0200 [thread overview]
Message-ID: <20030624182307.GA3710@fs.tum.de> (raw)
In-Reply-To: <1056478596.9839.118.camel@cherrypit.pdx.osdl.net>
On Tue, Jun 24, 2003 at 11:16:37AM -0700, John Cherry wrote:
> Unfortunately, the build continues even when it runs into compile or
> link errors. So if a binary impacts multiple components in the build,
> it results in multiple errors.
>
> The root of the nine errors is...
>
> fs/partitions/acorn.c: In function `adfspart_check_EESOX':
> fs/partitions/acorn.c:541: `first_sector' undeclared (first use in this
> function)
> fs/partitions/acorn.c:541: (Each undeclared identifier is reported only
> once
> fs/partitions/acorn.c:541: for each function it appears in.)
> fs/partitions/acorn.c:550: `hd' undeclared (first use in this function)
> fs/partitions/acorn.c:551: warning: implicit declaration of function
> `add_gd_partition'
> fs/partitions/acorn.c:551: `minor' undeclared (first use in this
> function)
> make[2]: [fs/partitions/acorn.o] Error 1 (ignored)
>
> Sorry for the confusion....but at least it got your attention! :)
I was surprised about nine new errors just to find it's one error I
already reported yesterday...
Could you change your scripts to avoid that such errors are counted that
often?
> John
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-06-24 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 17:26 John Cherry
2003-06-24 17:39 ` Adrian Bunk
2003-06-24 18:16 ` John Cherry
2003-06-24 18:23 ` Adrian Bunk [this message]
2003-06-24 18:31 ` Sam Ravnborg
2003-06-24 23:56 ` John Cherry
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=20030624182307.GA3710@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=cherry@osdl.org \
--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
all inboxes | Powered by JetHome®