From: Greg Schafer <gschafer@zip.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What's in kbuild.git for 2.6.19
Date: Sat, 19 Aug 2006 08:12:56 +1000 [thread overview]
Message-ID: <20060818221256.GA23549@tigers.local> (raw)
In-Reply-To: <20060818171335.GA7595@mars.ravnborg.org>
On Fri, Aug 18, 2006 at 07:13:35PM +0200, Sam Ravnborg wrote:
> On Fri, Aug 18, 2006 at 06:26:07PM +1000, Greg Schafer wrote:
> > HOSTCC scripts/unifdef
> > /tmp/ccwcmPxS.o: In function `keywordedit':
> > unifdef.c:(.text+0x25c): undefined reference to `strlcpy'
> > collect2: ld returned 1 exit status
> > make[1]: *** [scripts/unifdef] Error 1
> > make: *** [headers_install] Error 2
>
> When I grep in the unifdef sources I get only one reference to strlcpy.
> That's a prototype that was missed when I replaced the use of strlcpy
> with a dedicated implementation.
Arghhh, I was cherry-picking patches and missed "replace use of strlcpy with
a dedicated implmentation in unifdef". Sorry for the noise..
Regards
Greg
prev parent reply other threads:[~2006-08-18 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 19:45 What's in kbuild.git for 2.6.19 Sam Ravnborg
2006-08-13 20:54 ` Randy.Dunlap
2006-08-13 20:57 ` Randy.Dunlap
2006-08-13 21:09 ` Sam Ravnborg
2006-08-13 22:00 ` Randy.Dunlap
2006-08-14 3:38 ` [PATCH] kbuild: more doc. cleanups Randy.Dunlap
2006-08-14 7:02 ` What's in kbuild.git for 2.6.19 Keith Owens
2006-08-14 19:02 ` Siddha, Suresh B
2006-08-15 3:53 ` Keith Owens
2006-08-15 6:25 ` Keith Owens
2006-08-15 15:16 ` Sam Ravnborg
2006-08-18 8:26 ` Greg Schafer
2006-08-18 17:13 ` Sam Ravnborg
2006-08-18 22:12 ` Greg Schafer [this message]
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=20060818221256.GA23549@tigers.local \
--to=gschafer@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.