tcpdump: bitbake throws autoconf errors, error message confusing

tcpdump: bitbake throws autoconf errors, error message confusing

[Jack Mitchell]

So tcpdump is failing to build in my latest uprev to all things HEAD.
The error message is a touch cryptic:

ERROR: This autoconf log indicates errors, it looked at host include
and/or library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
ERROR: Function failed: do_qa_configure

log: http://ix.io/dg9

Looking at the log I can't see where that specific path is used... can
anyone shed any light?

Cheers,

-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 

Re: tcpdump: bitbake throws autoconf errors, error message confusing

[Robert Yang]

The error message comes from meta/classes/insane.bbclass:

grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation'

The log you showed didn't contain the words, so that it should not error,
maybe you have to debug in meta/classes/insane.bbclass.

Btw., the meta-oe's tcpdump is 4.3.0, yours is 4.5.1, maybe there are
other differences, for example you have used another insane.bbclass ?
(Just a guess)

// Robert

On 07/04/2014 05:42 PM, Jack Mitchell wrote:
> So tcpdump is failing to build in my latest uprev to all things HEAD.
> The error message is a touch cryptic:
>
> ERROR: This autoconf log indicates errors, it looked at host include
> and/or library paths while determining system capabilities.
> Rerun configure task after fixing this. The path was
> '/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
> ERROR: Function failed: do_qa_configure
>
> log: http://ix.io/dg9
>
> Looking at the log I can't see where that specific path is used... can
> anyone shed any light?
>
> Cheers,
>

Re: tcpdump: bitbake throws autoconf errors, error message confusing

[Jack Mitchell]

Hi Robert,

After further investigation that is also what I found, and why it's so
confusing. The different tcpdump is because I uprevved to the latest
version locally to see if it fixed the issue ;)

I'll see if I can figure out why the class if flagging it as bad when it
shouldn't.

On 04/07/14 11:14, Robert Yang wrote:
> 
> The error message comes from meta/classes/insane.bbclass:
> 
> grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation'
> 
> The log you showed didn't contain the words, so that it should not error,
> maybe you have to debug in meta/classes/insane.bbclass.
> 
> Btw., the meta-oe's tcpdump is 4.3.0, yours is 4.5.1, maybe there are
> other differences, for example you have used another insane.bbclass ?
> (Just a guess)
> 
> // Robert
> 
> On 07/04/2014 05:42 PM, Jack Mitchell wrote:
>> So tcpdump is failing to build in my latest uprev to all things HEAD.
>> The error message is a touch cryptic:
>>
>> ERROR: This autoconf log indicates errors, it looked at host include
>> and/or library paths while determining system capabilities.
>> Rerun configure task after fixing this. The path was
>> '/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
>>
>> ERROR: Function failed: do_qa_configure
>>
>> log: http://ix.io/dg9
>>
>> Looking at the log I can't see where that specific path is used... can
>> anyone shed any light?
>>
>> Cheers,
>>


-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 

Re: tcpdump: bitbake throws autoconf errors, error message confusing

[Andrea Adami]

On Fri, Jul 4, 2014 at 12:31 PM, Jack Mitchell <ml@communistcode.co.uk> wrote:
> Hi Robert,
>
> After further investigation that is also what I found, and why it's so
> confusing. The different tcpdump is because I uprevved to the latest
> version locally to see if it fixed the issue ;)
>
> I'll see if I can figure out why the class if flagging it as bad when it
> shouldn't.
>
> On 04/07/14 11:14, Robert Yang wrote:
>>
>> The error message comes from meta/classes/insane.bbclass:
>>
>> grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation'
>>
>> The log you showed didn't contain the words, so that it should not error,
>> maybe you have to debug in meta/classes/insane.bbclass.
>>
>> Btw., the meta-oe's tcpdump is 4.3.0, yours is 4.5.1, maybe there are
>> other differences, for example you have used another insane.bbclass ?
>> (Just a guess)
>>
>> // Robert
>>
>> On 07/04/2014 05:42 PM, Jack Mitchell wrote:
>>> So tcpdump is failing to build in my latest uprev to all things HEAD.
>>> The error message is a touch cryptic:
>>>
>>> ERROR: This autoconf log indicates errors, it looked at host include
>>> and/or library paths while determining system capabilities.
>>> Rerun configure task after fixing this. The path was
>>> '/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
>>>
>>> ERROR: Function failed: do_qa_configure
>>>
>>> log: http://ix.io/dg9
>>>
>>> Looking at the log I can't see where that specific path is used... can
>>> anyone shed any light?
>>>

