All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] host-python build issue
Date: Thu, 8 Jan 2015 12:26:48 +0100	[thread overview]
Message-ID: <20150108122648.26a06caf@free-electrons.com> (raw)
In-Reply-To: <54AE5AF0.1040008@gmail.com>

Dear Zoltan Gyarmati,

On Thu, 08 Jan 2015 11:24:48 +0100, Zoltan Gyarmati wrote:

> Yes, and the files of the package:
> $dpkg -L oss4-dev
> /.
> /usr
> /usr/include
> /usr/include/linux
> /usr/include/linux/soundcard.h
> package diverts others to: /usr/include/linux/soundcard.h.oss3
> /usr/share
> /usr/share/doc
> /usr/share/doc/oss4-dev
> /usr/share/doc/oss4-dev/copyright
> /usr/share/doc/oss4-dev/changelog.gz
> /usr/share/doc/oss4-dev/changelog.Debian.gz
> /usr/share/doc/oss4-dev/README.Debian
> 
> I didn't notice before that the header file in question was diverted, so
> after removing the package, host-python builds properly, thanks for the
> hint!

I have no idea why this package moves a kernel headers to a different
name. Obviously it can break quite a lot of userspace
applications/libraries. I don't really understand why they are doing
this.

That being said, I don't think the ossaudio Python module is very
useful, so disabling its build is probably the right thing to do for
host-python, and for target python, make it optional.

Thanks,

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

      reply	other threads:[~2015-01-08 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 13:11 [Buildroot] host-python build issue Zoltan Gyarmati
2015-01-07 16:43 ` Thomas Petazzoni
2015-01-07 16:45   ` Charles Krinke
2015-01-07 16:51     ` Thomas Petazzoni
2015-01-08  9:40       ` Zoltan Gyarmati
2015-01-08  9:56         ` Thomas Petazzoni
2015-01-08 10:24           ` Zoltan Gyarmati
2015-01-08 11:26             ` Thomas Petazzoni [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=20150108122648.26a06caf@free-electrons.com \
    --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 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.