From: Yukihiro Matsumoto <matz@...>
Date: 2006-04-06T18:11:02+09:00
Subject: Re: Pointer Signedness Errors When Compiling 1.8.4

Hi,

In message "Re: Pointer Signedness Errors When Compiling 1.8.4"
    on Thu, 6 Apr 2006 04:04:54 +0900, Ben Gribaudo <rubytalk@bengribaudo.com> writes:

|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?

It's not related to your segmentation fault.  gcc 4.x starts to give
you those warnings unlike prior versions.

							matz.