Re: macosx notes

[dyfet]

I have it compile the internal replacement function in file.cpp for the 
macosx target.  This got around that problem.  I also modified reconfig 
so that it would use glibtoolize if it finds it, rather than making the 
symlink.  I created a new macro, "MACOSX", based on __APPLE__ and 
__MACH__ being defined so that I could easily do other macosx specific 
changes easily.  This was done in the -rRELEASE1 tree, and that tree now 
does compile cleanly on macosx...

I will have to look at the sem_ stuff next...maybe then at least the 
ccgnu2 linked stuff will then execute.

Ian Gough wrote:

> Odd. I had all sorts of problems getting the ccgnu2 lib to compile for
> OS X, but I have not tried the code base lately. What I found was that
> the Mac did not have sem_init or sem_destroy, so I substituted the named
> semaphore variants sem_open and sem_close, choosing pseudorandom names.
>
> On the mac, there is a version of libtool installed, but it is called
> glibtool. That is the one I used. Just created a symlink from libtool to
> glibtool.
>
> I am surprised that you didn't run into a problem with not being able to
> find the signature for the lockf() function too. On my system, there
> isn't any signature in any header in /usr/include.
>
> I haven't attempted to build the ext lib.
>
>  
>
> > -----Original Message-----
> > From: 
> > address@hidden 
> > [mailto:address@hidden
> > org] On Behalf Of Federico Montesino Pouzols
> > Sent: Wednesday, March 26, 2003 11:53 AM
> > To: dyfet
> > Cc: address@hidden; address@hidden
> > Subject: Re: macosx notes
> >
> >
> >
> > 	I have found in my mailbox of cc++ bugs still to be 
> > fixed that sem_init does not work on macosx, which could 
> > explain the freezes. Ian Gough, who has been testing cc++ on 
> > macosx may have some comments, since I believe he was able to 
> > get cc++ working after some hacks...
> >
> >         An yes, I have not seen these kind of problems on FreeBSD.
> >
> > On Wed, Mar 26, 2003 at 11:21:22AM -0500, dyfet wrote:
> >    
> >
> > > Curiously, with a relativily few simple changes I can get 
> > >      
> > reconfig to
> >    
> >
> > > work and (r1 based) common c++ to compile on macosx with a 
> > >      
> > configure 
> >    
> >
> > > script and libtool built from macosx's distribution of libtool, 
> > > autoconf, and automake.
> > >
> > > However, I have yet to get a demo or test to actually work 
> > >      
> > on the test
> >    
> >
> > > machine in question, at least from the build directory.  
> > >      
> > Anything that 
> >    
> >
> > > is linked through ccext2 (including the simple digest test 
> > >      
> > app) appears 
> >    
> >
> > > to segfault in the dynamic linker while loading/resolving 
> > >      
> > the image.  
> >    
> >
> > > Things that use just ccgnu2 just freeze...most curious, 
> > >      
> > since the last 
> >    
> >
> > > time I had tested under FreeBSD (which is somewhat related), it 
> > > generally worked very well there...
> > >
> > >      
> > >
> > > > > > >      
> > > > > > >
> > > > > > >              
> > _______________________________________________
> > Bug-commoncpp mailing list
> > address@hidden 
> > http://mail.gnu.org/mailman/listinfo/bug-> commoncpp
> >
> >    
>
>