From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Wed, 22 May 2013 16:04:05 +0200 [thread overview]
Message-ID: <20130522160405.3b37b060@skate> (raw)
In-Reply-To: <321768C95D21724485BCE784F1BE98473EB1DCB9@DBDE04.ent.ti.com>
Dear prabindh,
On Wed, 22 May 2013 06:35:55 -0700 (PDT), prabindh wrote:
> Yes, I am talking about rebuilding the userspace libraries. I deliver
> the Graphics drivers for SGX.
Ah, nice to have you on board then :-) We may certainly have questions
as we integrate those libraries in Buildroot.
> The aspect of uclibc breaking compatibility was not clear to me
> earlier. How do you plan to support "any" closed source packages
> then ?
With (e)glibc libraries, that we support through the external toolchain
mechanism.
> Why cant we have backward compatibility in uclibc ?
I am not sure how accurate
https://www.kernel.org/pub/linux/libs/uclibc/Glibc_vs_uClibc_Differences.txt
is, must it says:
"""
3) uClibc does not even attempt to ensure binary compatibility across
releases. When a new version of uClibc is released, you may or may not
need to recompile all your binaries.
"""
That said, the uClibc web site, at http://www.uclibc.org/oldnews.html,
says:
"""
Please be aware we will break binary compatibilty in the upcoming
0.9.27 release to implement a few necessary changes we have been
postponing. That will hopefully be the last ABI change before we freeze
the ABI for the upcoming 1.0.x stable uClibc series.
"""
So it looks like there was some intention about having a stable ABI at
some point. But this news was from 2004, and the 1.0.x stable uClibc
series still hasn't been released, 9 years later.
Maybe other people can comment? Or maybe we should bring the issue to
the uClibc developers and see what they say?
In the mean time, my expectation is that we will be using all those
binary-only libraries on top of glibc/eglibc only. If you're doing some
crazy OpenGL multimedia stuff, you can anyway afford the comparatively
small additional cost of using glibc/eglibc in your embedded Linux
system.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-22 14:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04 ` Thomas Petazzoni
2013-02-19 4:18 ` prabindh
2013-02-19 15:29 ` Thomas Petazzoni
2013-05-20 3:31 ` prabindh
2013-05-22 11:55 ` Sundareson, Prabindh
2013-05-22 12:17 ` Thomas Petazzoni
2013-05-22 12:23 ` prabindh
2013-05-22 12:31 ` Thomas Petazzoni
2013-05-22 12:36 ` prabindh
2013-05-22 13:06 ` Thomas Petazzoni
2013-05-22 13:26 ` Sundareson, Prabindh
2013-05-22 13:30 ` Thomas Petazzoni
2013-05-22 13:35 ` prabindh
2013-05-22 14:04 ` Thomas Petazzoni [this message]
2013-05-22 14:18 ` Spenser Gilliland
2013-05-22 14:39 ` Thomas Petazzoni
2013-05-22 15:57 ` prabindh
2013-05-22 17:33 ` Spenser Gilliland
2013-05-23 20:38 ` Wojciech Sleńska
2013-05-22 12:16 ` Thomas Petazzoni
2013-05-22 12:21 ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45 ` Thomas Petazzoni
2013-01-14 12:48 ` Sagaert Johan
2013-01-14 13:10 ` Thomas Petazzoni
2013-01-17 9:03 ` Arnout Vandecappelle
2013-02-06 9:56 ` Daniel Nyström
2013-02-06 10:04 ` Thomas Petazzoni
2013-02-06 10:12 ` Frédéric COIFFIER
2013-02-06 10:43 ` 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=20130522160405.3b37b060@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