[yocto] gnutls_2.12.20: Incorrect location for header file

2012-08-11 Thread Elvis Dowson
Hi, While trying to build gnutls_2.12.20.bb recipe, with gcc-4.5, using the current poky master, I get the following error: | In file included from gnutlsxx.cpp:5:0: | ./includes/gnutls/gnutlsxx.h:4:21: fatal error: exception: No such file or directory The header file is located under

[yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Robert P. J. Day
[aside: i just tried to post to oe-core list but it bounced, and since this involves the yocto QS guide, i figured i'd use the yocto list as plan B.] kind of a followup from my earlier (oe-core) post but i'm a bit puzzled as to the *necessity* of a recipe including the line: BBCLASSEXTEND

Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor

2012-08-11 Thread Elvis Dowson
Hi Khem, I just noticed that libquadmath was disabled in the gcc-4.7.inc recipe. EXTRA_OECONF_INITIAL = --disable-libmudflap \ --disable-libgomp \ --disable-libssp \ --disable-libquadmath \

Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor

2012-08-11 Thread Khem Raj
On Sat, Aug 11, 2012 at 10:23 AM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, I just noticed that libquadmath was disabled in the gcc-4.7.inc recipe. EXTRA_OECONF_INITIAL = --disable-libmudflap \ --disable-libgomp \

Re: [yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Chris Larson
On Sat, Aug 11, 2012 at 10:03 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: however, the chrpath command is not listed in bitbake as part of ASSUME_PROVIDED, and its recipe includes the line BBCLASSEXTEND = native that's what's confusing -- if the QS guide demands that the user

Re: [yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Robert P. J. Day
On Sat, 11 Aug 2012, Chris Larson wrote: On Sat, Aug 11, 2012 at 10:03 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: however, the chrpath command is not listed in bitbake as part of ASSUME_PROVIDED, and its recipe includes the line BBCLASSEXTEND = native that's what's

Re: [yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Chris Larson
On Sat, Aug 11, 2012 at 11:32 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: On Sat, 11 Aug 2012, Chris Larson wrote: On Sat, Aug 11, 2012 at 10:03 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: however, the chrpath command is not listed in bitbake as part of ASSUME_PROVIDED, and

Re: [yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Robert P. J. Day
On Sat, 11 Aug 2012, Chris Larson wrote: On Sat, Aug 11, 2012 at 11:32 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: p.s. as a more obvious example, consider git. it's now ASSUME_PROVIDED, and listed in the quick start guide as required on the dev host, but it also still supports a

Re: [yocto] under what circumstances is BBCLASSEXTEND = native required in a recipe?

2012-08-11 Thread Robert P. J. Day
On Sat, 11 Aug 2012, Chris Larson wrote: On Sat, Aug 11, 2012 at 12:30 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: p.s. i'm still wondering if there's a convenient way to identify utilities on the dev host that are candidates for ASSUME_PROVIDED. surely a relatively recent version

Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor

2012-08-11 Thread Elvis Dowson
Hi Khem, I added support for gcc-4.5.1 inside meta-openembedded/toolchain-layer, and got it building against the latest yocto/master branch. However, switching to gcc-4.5.1 did not fix the issue. Elvis Dowson ___ yocto mailing list

Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor

2012-08-11 Thread Khem Raj
On Sat, Aug 11, 2012 at 8:34 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, I added support for gcc-4.5.1 inside meta-openembedded/toolchain-layer, and got it building against the latest yocto/master branch. However, switching to gcc-4.5.1 did not fix the issue.