All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10336] lttng compilation fails : linking error
Date: Tue, 31 Oct 2017 21:22:50 +0000	[thread overview]
Message-ID: <bug-10336-163-kXtsLmVt3q@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10336-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10336

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I can't reproduce with the following defconfig:

BR2_x86_64=y
BR2_HOST_DIR="/home/test/custom-host-dir/"
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_GCC_VERSION_5_X=y
BR2_PACKAGE_LTTNG_LIBUST=y

Are you sure your build failure is reproducible after doing a "make clean all"
? If it is, then please reopen this bug, attaching a minimal defconfig that
allows to reproduce the build failure.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2017-10-31 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 16:10 [Buildroot] [Bug 10336] New: lttng compilation fails : linking error bugzilla at busybox.net
2017-10-31 21:22 ` bugzilla at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-03 10:53 [Buildroot] [Bug 10336] " Norbert Lange

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=bug-10336-163-kXtsLmVt3q@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.