Re: [patch #4206] libobjc: Extend protocol hack to all gcc versions

[Jeremy Bettis]

More Information:

the libobjc in gcc's CVS server doesn't have any implementation in 
thr-win32.c and doesn't build as a dll. (Actually I can't figure how to get 
it to build at all w/o building all of gcc.)

I can't send in the thr-win32.c implementation from gnustep because it's not 
mine.

I can't solve this problem, please commit my patch to gnustep-libobjc, so 
that at least windows users can use Protocols.

----- Original Message ----- 
From: "Richard Frith-Macdonald" <richard@brainstorm.co.uk>
To: "Jeremy Bettis" <jeremy@deadbeef.com>
Cc: "Andrew Pinski" <pinskia@physics.uc.edu>; <bug-gnustep@gnu.org>
Sent: Wednesday, July 27, 2005 11:03 AM
Subject: Re: [patch #4206] libobjc: Extend protocol hack to all gcc versions


> On 2005-07-27 13:48:48 +0100 Jeremy Bettis <jeremy@deadbeef.com> wrote:
>
> > Why is this my problem.
> >
> > Look at 
> > http://wwwmain.gnustep.org/resources/downloads.php?site=http%3A%2F%2Fftpmain.gnustep.org%2Fpub%2Fgnustep%2F
> > Notice how it has listed libobjc as prereq on windows.
> > See the link to 
> > http://ftpmain.gnustep.org/pub/gnustep/libs/gnustep-objc-1.3.0.tar.gz
> > Notice how that is NOT GCC's libobjc.
> > See my patch to that code.
> >
> > I don't really care what libobjc GCC has because I have to use gnustep's.
> >
> > Feel free to fix any of the steps that got us to this point, but don't 
> > tell me that I am not using the right software when I followed the 
> > published instructions.
>
> Stay calm ...
>
> Andrew is familiar with gcc, but not windows, you are familiar with 
> building GNUstep on windows, and neither of you know each others 
> background ... you just have two different viewpoints and I'm sure there 
> is no intention on either part to be awkward.
>
> As far as I know (and I could be wrong on this) ... the libobjc provided 
> in the GNUstep CVS is a version which has been hacked to build nicely on 
> windows export the symbols windows needs in the way it needs them etc (I 
> don't know the details), but the mainline libobjc in the gcc project lacks 
> these modifications.  On the other hand, the gcc version has various 
> bugfixes which are not in the version on gnustep cvs.
>
> If this is not the case ... and the main gcc version of the library is 
> fine on windows, then the instructions we have for running gnustep on 
> windows are out of date ... and it would be good to know that so we can 
> change them.
>
> If it is the case, the pair of you could do everyone a favour by finding 
> out what needs to be done to the main gcc version of the library to make 
> it usable with gnustep under windows, and get the changes into the main 
> version ... so we can remove the library from gnustep cvs.
>
> I'm hoping to see something productive come of this.
>
>
>
> > ----- Original Message ----- From: "Andrew Pinski" 
> > <pinskia@physics.uc.edu>
> > To: "Jeremy Bettis" <jeremy@deadbeef.com>
> > Cc: "Andrew Pinski" <pinskia@physics.uc.edu>; <bug-gnustep@gnu.org>
> > Sent: Tuesday, July 26, 2005 2:42 PM
> > Subject: Re: [patch #4206] libobjc: Extend protocol hack to all gcc 
> > versions
> >
> >
> > > > Gcc has a libobjc also, but the code I patched was from gnustep's CVS
> > > > server, not gcc's.
> > > >
> > > > Let's take one step at a time.
> > >
> > > The GNUstep's libobjc really should be removed now as it does not 
> > > contain
> > > all the fixes which are in the GCC's CVS.  And the libobjc in GCC is 
> > > upstream
> > > so the bug should be submitted there first.  This might turn out to be a
> > > front-end bug if you submit a bug to GCC's bug database.
> > >
> > > -- Pinski