All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix build of lttng-libust
Date: Sun, 5 Nov 2017 17:13:23 +0100	[thread overview]
Message-ID: <cf2f5ee6-d0e2-fcfa-f2af-5ff722d3388c@mind.be> (raw)
In-Reply-To: <CADYdroP3-gaXzRy61r7FraPq+g6MeB5CUGN_nFLyFy3MxxfVvw@mail.gmail.com>



On 31-10-17 11:20, Norbert Lange wrote:
> Hello Thomas,
> 
> I dont know about the autobuilder (can I upload configs to test
> there?), this is an issue I encountered with a private buildroot
> config.
> I tried to reduce it as much as possible, and added the defconfig.
> 
> 2017-10-30 20:40 GMT+01:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
>> Hello,
>>
>> On Mon, 30 Oct 2017 17:31:21 +0100, Norbert Lange wrote:
>>> The build of doc/examples/cmake-multiple-shared-libraries
>>> does fail as a dependend library is missing.
>>> This issue is not specific to builroot and should ideally
>>> be fixed upstream (Issue: https://bugs.lttng.org/issues/1132)
>>>
>>> The fix is done without any indepth knowledge of the CMake
>>> mechanisms, but seems to work correctly
>>>
>>> Signed-off-by: Norbert Lange <norbert.lange@andritz.com>
>>
>> Which specific build problem are you fixing? Is this a problem that has
>> been found by http://autobuild.buildroot.org? If that's the case, we
>> like to include a reference to such an autobuilder failure in the
>> commit log.

 It has not been found by the autobuilders, the only failure is
http://autobuild.buildroot.net/results/c86a82b2fd41316a7a451b20d9274d5c95f89baa
and that's due to CMake version.

 The build error is:

output/host/lib/gcc/x86_64-buildroot-linux-gnu/7.2.0/../../../../x86_64-buildroot-linux-gnu/bin/ld:
warning: liblttng-ust-tracepoint.so.0, needed by
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so, not found
(try using -rpath or -rpath-link)
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so: undefined
reference to `exit_tracepoint'
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so: undefined
reference to `__tracepoint_probe_unregister_queue_release'
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so: undefined
reference to `__tracepoint_probe_register_queue_release'
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so: undefined
reference to `__tracepoint_probe_prune_release_queue'
output/build/lttng-libust-2.9.0/liblttng-ust/.libs/liblttng-ust.so: undefined
reference to `init_tracepoint'
collect2: error: ld returned 1 exit status

 The weird thing is: liblttng-ust.so.0 does have the correct RPATH to find the
tracepoint library. And on all other builds I tried (and apparently including
all the autobuilders), it does find it. So I guess it's either binutils 2.29 or
GCC 7's LTO plugin that is acting up somehow...


 Since this is anyway just an example, wouldn't it be better to just disable the
documentation entirely? I.e. teach configure.ac to understand --disable-doc and
teach Makefile.am to not recurse into doc if docs are disabled?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2017-11-05 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 16:31 [Buildroot] [PATCH 1/1] Fix build of lttng-libust Norbert Lange
2017-10-30 19:40 ` Thomas Petazzoni
2017-10-31 10:20   ` Norbert Lange
2017-11-05 16:13     ` Arnout Vandecappelle [this message]
2017-11-05 16:31       ` Yann E. MORIN
2017-11-05 19:55         ` Philippe Proulx
2017-11-05 21:10           ` Yann E. MORIN
2017-11-05 21:20             ` Yann E. MORIN
2017-11-05 20:36       ` Norbert Lange
2017-11-05 22:02         ` Arnout Vandecappelle
2017-11-06 21:06           ` Philippe Proulx
2017-11-06 21:12             ` Thomas Petazzoni
2017-11-06 21:41               ` Philippe Proulx

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=cf2f5ee6-d0e2-fcfa-f2af-5ff722d3388c@mind.be \
    --to=arnout@mind.be \
    --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.