Just gave a quick glimpse. Maybe it complains about this ?

  --exec_prefix=/usr

autoreconf: configure.in: not using Automake
autoreconf: running: gnu-configize
autoreconf: Leaving directory `.'
NOTE: Running /home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/tcpdump-4.5.1/configure
 --build=x86_64-linux  --host=i586-oe-linux  --target=i586-oe-linux
--prefix=/usr  --exec_prefix=/usr  --bindir=/usr/bin
--sbindir=/usr/sbin  --libexecdir=/usr/lib/tcpdump
--datadir=/usr/share  --sysconfdir=/etc  --sharedstatedir=/com
--localstatedir=/var  --libdir=/usr/lib  --includedir=/usr/include
--oldincludedir=/usr/include  --infodir=/usr/share/info
--mandir=/usr/share/man  --disable-silent-rules
--disable-dependency-tracking
--with-libtool-sysroot=/home/jack/Work/oe-core.git/test-build/tmp-eglibc/sysroots/cbnlcomexpress
--without-crypto         --enable-ipv6
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-dependency-tracking, --with-libtool-sysroot

Cheers

Andrea


>>> Cheers,
>>>
>
>
> --
>   Jack Mitchell (jack@embed.me.uk)
>   Embedded Systems Engineer
>   Cambridgeshire, UK
>   http://www.embed.me.uk
> --
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: tcpdump: bitbake throws autoconf errors, error message confusing

[Jack Mitchell]

On 04/07/14 11:31, Jack Mitchell wrote:
> Hi Robert,
> 
> After further investigation that is also what I found, and why it's so
> confusing. The different tcpdump is because I uprevved to the latest
> version locally to see if it fixed the issue ;)
> 
> I'll see if I can figure out why the class if flagging it as bad when it
> shouldn't.
> 
> On 04/07/14 11:14, Robert Yang wrote:
>>
>> The error message comes from meta/classes/insane.bbclass:
>>
>> grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation'
>>
>> The log you showed didn't contain the words, so that it should not error,
>> maybe you have to debug in meta/classes/insane.bbclass.
>>
>> Btw., the meta-oe's tcpdump is 4.3.0, yours is 4.5.1, maybe there are
>> other differences, for example you have used another insane.bbclass ?
>> (Just a guess)
>>
>> // Robert
>>
>> On 07/04/2014 05:42 PM, Jack Mitchell wrote:
>>> So tcpdump is failing to build in my latest uprev to all things HEAD.
>>> The error message is a touch cryptic:
>>>
>>> ERROR: This autoconf log indicates errors, it looked at host include
>>> and/or library paths while determining system capabilities.
>>> Rerun configure task after fixing this. The path was
>>> '/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
>>>
>>> ERROR: Function failed: do_qa_configure
>>>
>>> log: http://ix.io/dg9
>>>
>>> Looking at the log I can't see where that specific path is used... can
>>> anyone shed any light?
>>>
>>> Cheers,
>>>
> 
> 

Ok, so I've found the issue. tcpdump finds some pcap binaries it needs
in the host sysroot, which then provides links to host include paths and
as such, the failure.

The question, how do I fix it? Will I need to inherit native or
something like that, so a local version is built which then points to
the correct sysroot that the cross version can then make use of? I've
never really had to deal with anything like this before...

config.log: http://ix.io/dgf

Regards,

-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
--