public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] glibc: print PN when bbwarn
Date: Fri, 17 Jul 2015 14:58:23 +0800	[thread overview]
Message-ID: <55A8A78F.7020209@windriver.com> (raw)
In-Reply-To: <CAMKF1sqVDngrV0zZEzZcCScM+HyV+LC++VzpFtVV9ZBW0M8jSQ@mail.gmail.com>



On 07/17/2015 12:45 PM, Khem Raj wrote:
> On Mon, Jul 13, 2015 at 3:02 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
>> The current warning is:
>> WARNING: glibc: unable to generate header for spray.x
>>
>> Which is easier to debug than:
>> WARNING: unable to generate header for spray.x
>>
>> And remove the file before generate it again to fix the warning when
>> recompile:
>> file `bootparam_prot.h' already exists and may be overwritten
>> WARNING: unable to generate header for bootparam_prot.x
>> file `nlm_prot.h' already exists and may be overwritten
>> WARNING: unable to generate header for nlm_prot.x
>> [snip]
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>>   meta/recipes-core/glibc/glibc_2.21.bb |    3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-core/glibc/glibc_2.21.bb b/meta/recipes-core/glibc/glibc_2.21.bb
>> index 8197c29..30f1937 100644
>> --- a/meta/recipes-core/glibc/glibc_2.21.bb
>> +++ b/meta/recipes-core/glibc/glibc_2.21.bb
>> @@ -135,7 +135,8 @@ do_compile () {
>>                  cd ${S}/sunrpc/rpcsvc
>>                  for r in ${rpcsvc}; do
>>                          h=`echo $r|sed -e's,\.x$,.h,'`
>> -                       rpcgen -h $r -o $h || bbwarn "unable to generate header for $r"
>> +                       rm -f $h
>
> it quashes the warning but doesnt fix underlying problem. this doesnt
> seem to be right thing to do in cross builds. We use cross-rpcgen to
> generate these files so this whole rpcgen run should be removed
> instead. Please test such a patch and correct it.
>

Hi Khem,

I will be on vacation the whole next week, will do when I come back.

// Robert

>> +                       rpcgen -h $r -o $h || bbwarn "${PN}: unable to generate header for $r"
>>                  done
>>          )
>>          echo "Adjust ldd script"
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  reply	other threads:[~2015-07-17  6:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 10:02 [PATCH 0/3] meta: 3 fixes Robert Yang
2015-07-13 10:02 ` [PATCH 1/3] glibc: print PN when bbwarn Robert Yang
2015-07-17  4:45   ` Khem Raj
2015-07-17  6:58     ` Robert Yang [this message]
2015-08-17 12:33     ` Burton, Ross
2015-08-18 17:02       ` Burton, Ross
2015-08-19  1:13         ` Robert Yang
2015-07-13 10:02 ` [PATCH 2/3] dbus-ptest: set INSANE_SKIP for build-deps Robert Yang
2015-07-13 10:02 ` [PATCH 3/3] gnu-config: set noexec for do_compile Robert Yang

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=55A8A78F.7020209@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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