All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-18
Date: Wed, 24 Aug 2016 18:51:28 +0200	[thread overview]
Message-ID: <20160824185128.68a2fdef@free-electrons.com> (raw)
In-Reply-To: <20160819222925.GD6096@free.fr>

Hello,

On Sat, 20 Aug 2016 00:29:25 +0200, Yann E. MORIN wrote:

> There is another type of issues for kmsxx:
> 
>     http://autobuild.buildroot.org/results/5e9/5e9963c1f11af40a6349da524fc128116a1d9e6e/build-end.log
> 
>     [ 81%] Linking CXX executable ../bin/fbtestpat
>     /tmp/ccvhwy4u.ltrans0.ltrans.o: In function `main':
>     <artificial>:(.text.startup+0xa4): undefined reference to `kms::ExtCPUFramebuffer::ExtCPUFramebuffer(unsigned int, unsigned int, kms::PixelFormat, unsigned char*, unsigned int)'
>     <artificial>:(.text.startup+0xd4): undefined reference to `kms::draw_test_pattern(kms::IMappedFramebuffer&)'
>     <artificial>:(.text.startup+0x10c): undefined reference to `kms::RGB::RGB(unsigned char, unsigned char, unsigned char)'
>     <artificial>:(.text.startup+0x128): undefined reference to `kms::draw_text(kms::IMappedFramebuffer&, unsigned int, unsigned int, std::string const&, kms::RGB)'
>     <artificial>:(.text.startup+0x188): undefined reference to `kms::ExtCPUFramebuffer::~ExtCPUFramebuffer()'
>     <artificial>:(.text.startup+0x2a8): undefined reference to `kms::ExtCPUFramebuffer::~ExtCPUFramebuffer()'
>     collect2: error: ld returned 1 exit status
>     make[3]: *** [bin/fbtestpat] Error 1
> 
> And I was not able to reproduce it either... :-/

This issue happened only once:

	http://autobuild.buildroot.net/?reason=kmsxx-bd5f6471e619a6ba2987bc7f66ef78a531f94d6c

I've restarted the same build on the same machine, I'll see if it
happens again.

> > Secondary question: other packages are using libbsd, why aren't we
> > seeing other occurrences of this problem?  
> 
> Because none is using libbsd-overlay.pc, just libbsd.pc.

OK.

> The underlying issue, that pkconf does not munge -isystem, is being
> investigated by the pkconf guys:
>     https://github.com/pkgconf/pkgconf/issues/94

OK. I'll apply your lldpd workaround then.

Thanks for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-24 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-18 Thomas Petazzoni
2016-08-19 22:07 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-19 22:19   ` Yann E. MORIN
2016-08-19 22:22   ` Waldemar Brodkorb
2016-08-20 10:27     ` Thomas Petazzoni
2016-08-19 22:29   ` Yann E. MORIN
2016-08-24 16:51     ` Thomas Petazzoni [this message]
2016-08-24 20:40       ` [Buildroot] Remaining kmsxx build issue Thomas Petazzoni
2016-08-26 19:30         ` Arnout Vandecappelle
2016-08-26 19:42           ` Thomas Petazzoni
2016-08-20  9:17   ` [Buildroot] Analysis of build results for 2016-08-18 Rahul Bedarkar
2016-08-20  9:22     ` Thomas Petazzoni
2016-08-20 10:11       ` Rahul Bedarkar
2016-08-20 13:52   ` Gustavo Zacarias
2016-08-20 13:55     ` [Buildroot] odroid-mali issue Thomas Petazzoni
2016-08-21  6:42   ` [Buildroot] Analysis of build results for 2016-08-18 Baruch Siach

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=20160824185128.68a2fdef@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.