All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-28
Date: Sun, 29 Nov 2015 22:26:21 +0100	[thread overview]
Message-ID: <1448832381.1886.12.camel@embedded.rocks> (raw)
In-Reply-To: <20151129150031.5f26aeba@free-electrons.com>

Dear Thomas,
Dear Brendan,

On So, 2015-11-29 at 15:00 +0100, Thomas Petazzoni wrote:
> J?rg,
> 
> On Sun, 29 Nov 2015 11:08:41 +0100, J?rg Krause wrote:
> 
> > > ??????x86_64 |????????????????arptables-0.0.4 | NOK | http://auto
> > > buil
> > > d.buildroot.net/results/002bea21e0b902eecca245c9c889a55583c0751c/
> > 
> > I suggest to disable arptables for musl toolchains for now. I think
> > it
> > is not easily feasible to untangle the mixed used of linux/netinet
> > headers [1].
> 
> I'm fine with this option since arptables does not have any reverse
> dependency. However:
> 
> ?1/ We have two patches in package/arptables/ that were meant to fix
> ????the build of arptables with musl, so we should get rid of them.
> Or
> ????instead, you can contact Brendan Heading
> ????<brendanheading@gmail.com>, who did commit
> ????61fe902bacaca7c5fdcc7d3a68ded95a835fe2e1, which was supposed to
> ????make arptables build properly with musl. Brendan ?
> 
> ?2/ The problem should be reported upstream (either to musl to get
> some
> ????better insight, or to arptables)

I'll sent a patch to disable arptables for musl. If Brendan has success
to fix it, we can re-enable it again, okay?

I'll report to musl and upstream, too.

> 
> > > ?????????arm |?????????????shairport-sync-2.6 | NOK | http://auto
> > > buil
> > > d.buildroot.net/results/04498ba9e44f022f4bebb339f26aac76fce3e06c/
> > 
> > I'll have a look at this later today.
> 
> Good.

Some alsa-lib plugins (pcm_meter, pcm_dmix) require dlopen and dlsym.
However, shairport-sync does not require any of these plugins. Since we
cannot adjust the plugins from the package config, I would suggest to
disable shairport-sync for static builds. Okay?

J?rg

      parent reply	other threads:[~2015-11-29 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-28 Thomas Petazzoni
2015-11-29 10:08 ` Jörg Krause
2015-11-29 14:00   ` Thomas Petazzoni
2015-11-29 14:06     ` Brendan Heading
2015-11-29 14:15       ` Thomas Petazzoni
2015-11-29 14:24         ` Brendan Heading
2015-11-29 14:28           ` Thomas Petazzoni
2015-11-29 21:26     ` Jörg Krause [this message]

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=1448832381.1886.12.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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.