Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] alsa-lib: add patch to fix incorrect code dependency
Date: Sat, 12 Aug 2017 13:50:13 +0200	[thread overview]
Message-ID: <20170812135013.14446155@windsurf> (raw)
In-Reply-To: <20170812100046.GB3021@scaer>

Hello,

On Sat, 12 Aug 2017 12:00:46 +0200, Yann E. MORIN wrote:

> > +/home/thomas/projets/buildroot/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libasound.a(pcm_dmix.o): In function `snd_pcm_dmix_sync_ptr':
> > +pcm_dmix.c:(.text+0x83c): warning:
> > +/home/thomas/projets/buildroot/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libasound.a(rawmidi_symbols.o):(.data+0x4): undefined reference to `_snd_module_rawmidi_virt'
> > +collect2: error: ld returned 1 exit status
> > +
> > +To fix this, we make sure that rawmidi_symbols.c only uses
> > +_snd_module_rawmidi_virt when available.
> > +
> > +Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>  
> 
> Upstream status?

I submitted it upstream after sending the Buildroot patch, so I didn't
had the link. But it's submitted upstream, see
https://www.spinics.net/lists/alsa-devel/msg65902.html.

Best regards,

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

  reply	other threads:[~2017-08-12 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 21:21 [Buildroot] [PATCH 1/2] alsa-lib: add patch to fix incorrect code dependency Thomas Petazzoni
2017-08-11 21:21 ` [Buildroot] [PATCH 2/2] Revert "alsa-utils: amidi option needs seq support in alsa-lib" Thomas Petazzoni
2017-08-12 10:01   ` Yann E. MORIN
2017-08-12 10:00 ` [Buildroot] [PATCH 1/2] alsa-lib: add patch to fix incorrect code dependency Yann E. MORIN
2017-08-12 11:50   ` Thomas Petazzoni [this message]
2017-08-12 16:30     ` Arnout Vandecappelle

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=20170812135013.14446155@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox