Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of VLC build failures
Date: Tue, 25 Feb 2014 08:15:32 +0100	[thread overview]
Message-ID: <530C4314.4000203@mind.be> (raw)
In-Reply-To: <20140223110021.16b6b976@skate>

On 23/02/14 11:00, Thomas Petazzoni wrote:
>>    aarch64 |                      vlc-2.1.2 | NOK | http://autobuild.buildroot.net/results/64c4f405c7bd72e5e9dc8fc0823677b79e476e8e/
>> >     x86_64 |                      vlc-2.1.2 | NOK | http://autobuild.buildroot.net/results/8726be7b5432dbab0b0ca5a0c0e5152a66c45171/
>> >     x86_64 |                      vlc-2.1.2 | NOK | http://autobuild.buildroot.net/results/b319c6722395a99f98790e6c4582dc872d7ef0d9/
> Weird problems :)
> 

 I've been looking at vlc off and on for the last couple of days. I don't
have a solution yet, but I do have a number of observations.

- When I disable all optional packages, it does work. But I haven't been
able to pinpoint a single dependency that makes it fail. I haven't been
methodical about it, though.

- vlc uses a homegrown "dolt" instead of libtool; however, it does
support libtool as a fallback. Switching to that doesn't make a
difference. And anyway, for linking it calls into libtool.

- The relocatable object files are created in .libs/*.o like they usually
are. They just don't get linked into a .libs/*.so library.

- Our AUTOREGEN breaks a lot of things. During autoregen I get errors like:

modules/stream_out/Modules.am:18: warning: source file 'transcode/osd.c'
is in a subdirectory,
modules/stream_out/Modules.am:18: but option 'subdir-objects' is disabled
modules/stream_out/Makefile.am:10:   'modules/common.am' included from here

and at configure time I get:
configure: WARNING: unrecognized options: --disable-gtk-doc,
--disable-doc, --disable-docs, --disable-documentation, --with-xmlto,
--with-fop, --enable-ipv6, --disable-shout, --disable-twolame,
--disable-dca, --disable-dirac, --disable-schroedinger,
--disable-quicksync, --disable-fluidsynth, --disable-kate,
--disable-caca, --disable-samplerate, --disable-chromaprint,
--disable-goom, --disable-mtp, --enable-bonjour, --enable-flac,
--enable-opus, --enable-libmpeg2, --enable-svg, --enable-theora,
--enable-upnp, --enable-vorbis, --enable-libxml2, --enable-speex,
--enable-udev



 My feeling is that vlc is currently not in a state that we can release
it. I have no issue with including some package that doesn't work very
well in a release, but for a flagship package like vlc I think it's
important that we really get it right. And currently we don't.


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-02-25  7:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-22 Thomas Petazzoni
2014-02-23 10:00 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-23 10:16   ` Thomas De Schampheleire
2014-02-23 10:56     ` Thomas Petazzoni
2014-02-23 15:45   ` Peter Korsgaard
2014-02-23 23:46   ` Ezequiel García
2014-02-24 21:16     ` Thomas Petazzoni
2014-02-24 21:18       ` Ezequiel García
2014-02-26 21:10         ` Thomas Petazzoni
2014-02-24 10:12   ` Vicente Olivert Riera
2014-02-24 10:30     ` Vicente Olivert Riera
2014-02-25  7:15   ` Arnout Vandecappelle [this message]
2014-02-25 15:17     ` [Buildroot] Analysis of VLC " Simon Dawson
2014-02-25 16:58       ` Arnout Vandecappelle
2014-02-25 20:25         ` Peter Korsgaard
2014-02-25 18:14     ` Thomas Petazzoni
2014-02-25 21:08   ` [Buildroot] Analysis of " Samuel Martin

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=530C4314.4000203@mind.be \
    --to=arnout@mind.be \
    --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