Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Tim McIntosh
On Mar 30, 2008, at 5:31 PM, David Ayers wrote: Tim McIntosh schrieb: GNUstep seems to do a lot of mucking with the runtime structures that are no longer visible with Obj-C 2.0, so I think the changes I made were just barely scratching the surface in view of what is actually needed. Not be

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread David Ayers
Tim McIntosh schrieb: > GNUstep seems to do a lot of mucking with the runtime structures that > are no longer visible with Obj-C 2.0, so I think the changes I made were > just barely scratching the surface in view of what is actually needed. > Not being familiar enough with the GNUstep code base,

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Nicola Pero
The right fix still seems to be to update the Apple runtime code in gnustep-base to work with the new runtime if available, but in the meanwhile if we add the -Wno-deprecated flag, we should probably add it inside gnustep-base so that when support for the new runtime is available, we can

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Tim McIntosh
On Mar 30, 2008, at 9:27 AM, Nicola Pero wrote: The right fix still seems to be to update the Apple runtime code in gnustep-base to work with the new runtime if available, but in the meanwhile if we add the -Wno-deprecated flag, we should probably add it inside gnustep-base so that when sup

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Blake Nicholson
On Mar 30, 2008, at 10:27 AM, Nicola Pero wrote: On 30 Mar 2008, at 14:55, Blake Nicholson wrote: Nicola, Unfortunately, I think the sample output I sent was not a good representation. Sorry about that. I went ahead and built base under apple-apple-apple and redirected stderr to a file.

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Nicola Pero
On 30 Mar 2008, at 14:55, Blake Nicholson wrote: Nicola, Unfortunately, I think the sample output I sent was not a good representation. Sorry about that. I went ahead and built base under apple-apple-apple and redirected stderr to a file. I've attached the file so you can see all the

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-29 Thread Nicola Pero
PROTECTED]> Date: March 18, 2008 4:00:28 PM GMT-04:00 To: gnustep-dev@gnu.org Subject: PATCH: suppress deprecation warnings on OS X Leopard The following patch modifies target.make so that it adds the compiler option -Wno-deprecated-declarations when compiling GNUstep on Mac OS X 10.5 (Leo

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-24 Thread Blake Nicholson
in forwarded message: From: Blake Nicholson <[EMAIL PROTECTED]> Date: March 18, 2008 4:00:28 PM GMT-04:00 To: gnustep-dev@gnu.org Subject: PATCH: suppress deprecation warnings on OS X Leopard The following patch modifies target.make so that it adds the compiler option -Wno-deprecated-declar

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-24 Thread Nicola Pero
ecision on whether to add this to their relevant makefiles? 2) Is INTERNAL_OBJCFLAGS the correct variable to which this compiler setting should be added? Thanks, Blake Begin forwarded message: From: Blake Nicholson <[EMAIL PROTECTED]> Date: March 18, 2008 4:00:28 PM GMT-04:00 To: gnustep-d

Fwd: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-22 Thread Blake Nicholson
heir relevant makefiles? 2) Is INTERNAL_OBJCFLAGS the correct variable to which this compiler setting should be added? Thanks, Blake Begin forwarded message: From: Blake Nicholson <[EMAIL PROTECTED]> Date: March 18, 2008 4:00:28 PM GMT-04:00 To: gnustep-dev@gnu.org Subject: PATCH: suppress

PATCH: suppress deprecation warnings on OS X Leopard

2008-03-18 Thread Blake Nicholson
The following patch modifies target.make so that it adds the compiler option -Wno-deprecated-declarations when compiling GNUstep on Mac OS X 10.5 (Leopard) using Apple's GCC. Is this kind of wholesale disabling of warnings okay, or should this be done on an individual GNUmakefile level?