From: Mario Lang <mlang@blind.guru>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/brltty: disable features and add optional dependencies
Date: Mon, 18 Dec 2017 12:31:43 +0100 [thread overview]
Message-ID: <871sjsclwg.fsf@home.blind.guru> (raw)
In-Reply-To: <20171218110127.6df4ba7e@windsurf> (Thomas Petazzoni's message of "Mon, 18 Dec 2017 11:01:27 +0100")
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> On Mon, 18 Dec 2017 10:51:43 +0100, Mario Lang wrote:
>> * --without-midi-package should fix a number of autobuild failures.
>
> Which ones? We like to have references to autobuilder failures.
At least these two:
http://autobuild.buildroot.net/results/0c4f557c2ad276b1ed065119532af37c0af5f014
http://autobuild.buildroot.net/results/ea82b7c7732821368746ddddb5d529e97c9b6c16
>> * Disable a number of speech drivers to avoid build failures
>> if they are installed on the host.
>> * Optional dependency on espeak and flite fixes builds where
>> espeak or flite are installed on the host.
>
> Autobuilder failure references ?
These failures didn't show up on any autobuilder, as autobuilders
typically don't have commercial speech synthesizers or espeak/flite
installed on the host. But these build failures showed up during builds
of BRLTTY users. In particular, espeak, flite and speechd were
accidentally picked up from the host during configure.
--
CYa,
????? | Blog: <https://blind.guru/> GitHub: <https://github.com/mlang/>
.''`. | Twitter: @blindbird23 FaceBook: disyled
: :' : | SoundCloud: <soundcloud.com/mario-lang>
`. `' | YouTube: <youtube.com/user/mlang23>
`-
next prev parent reply other threads:[~2017-12-18 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:51 [Buildroot] [PATCH] package/brltty: disable features and add optional dependencies Mario Lang
2017-12-18 10:01 ` Thomas Petazzoni
2017-12-18 11:31 ` Mario Lang [this message]
2017-12-18 14:57 ` Thomas Petazzoni
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=871sjsclwg.fsf@home.blind.guru \
--to=mlang@blind.guru \
--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