All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Schafer <gschafer@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: What's in kbuild.git for 2.6.19
Date: Fri, 18 Aug 2006 18:26:07 +1000	[thread overview]
Message-ID: <pan.2006.08.18.08.26.03.994311@zip.com.au> (raw)
In-Reply-To: 20060813194503.GA21736@mars.ravnborg.org

On Sun, 13 Aug 2006 21:45:03 +0200, Sam Ravnborg wrote:

> Just a quick intro to what is pending in kbuild.git/lxdialog.git for 2.6.19.
> And a short status too.
> 
> Highlights:
> 	o unifdef is now included in the kernel source (used by
> 	  headers_* targets).

Hi Sam,

This apparently doesn't build:

  CHK     include/linux/version.h
  UPD     include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  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


AFAICT, strlcpy is a BSD'ism and isn't generally available to userland on
Linux (but of course the kernel has its own strlcpy implementation).
Debian solve this by including a separate strlcpy.c with the unifdef
source. See:

http://ftp.debian.org/debian/pool/main/u/unifdef/unifdef_1.0+20030701.orig.tar.gz

Regards
Greg


  parent reply	other threads:[~2006-08-18  8:30 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 [this message]
2006-08-18 17:13   ` Sam Ravnborg
2006-08-18 22:12     ` Greg Schafer

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=pan.2006.08.18.08.26.03.994311@zip.com.au \
    --to=gschafer@zip.com.au \
    --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 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.