From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot] libevas build failure analysis
Date: Wed, 4 Dec 2013 10:27:53 +0100 [thread overview]
Message-ID: <20131204102753.419a9057@skate> (raw)
In-Reply-To: <CAKAx1ciXsAPtG-uegQC5CPO8yJFPG4gn7CvuzVZ2JQh_T0FrAA@mail.gmail.com>
Dear Lionel Orry,
On Tue, 3 Dec 2013 09:45:15 +0100, Lionel Orry wrote:
> They just released the 1.8 version, I think it's time to think about
> the bump, but there are some quite fundamental changes between 1.7 and
> 1.8 (most noticeable one is the merged tree instead of separate source
> code for core libraries), and the bump is probably not that easy at
> first, and then, I also suppose there are some applications that may
> still need 1.7 among buildroot users.
Are you sure 1.8 breaks the compatibility with 1.7 ? I don't think so.
It's not because in terms of source code everything is now inside a
single tarball that the compatibility for applications has been broken.
> I would then suggest to have EFL 1.7 and EFL 1.8 in parallel for some
> time. Maybe we should create efl18 package.
Before doing that, I'd like to understand how/why EFL 1.8 is
incompatible with EFL 1.7.
> As for EFL 1.7, maybe the easiest to do is require a toolchain with
> threads support.
I agree.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-04 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 19:04 [Buildroot] [buildroot] libevas build failure analysis arnaud aujon
2013-11-28 19:11 ` Lionel Orry
2013-11-28 19:35 ` arnaud aujon
2013-12-03 8:32 ` arnaud aujon
2013-12-03 8:45 ` Lionel Orry
2013-12-03 9:13 ` arnaud aujon
2013-12-04 9:28 ` Thomas Petazzoni
2013-12-04 9:27 ` Thomas Petazzoni [this message]
2013-12-04 10:24 ` Lionel Orry
2013-12-04 12:21 ` Lucas De Marchi
2013-12-04 12:56 ` Lionel Orry
2013-12-04 14:30 ` Lucas De Marchi
2013-12-04 12:29 ` 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=20131204102753.419a9057@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox