Update jpeg name mangling to allow linking with both IJG libjpeg and turbo_libjpeg

In some situation on CrOS we need to have with both IJG libjpeg and libjpeg_turbo. This CL update the jpeg name mangling to allow linking both.

1) Prefixing with just chromium_ was insufficient because WebKit will pull libjpeg_turbo on most platforms and that has the same demangling rules
2) Two symbols were missing:
   jpeg_std_message_table
   jpeg_natural_order
3) Sorted macros in alpha order.

BUG=144296
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=153947

[Emmanuel Saint-loubert-Bié, 2012-08-29 01:20:34]

Hi Tony,

Since you seem to have been touching this library please review. Thanks,

-- Emmanuel

[tony, 2012-08-29 16:48:13]

I don't understand.  Doesn't WebKit and chromium use the same copy of
libjpeg_turbo?  Are you saying we have 2 copies of libjpeg_turbo in the same
binary?

[Emmanuel Saint-loubert-Bié, 2012-08-29 16:50:09]

Hi Tony,

What I am saying is that unless I land this CL we cannot have two copies.  And
for ChromeOS we want to have both (see  crbug.com/144296 which will probably
answer all your questions)

-- Emmanuel

[tony, 2012-08-29 16:58:06]

LGTM

Please update the change description to say 'why' we need both.  I would make
sure to mention that this is for ChromeOS.

[Emmanuel Saint-loubert-Bié, 2012-08-29 17:04:42]

On 2012/08/29 16:58:06, tony wrote:
> LGTM
> 
> Please update the change description to say 'why' we need both.  I would make
> sure to mention that this is for ChromeOS.


Agreed. I updated the decsription and added: In some situation on CrOS we need
to have with both IJG libjpeg and libjpeg_turbo. This CL update the jpeg name
mangling to allow linking both.

[commit-bot: I haz the power, 2012-08-29 17:05:08]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/saintlou@chromium.org/10894031/1