From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] giflib: fix description about compatibility with libungif
Date: Sun, 12 Apr 2015 11:10:44 +0200 [thread overview]
Message-ID: <20150412091044.GA4218@free.fr> (raw)
In-Reply-To: <20150412084723.GH2279@tarshish>
Baruch, All,
On 2015-04-12 11:47 +0300, Baruch Siach spake thusly:
> On Sun, Apr 12, 2015 at 10:43:05AM +0200, Fabio Porcedda wrote:
> > Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
> > ---
> > package/giflib/Config.in | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/package/giflib/Config.in b/package/giflib/Config.in
> > index 70368dc..bb5741a 100644
> > --- a/package/giflib/Config.in
> > +++ b/package/giflib/Config.in
> > @@ -1,7 +1,7 @@
> > config BR2_PACKAGE_GIFLIB
> > bool "giflib"
> > help
> > - giflib is a library for reading and writing gif images. It is API and
> > + giflib is a library for reading and writing gif images. It was API and
> > ABI compatible with libungif which was in wide use while the LZW
> > compression algorithm was patented.
>
> So giflib is not compatible to libungif anymore?
No it is no longer comatible. It was, until version 5.0 introduced
changes for thread-safety. Quoting their website:
The 5.x versions change the API slightly in a way that isn't
compatible with older shared libraries.
and:
[...] the signatures of the file-opener functions were changed in
5.0 in order to make the library fully reentrant and thread-safe
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-04-12 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 8:43 [Buildroot] [PATCH] giflib: fix description about compatibility with libungif Fabio Porcedda
2015-04-12 8:47 ` Baruch Siach
2015-04-12 8:57 ` Fabio Porcedda
2015-04-12 9:08 ` Baruch Siach
2015-04-12 9:13 ` Yann E. MORIN
2015-04-12 10:04 ` Fabio Porcedda
2015-04-12 9:10 ` Yann E. MORIN [this message]
2015-04-12 10:21 ` Fabio Porcedda
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=20150412091044.GA4218@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.