On 17 August 2015 at 13:33, Burton, Ross ross.bur...@intel.com wrote:
There's been a related report on the yocto@ list where it was noticed
that we're executing the host rpcgen during glibc builds, so consider
this is a ping. :)
Filed #8181 so this doesn't get lost.
Ross
--
Thanks, I will work on it.
// Robert
On 08/19/2015 01:02 AM, Burton, Ross wrote:
On 17 August 2015 at 13:33, Burton, Ross ross.bur...@intel.com
mailto:ross.bur...@intel.com wrote:
There's been a related report on the yocto@ list where it was noticed that
we're executing the host
On 17 July 2015 at 05:45, Khem Raj raj.k...@gmail.com wrote:
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
On 07/17/2015 12:45 PM, Khem Raj wrote:
On Mon, Jul 13, 2015 at 3:02 AM, Robert Yang liezhi.y...@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
On Mon, Jul 13, 2015 at 3:02 AM, Robert Yang liezhi.y...@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
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
