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

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

[Thomas Petazzoni]

Build statistics for 2014-06-25
===============================

        success : 88 
       failures : 19 
       timeouts : 1  
          TOTAL : 108

Classification of failures by reason
====================================

                  cppcms-1.0.4 | 2 
                directfb-1.6.3 | 2 
                    sdl-1.2.15 | 2 
                      icu-51.2 | 2 
host-gdb-6be65fb56ea6694a92... | 1 
                  dhcpcd-6.4.0 | 1 
                libiscsi-1.6.0 | 1 
                      gd-2.1.0 | 1 
          enlightenment-0.17.3 | 1 
                pinentry-0.8.3 | 1 
                 haserl-0.9.33 | 1 
                    radvd-1.13 | 1 
                   dillo-3.0.4 | 1 
     host-xproto_kbproto-1.0.6 | 1 
                  prboom-2.5.0 | 1 
                 cairo-1.12.10 | 1 

Detail of failures
===================

      bfin |                  cairo-1.12.10 | NOK | http://autobuild.buildroot.net/results/c332f1f2e15fedd30bc3d6b9bee1825bbec7d7a1/
   powerpc |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/448a37b22dd2582cafae9ed72283728352b17f28/
   powerpc |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/91cd90ce075089534c05b031aab14ded9510f053/
    xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/
     avr32 |                    dillo-3.0.4 | NOK | http://autobuild.buildroot.net/results/ca418f13d0a3642efffd013e6681e81b8ec304e7/
   powerpc |                 directfb-1.6.3 | NOK | http://autobuild.buildroot.net/results/fa64973059843cde9f951b7fedd8a3ba94013fff/
    x86_64 |                 directfb-1.6.3 | NOK | http://autobuild.buildroot.net/results/9d550f24b5a8c0c24adba16ae3a4f8e34cca6fb7/
   powerpc |           enlightenment-0.17.3 | NOK | http://autobuild.buildroot.net/results/41f079c455410a651dd4ff08ee1bcf1f364cb1fd/
      bfin |                       gd-2.1.0 | NOK | http://autobuild.buildroot.net/results/c5ce1ce98dd5418f3cfa5505dd7d48149e6651d2/
  mips64el |                  haserl-0.9.33 | NOK | http://autobuild.buildroot.net/results/f9239c618fe144cebf1b57bfc4e2d4bc8a0ae47c/
microblazeel | host-gdb-6be65fb56ea6694a92... | NOK | http://autobuild.buildroot.net/results/d8f6c99395fcfd342a618352fa46b357c13e14e6/
    x86_64 |      host-xproto_kbproto-1.0.6 | TIM | http://autobuild.buildroot.net/results/f8d8f9992852a99ad68691ea5bf2783b86fb0dee/
      bfin |                       icu-51.2 | NOK | http://autobuild.buildroot.net/results/2d18fda6645bcd690ed71c8475cc337b7564f467/
      bfin |                       icu-51.2 | NOK | http://autobuild.buildroot.net/results/cf6cfa1fb8132ef6d6e5f3a413d21993941a9ad1/
      i486 |                 libiscsi-1.6.0 | NOK | http://autobuild.buildroot.net/results/e9a3b30302583cf4ae2f3ba5c53af33797eab1a5/
    x86_64 |                 pinentry-0.8.3 | NOK | http://autobuild.buildroot.net/results/fa14d1e93a827481e69dfab450f7a8375ec8133d/
      bfin |                   prboom-2.5.0 | NOK | http://autobuild.buildroot.net/results/acb4550576517808d859c51331b618fb9200eda2/
   powerpc |                     radvd-1.13 | NOK | http://autobuild.buildroot.net/results/7be10f10ba3e21fa36e8c2e80bb885bb9b999813/
   powerpc |                     sdl-1.2.15 | NOK | http://autobuild.buildroot.net/results/180f9a9790f5fe99f68cc203ab4f54aa54dd2641/
   powerpc |                     sdl-1.2.15 | NOK | http://autobuild.buildroot.net/results/e840c16654e5448732a7dd08a2e24946256d85dd/


-- 
http://autobuild.buildroot.net

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

[Baruch Siach]

Hi Max,

On Thu, Jun 26, 2014 at 08:30:11AM +0200, Thomas Petazzoni wrote:
>     xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/

This is strange. It seems like xtensa toolchains don't like /dev/null as
output file:

$ .../output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o /dev/null test.c
.../output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.8.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: Final link failed: File truncated

Toolchains for other architectures are just fine with /dev/null. Any Idea?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

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

