Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: add a 'Known issues' chapter
Date: Sun, 06 Oct 2013 20:36:34 +0200	[thread overview]
Message-ID: <87r4byfdql.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1381081747-20598-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sun, 6 Oct 2013 19:49:07 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Add a 'Known issues' chapter, which lists the exceptions I have
 Thomas> currently in the autobuilder scripts to avoid known problems from
 Thomas> occuring. I believe it is more useful to document them rather than
 Thomas> keeping them hidden in my autobuilder script.

The uClibc dependencies are already documented in Config.in, but ok.

 Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 Thomas> ---
 Thomas>  docs/manual/known-issues.txt | 32 ++++++++++++++++++++++++++++++++
 Thomas>  docs/manual/manual.txt       |  2 ++
 Thomas>  2 files changed, 34 insertions(+)
 Thomas>  create mode 100644 docs/manual/known-issues.txt

 Thomas> diff --git a/docs/manual/known-issues.txt b/docs/manual/known-issues.txt
 Thomas> new file mode 100644
 Thomas> index 0000000..f731f8f
 Thomas> --- /dev/null
 Thomas> +++ b/docs/manual/known-issues.txt
 Thomas> @@ -0,0 +1,32 @@
 Thomas> +// -*- mode:doc; -*-
 Thomas> +// vim: set syntax=asciidoc:
 Thomas> +
 Thomas> +Known issues
 Thomas> +============
 Thomas> +
 Thomas> +* The +ltp-testsuite+ package does not build with the default uClibc
 Thomas> +  configuration used by the Buildroot toolchain backend. The LTP
 Thomas> +  testsuite uses several functions that are considered obsolete, such
 Thomas> +  as sigset() and others. uClibc configuration options such as
 Thomas> +  DO_XSI_MATH, UCLIBC_HAS_OBSOLETE_BSD_SIGNAL and
 Thomas> +  UCLIBC_SV4_DEPRECATED are needed if one wants to build the
 Thomas> +  +ltp-testsuite+ package with uClibc. You need to either a glibc or

s/either/either use/

In all 3 sections.

 Thomas> +* The +prboom+ package triggers a compiler failure with the SuperH 4
 Thomas> +  compiler from Soucery CodeBench, version 2012.09.

I believe we have a lot of other situations with packages triggering
internal compiler errors, especially for microblaze and avr32.

Committed with these changes, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-10-06 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 17:49 [Buildroot] [PATCH] docs/manual: add a 'Known issues' chapter Thomas Petazzoni
2013-10-06 18:36 ` Peter Korsgaard [this message]
2013-10-06 21:22   ` Thomas Petazzoni
2013-10-06 18:37 ` 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=87r4byfdql.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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