415861 - AIX Compilation error for trunk build source jdcolor.c :Operation between types "unsigned char" and "unsigned char*" is not allowed

Status: RESOLVED DUPLICATE of bug 44781

(Firefox Build System :: General, defect)

Description

[Shailen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

While compiling trunk build source mozilla/jpeg/jdcolor.c on
AIX, getting below compilation error -

mozilla/jpeg/jdcolor.c", line 299.8: 1506-234 (E) Expecting a new-line character on #endif directive.
mozilla/jpeg/jdcolor.c", line 464.17: 1506-068 (S) Operation between types "unsigned char" and "unsigned char*" is not allowed.
mozilla/jpeg/jdcolor.c", line 465.17: 1506-068 (S) Operation between types "unsigned char" and "unsigned char*" is not allowed.
mozilla/jpeg/jdcolor.c", line 468.17: 1506-068 (S) Operation between types "unsigned char" and "unsigned char*" is not allowed.
gmake[1]: *** [jdcolor.o] Error 1




Reproducible: Always

Steps to Reproduce:
1.Build Mozilla Firefox Trunk build on AIX with Gnome 2.12 RPMS of 64 bit
version.
2.
3.
Actual Results:  
Build fails with the above errors.

Expected Results:  
No build failure

Comment 1

[Shailen]

Attachment: Patch V1

Modified the code to have operation between unsigned chars

Comment 2

[Benjamin Smedberg]

Comment on attachment 301627 [details] [diff] [review]
Patch V1

I think this is libjpeg... asking stuart, the module owner, for review.

Comment 3

[Stuart Parmenter]

Marti:  Can you take a look at this patch?

Comment 4

[Marti]

Sure, but this is not related with littlecms. Maybe the author/mantainer of libjpeg would be more proper.

Comment 5

[Stuart Parmenter]

Comment on attachment 301627 [details] [diff] [review]
Patch V1

argh, whoops.  not sure why i thought this was in littlecms....  I'll take a look at it.

Comment 6

[Shailen]

I am able to compile the trunk build without the above errors. I believe the error is fixed with bug 44781 fix.