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 11:24:45 -0700 [thread overview]
Message-ID: <CAK2H+ecxRKC8Cv5cTi_bNXwCMJZChJzo14b1MrM9uBhzihY8ew@mail.gmail.com> (raw)
In-Reply-To: <CADPrc80p5BGOfSARLagaKeLvnt32SncQPCRtu-X0PA+R1XOVsQ@mail.gmail.com>
On Fri, Aug 2, 2013 at 11:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> On Fri, Aug 2, 2013 at 1:02 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> On Fri, Aug 2, 2013 at 10:45 AM, Frank Peters <frank.peters@comcast.net> wrote:
>>> Libjpeg-turbo has been the default jpeg image processor on Gentoo
>>> for some time now.
>>
>> Really? I don't have it on any of my systems here and I run (mostly) stable.
>>
>> What pulls it in?
>
> virtual/jpeg pulls media-libs/libjpeg-turbo before media-libs/jpeg.
>
Interesting, and thanks for the info. Would it switch to libjpeg-turbo
if jpeg is already properly installed?
I suspect it would not or I'd likely have libjpeg-turbo here...
>> No answer to your underlying question as I haven't seen then problem
>> here and didn't find anything in Google.
>
> Netiher do I. I have libjpeg-turbo, but I'm unaware of any problems with it.
>
> Regards.
> --
> Canek Peláez Valdés
> Posgrado en Ciencia e Ingeniería de la Computación
> Universidad Nacional Autónoma de México
>
Cheers,
Mark
next prev parent reply other threads:[~2013-08-02 18:24 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
2013-08-03 7:17 ` Sergey Popov
2013-08-02 18:24 ` Mark Knecht [this message]
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+ecxRKC8Cv5cTi_bNXwCMJZChJzo14b1MrM9uBhzihY8ew@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