[Max Filippov]

Hi Baruch,

On Thu, Jun 26, 2014 at 10:35 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> On Thu, Jun 26, 2014 at 08:30:11AM +0200, Thomas Petazzoni wrote:
>>     xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/
>
> This is strange. It seems like xtensa toolchains don't like /dev/null as
> output file:
>
> $ .../output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o /dev/null test.c
> .../output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.8.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: Final link failed: File truncated
>
> Toolchains for other architectures are just fine with /dev/null. Any Idea?

Not yet, looking at it.

-- 
Thanks.
-- Max

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

[Max Filippov]

On Thu, Jun 26, 2014 at 1:27 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> Hi Baruch,
>
> On Thu, Jun 26, 2014 at 10:35 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>> On Thu, Jun 26, 2014 at 08:30:11AM +0200, Thomas Petazzoni wrote:
>>>     xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/
>>
>> This is strange. It seems like xtensa toolchains don't like /dev/null as
>> output file:
>>
>> $ .../output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o /dev/null test.c
>> .../output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.8.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: Final link failed: File truncated
>>
>> Toolchains for other architectures are just fine with /dev/null. Any Idea?

It wants to read back just written .xt.lit.plt section to rearrange it
a bit in the
following call chain:

main
  ldwrite
    bfd_elf_final_link
      elf_xtensa_finish_dynamic_sections
        elf_xtensa_combine_prop_entries

and obviously fails. This only happens when the result is dynamic object,
static linking completes successfully.
I don't see why this might be considered invalid behaviour, and rather
think that
the check in the dhcpcd configure script is wrong.

-- 
Thanks.
-- Max

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

[Thomas De Schampheleire]

Hi,

On Thu, Jun 26, 2014 at 3:45 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Thu, Jun 26, 2014 at 1:27 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>> Hi Baruch,
>>
>> On Thu, Jun 26, 2014 at 10:35 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>> On Thu, Jun 26, 2014 at 08:30:11AM +0200, Thomas Petazzoni wrote:
>>>>     xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/
>>>
>>> This is strange. It seems like xtensa toolchains don't like /dev/null as
>>> output file:
>>>
>>> $ .../output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o /dev/null test.c
>>> .../output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.8.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: Final link failed: File truncated
>>>
>>> Toolchains for other architectures are just fine with /dev/null. Any Idea?
>
> It wants to read back just written .xt.lit.plt section to rearrange it
> a bit in the
> following call chain:
>
> main
>   ldwrite
>     bfd_elf_final_link
>       elf_xtensa_finish_dynamic_sections
>         elf_xtensa_combine_prop_entries
>
> and obviously fails. This only happens when the result is dynamic object,
> static linking completes successfully.
> I don't see why this might be considered invalid behaviour, and rather
> think that
> the check in the dhcpcd configure script is wrong.

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.

Note that we are using the same /dev/null trick in the check-arm-abi code.

Best regards,
Thomas

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

[Max Filippov]

On Thu, Jun 26, 2014 at 11:11 PM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> Hi,
>
> On Thu, Jun 26, 2014 at 3:45 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>> On Thu, Jun 26, 2014 at 1:27 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>>> Hi Baruch,
>>>
>>> On Thu, Jun 26, 2014 at 10:35 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>>> On Thu, Jun 26, 2014 at 08:30:11AM +0200, Thomas Petazzoni wrote:
>>>>>     xtensa |                   dhcpcd-6.4.0 | NOK | http://autobuild.buildroot.net/results/ecbba5682e3a8065f3cf3e0a9670c2febc71949a/
>>>>
>>>> This is strange. It seems like xtensa toolchains don't like /dev/null as
>>>> output file:
>>>>
>>>> $ .../output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o /dev/null test.c
>>>> .../output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.8.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: Final link failed: File truncated
>>>>
>>>> Toolchains for other architectures are just fine with /dev/null. Any Idea?
>>
>> It wants to read back just written .xt.lit.plt section to rearrange it
>> a bit in the
>> following call chain:
>>
>> main
>>   ldwrite
>>     bfd_elf_final_link
>>       elf_xtensa_finish_dynamic_sections
>>         elf_xtensa_combine_prop_entries
>>
>> and obviously fails. This only happens when the result is dynamic object,
>> static linking completes successfully.
>> I don't see why this might be considered invalid behaviour, and rather
>> think that
>> the check in the dhcpcd configure script is wrong.
>
> 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.

> 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?

-- 
Thanks.
-- Max

[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@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