From: Mark Knecht <markknecht@gmail.com>
To: Gentoo AMD64 <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Libjpeg-Turbo Drops Newer ABIs
Date: Fri, 2 Aug 2013 12:17:35 -0700 [thread overview]
Message-ID: <CAK2H+eek6y0nvPrbCDKjN=9NqZ449Qk_d5A5P7+-iq2gtUpWcQ@mail.gmail.com> (raw)
In-Reply-To: <20130802145805.d9673faf37063835701db3f7@comcast.net>
On Fri, Aug 2, 2013 at 11:58 AM, Frank Peters <frank.peters@comcast.net> wrote:
> On Fri, 2 Aug 2013 11:28:10 -0700
> Mark Knecht <markknecht@gmail.com> wrote:
>
>>
>> Frank stated it's the 'default', but
>> I guess it's really only the default for new installs.
>>
>
> See these links:
>
> http://forums.gentoo.org/viewtopic-t-870799-start-0.html
>
> http://forums.gentoo.org/viewtopic-t-921342.html
>
>
> There is no problem with the latest libjpeg-turbo-1.3.0-r2. I am
> just wondering why the sudden drop of the ABI's. The legacy
> libjpeg has gone on to ABI 9 whereas libjpeg-turbo is reverting
> to the ancient ABI 6.
>
> Frank Peters
Thanks for the links Frank.
I also have some deep, dark recollection of a news item about this
topic which likely I didn't pay a lot of attention to. I'll probably
update a machine today and make sure there's no obvious problems here
before I do my important machines.
And I do understand that you weren't saying there was a problem - only
that you were having to rebuild a lot of stuff so you were looking for
background on why.
Cheers,
Mark
next prev parent reply other threads:[~2013-08-02 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 17:45 [gentoo-amd64] Libjpeg-Turbo Drops Newer ABIs Frank Peters
2013-08-02 18:02 ` Mark Knecht
2013-08-02 18:18 ` Canek Peláez Valdés
2013-08-02 18:22 ` Rich Freeman
2013-08-02 18:28 ` Mark Knecht
2013-08-02 18:58 ` Frank Peters
2013-08-02 19:17 ` Mark Knecht [this message]
2013-08-03 7:17 ` Sergey Popov
2013-08-02 18:24 ` Mark Knecht
2013-08-02 18:40 ` Mark Knecht
2013-08-02 18:50 ` Barry Schwartz
2013-08-02 19:06 ` Frank Peters
2013-08-02 19:31 ` Barry Schwartz
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='CAK2H+eek6y0nvPrbCDKjN=9NqZ449Qk_d5A5P7+-iq2gtUpWcQ@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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