[yocto] help sought with migrating oe-classic recipe

[Tim Coote]

Hullo

I'm trying to put an amqp client into a yocto build. My preferred choice is rabbitmq, which requires getting Erlang into the build. I'm starting with an old recipe, which is based on openembedded classic (http://bit.ly/UpGACX, which is based on http://bit.ly/UpGFGB, with updates for newer releases.)

I've added in the oe-core migrations from here: http://bit.ly/XEI9u6

I'm running into what I believe are incomplete cross-compile problems:
[code]
bitbake -v -b ../meta-openembedded/meta-oe/recipes-extended/erlang/erlang_R15B.bb 2>&1 |less
[/code]

to just build the package. Fails when the python script checks for unsafe cross compile error messages (around line 777 of danny-8.0/meta/classes/insane.bbclass):
[code]
         statement = "grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation' %s > /dev/null" % \
                     os.path.join(root,"config.log")
         if "config.log" in files:
             if subprocess.call(statement, shell=True) == 0:
[/code]
the grep finds:

[code]
/opt/poky/mybuilds/tmp/sysroots/i686-linux/usr/libexec/armv5te-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld: warning: library search path "/lib" is unsafe for cross-compilation

[/code]


. The bad message occurs just after this in the log:
[code]
configure:11485: result: no
configure:11518: Extending the search to include /lib
configure:11520: checking for dlpi_open in -ldlpi
[/code]

and seems to me to be due to something adding /lib into the library search path. I'm not clear what's the source of this problem, nor how to narrow it down. I'd guess that somehow, /lib should be scoped out of library searches for the autoconf tools.

Any ideas and any pointers on where I can find relevant documentation?

cheers

Tim