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 8011] When building only busybox and strace, strace fails on not finding bluetooth/bluetooth.h
Date: Sat, 11 Apr 2015 16:01:38 +0000 (UTC)	[thread overview]
Message-ID: <20150411160138.C96E4804F1@busybox.osuosl.org> (raw)
In-Reply-To: <bug-8011-163@https.bugs.busybox.net/>

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

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2015-04-11 16:01:38 UTC ---
Could you please indicate the Buildroot version you're using, and attach a
minimal Buildroot .config that exhibits the problem?

I'm routinely building system with just Busybox and strace, and it just works
fine for me, so there is probably something special in the configuration you're
using.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  reply	other threads:[~2015-04-11 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 15:09 [Buildroot] [Bug 8011] New: When building only busybox and strace, strace fails on not finding bluetooth/bluetooth.h bugzilla at busybox.net
2015-04-11 16:01 ` bugzilla at busybox.net [this message]
2015-04-11 16:09 ` [Buildroot] [Bug 8011] " bugzilla at busybox.net
2015-04-11 16:09 ` bugzilla at busybox.net
2015-04-11 17:27 ` bugzilla at busybox.net
2015-04-11 18:40 ` bugzilla at busybox.net
2015-04-11 18:44 ` bugzilla at busybox.net
2015-04-11 21:03 ` bugzilla at busybox.net
2015-04-12 12:06 ` bugzilla at busybox.net
2015-04-12 12:15 ` bugzilla at busybox.net
2015-04-12 12:25 ` bugzilla at busybox.net
2015-04-12 12:46 ` bugzilla at busybox.net
2015-04-17 13:02 ` bugzilla at busybox.net

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=20150411160138.C96E4804F1@busybox.osuosl.org \
    --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.