[Buildroot] [autobuild.buildroot.net] Build results for 2014-06-25

[Thomas De Schampheleire]

Hi Max,

On Thu, Jun 26, 2014 at 10:42 PM, Max Filippov <jcmvbkbc at gmail.com> wrote:
[..]
>>
>> I think it is debatable whether output to /dev/null in gcc is legal or not.
>> My personal feeling is that this should work, and that if xtensa
>> cannot deal with it then they should buffer internally and write out
>> the file as the last step.
>
> It just doesn't seem practical to fix in ld what can be fixed (and actually
> once was fixed) in the configure script. AFAIU the configure script should
> be as conservative as possible, so e.g. autoconf-generated scripts don't
> use such trick.

>From a buildroot-practical point of view it's indeed more easy to fix dhcpcd.

>
>> Note that we are using the same /dev/null trick in the check-arm-abi code.
>
> Haven't found that, can you point me to a specific file?

See toolchain/helpers.mk, function check_arm_abi:

check_arm_abi = \
    __CROSS_CC=$(strip $1) ; \
    __CROSS_READELF=$(strip $2) ; \
    EXT_TOOLCHAIN_TARGET=`LANG=C $${__CROSS_CC} -v 2>&1 | grep ^Target
| cut -f2 -d ' '` ; \
    if ! echo $${EXT_TOOLCHAIN_TARGET} | grep -qE 'eabi(hf)?$$' ; then \
        echo "External toolchain uses the unsuported OABI" ; \
        exit 1 ; \
    fi ; \
    if ! echo 'int main(void) {}' | $${__CROSS_CC} -x c -o /dev/null -
2>/dev/null; then \
        abistr_$(BR2_ARM_EABI)='EABI'; \
        abistr_$(BR2_ARM_EABIHF)='EABIhf'; \
        echo "Incorrect ABI setting: $${abistr_y} selected, but
toolchain is incompatible"; \
        exit 1 ; \
    fi


Best regards,
Thomas