All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: Problem compiling diffutils on poky-tiny in danny
Date: Wed, 14 Nov 2012 10:07:52 +0000	[thread overview]
Message-ID: <50A36D78.8090208@r-finger.com> (raw)
In-Reply-To: <50A2EFC0.3090908@am.sony.com>

Hi Tim,

On 14/11/12 01:11, Tim Bird wrote:
> ./wctype.h:448:1: error: static declaration of 'iswalnum' follows non-static declaration
> ./wctype.h:460:1: error: static declaration of 'iswalpha' follows non-static declaration
> ...
> Has anyone seen this type of error before, or can provide some
> hints of what to check or adjust to fix this?

The diffutils package provides a replacement for wctypes.h, which
includes the system wctypes.h and then adds some stuff of it's own -- I
think you are hitting the '#if !GNULIB_defined_wctype_functions' in the
replacement file, which expects to be providing iswalnum, etc., and
prototypes them as 'static inline'; the system wctypes.h protypes are
not static.

Not sure why it should be taking that path, could be because these
functions are not provided by libc for poky-tiny (in which case the libc
headers need patching), or could be the detection in diffutils is
broken. As a quick hack, try removing the offending prototypes from the
sysroot wctypes.h.

Tomas

-- 
http://sleepfive.com


  reply	other threads:[~2012-11-14 10:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  1:11 Problem compiling diffutils on poky-tiny in danny Tim Bird
2012-11-14 10:07 ` Tomas Frydrych [this message]
2012-11-14 16:48 ` Darren Hart
2012-11-14 18:43   ` Tim Bird
2012-11-14 18:50     ` Darren Hart
2012-11-14 18:57       ` Tim Bird
2012-11-14 19:05         ` Darren Hart
2012-11-14 21:47           ` Tim Bird
2012-11-14 21:58             ` Tim Bird
2012-11-14 22:30             ` Darren Hart

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=50A36D78.8090208@r-finger.com \
    --to=tf+lists.yocto@r-finger.com \
    --cc=yocto@yoctoproject.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.