From: Ben Gribaudo <rubytalk@...>
Date: 2006-04-06T04:04:54+09:00
Subject: Re: Pointer Signedness Errors When Compiling 1.8.4

Hi Zach,

I get that output during compilation. Thanks for the info on not needing 
to worry about it. Why do I receive it, though? In particular, I'm 
curious as I'm experiencing Ruby segmentation faulting--could the 
mis-matched pointer signedness cause a memory access violation?

Ben

zdennis wrote:
> When ruby runs you get this output? Or just when you are compiling? If
> it's just when you are compiling don't worry about it if ruby finishes
> compiling with no explicit **Error** 's.
>
> Zach
>
> Ben Gribaudo wrote:
>   
>> Hi,
>>
>> I'm working on compiling Ruby 1.8.4 on Ubunty Breezy (5.10) using gcc
>> 4.0.2 (20050808 prerelease Ubuntu 4.0.1-4ubuntu9). When make is run,
>> compilation will complete and Ruby will run but I receive a lot of
>> warnings about pointer targets differing in signedness. (Warning
>> messages at bottom of message.)
>>
>> Should these warnings concern me? Do they indicate that my Ruby build
>> will have problems (like segmentation faults)? Is there any way I can
>> fix the warnings?
>>
>> Thank you,
>> Ben
>>
>> re.c: In function _memsearchre.c:121: warning: pointer targets in
>> passing argument 1 of _memcicmpiffer in signedness
>> re.c:121: warning: pointer targets in passing argument 2 of
>> _memcicmpiffer in signedness
>> re.c:129: warning: pointer targets in passing argument 1 of
>> _memcicmpiffer in signedness
[snip]