I'm hoping someone a bit more familiar with buildroot and/or standard Linux Environment variables than myself can answer a question.
I'm running a fairly standard buildroot-generated rootfs. I haven't altered the core in any way, just plonked some more apps on top.
If I compile something outside the buildroot tree but using the buildroot-built toolchain, running the app always starts with a list of unresolved symbols. EG I just built php using the buildroot toolchain, now:
-sh-3.2# php --version php: can't resolve symbol 'mblen' php: can't resolve symbol '__avr32_s32_to_f32' PHP 5.1.6 (cgi-fcgi) (built: Feb 18 2008 12:09:29) Copyright (c) 1997-2006 The PHP Group Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
To access the buildroot toolchain I just have the staging_dir/bin at the head of my PATH. So; I'm using the buildroot toolchain, buildroot libraries on target, what more do I have to do to get them to actually match up nice?
As an aside, compiling PHP with same config as above, just using the current Atmel-supplied openSUSE toolchain results in the less satisfactory output
-sh-3.2# php --version php: can't resolve symbol 'mblen' php: can't resolve symbol '__avr32_s32_to_f32' Segmentation Fault
So it would seem that the openSUSE toolchain is fairly Ronnied at the moment.