Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-09
Date: Sat, 13 Aug 2016 23:55:02 +0200	[thread overview]
Message-ID: <20160813215502.GC5734@free.fr> (raw)
In-Reply-To: <87lh00z80r.fsf@ketchup.mtl.sfl>

Vivien, All,

On 2016-08-13 17:14 -0400, Vivien Didelot spake thusly:
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
> >>     mips64el |                    lldpd-0.9.4 | NOK | http://autobuild.buildroot.net/results/c8a6001f437701ecc75f6c9252935645bda8a8c8/
> >
> > Not sure:
> >
> >   checking if system libevent works as expected... configure: error: *** unusable system libevent
> >
> > Vivien, you are the last person who bumped lldpd, so could you have a
> > look?
> 
> I'm not sure to understand the error.
> 
> Given http://autobuild.buildroot.net/results/c8a/c8a6001f437701ecc75f6c9252935645bda8a8c8/
> here's why I did:
> 
>     buildroot$ git checkout eef80855f1b4533467e04c8e776f1e2f826e5090
>     buildroot$ curl http://autobuild.buildroot.net/results/c8a/c8a6001f437701ecc75f6c9252935645bda8a8c8/config > .config
>     buildroot$ make lldpd
> 
> And this works. What am I doing wrong the reproduce the issue?

I was not able to reproduce it either, and all build failures occur on
Peter's machine:
    http://autobuild.buildroot.org/?reason=lldpd-0.9.4

However, the libevent issue is nto the real issue. The config.log hints
at a much earlier issue:

    [--SNIP--]
    configure:22887: checking for library containing res_init
    configure:22913: /home/peko/autobuild/instance-2/output/host/usr/bin/mips64el-linux-gcc -std=gnu99 -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os  -isystem /usr/include/bsd -DLIBBSD_OVERLAY   -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  conftest.c  -L/home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/lib -lbsd   >&5
    In file included from /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/sys/types.h:29:0,
                     from /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/resolv.h:56,
                     from conftest.c:55:
    /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/bits/types.h:30:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'typedef'
     typedef unsigned char __u_char;
     ^
    In file included from /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/resolv.h:56:0,
                     from conftest.c:55:
    /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/sys/types.h:33:9: error: unknown type name '__u_char'
     typedef __u_char u_char;
             ^
    In file included from /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/sys/types.h:132:0,
                     from /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/resolv.h:56,
                     from conftest.c:55:
    /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/time.h:59:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'typedef'
     typedef __clock_t clock_t;
     ^
    /home/peko/autobuild/instance-2/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/time.h:60:1: error: unknown type name '__END_NAMESPACE_STD'
     __END_NAMESPACE_STD
     ^
    [--SNIP--]


On my machine, I got:

    configure:22887: checking for library containing res_init
    configure:22913: /home/ymorin/dev/buildroot/O/host/usr/bin/mips64el-ctng_n64-linux-gnu-gcc -std=gnu99 -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  conftest.c  >&5
    configure:22913: $? = 0
    configure:22930: result: none required

This is really weird...

I diff-ed the config.log from the build failure with mine, and I saw a
few differences.

Here's the procedure (libbsd is an implicit dependency, which was built
before lldpd in the autobuild failure, so I built it explicitly):

    $ wget -O .config 'http://autobuild.buildroot.net/results/c8a/c8a6001f437701ecc75f6c9252935645bda8a8c8/config'
    $ make O=/home/ymorin/dev/buildroot/O lldpd-depends libbsd
    $ make O=/home/ymorin/dev/buildroot/O lldpd-configure
    $ wget -O config.log.failed 'http://autobuild.buildroot.net/results/c8a6001f437701ecc75f6c9252935645bda8a8c8/lldpd-0.9.4/config.log'
    $ sed -r -i -e 's:/home/peko/autobuild/instance-2/output/:/home/ymorin/dev/buildroot/O/:g'
        # So that I get the same paths in both log files...
    $ diff -du config.log.failed /home/ymorin/dev/buildroot/O/build/lldpd-0.9.4/config.log

But I can't find any interesting hunk before that failure...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-08-13 21:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-09 Thomas Petazzoni
2016-08-10 14:14 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-10 19:36   ` Waldemar Brodkorb
2016-08-10 20:30     ` Thomas Petazzoni
2016-08-10 22:21   ` Alistair Francis
2016-08-11 20:00     ` Yann E. MORIN
2016-08-11 20:23       ` Thomas Petazzoni
2016-08-12 22:33         ` Alistair Francis
2016-08-12  9:31   ` Jörg Krause
2016-08-17  2:27     ` Matthew Weber
2016-08-17  9:20       ` Yann E. MORIN
2016-08-13 21:14   ` Vivien Didelot
2016-08-13 21:55     ` Yann E. MORIN [this message]
2016-08-13 22:14       ` Yann E. MORIN
2016-08-14  0:17         ` Arnout Vandecappelle
2016-08-14  0:37           ` Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160813215502.GC5734@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox