public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ncurses: update to 6.0 and rename 5.9 to ncurses-compat
Date: Mon, 02 May 2016 12:36:48 +0100	[thread overview]
Message-ID: <1462189008.10266.318.camel@ipfire.org> (raw)
In-Reply-To: <00e5fc874f55f957215708e1d4a2160d@mail01.ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hi,

@Marcel: Would you look into why this won't build in the toolchain stage on i586
and x86_64 and get back to us? If you can find a solution, please post an
updated version of this patch.

Best,
-Michael

On Sat, 2016-04-30 at 15:45 +0200, Arne Fitzenreiter wrote:
> On 2016-04-23 08:33, Marcel Lorenz wrote:
> > 
> > This patch updates the ncurses to 6.0. The old 5.9 are renamed to
> > ncurses-compat.
> > The compat makes the old libs maintainable and the compat rootfile is
> > cleaned up.
> > The 6.0 is build after 5.9 and all IPFire componentes will build with 
> > 6.0
> > In version 6 only the wide-character libraries are build. The are 
> > usable
> > in both multibyte and traditional 8-bit locales while normal libraries 
> > work
> > properly only in 8-bit locales. The toolchain is only bild with 6.0.
> I have reverted the patch because the toolchain not build on every arch.
> 
> Please also not remove the "EXTRA_CONFIG" part because i need this to 
> fix
> an other build bug on aarch64 buildhosts.
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

       reply	other threads:[~2016-05-02 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00e5fc874f55f957215708e1d4a2160d@mail01.ipfire.org>
2016-05-02 11:36 ` Michael Tremer [this message]
2016-05-03 14:39 ` Marcel Lorenz
2016-04-23  6:33 Marcel Lorenz

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=1462189008.10266.318.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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