Re: [sqlite] Mac OS X name mangling

2007-12-03 Thread Peter Johnson
On Dec 1, 2007, at 5:08 AM, [EMAIL PROTECTED] wrote: The comment probably should read: "Needed to enable pthread recursive mutexes *on Linux*". The _XOPEN_SOURCE define is needed to fix compile-time problems. If you didn't get a compile-time error, it is probably working. Great, that's the

Re: [sqlite] Mac OS X name mangling

2007-12-01 Thread Joe Wilson
--- [EMAIL PROTECTED] wrote: > Joe Wilson <[EMAIL PROTECTED]> wrote: > > --- [EMAIL PROTECTED] wrote: > > > The comment probably should read: "Needed to enable pthread > > > recursive mutexes *on Linux*". > > > > Or more specifically, on old versions of Linux/GNU LIBC. > > > > Have you seen

Re: [sqlite] Mac OS X name mangling

2007-12-01 Thread drh
Joe Wilson <[EMAIL PROTECTED]> wrote: > --- [EMAIL PROTECTED] wrote: > > The comment probably should read: "Needed to enable pthread > > recursive mutexes *on Linux*". > > Or more specifically, on old versions of Linux/GNU LIBC. > > Have you seen any recent Linux distros that need this macro

Re: [sqlite] Mac OS X name mangling

2007-12-01 Thread Joe Wilson
--- [EMAIL PROTECTED] wrote: > The comment probably should read: "Needed to enable pthread > recursive mutexes *on Linux*". Or more specifically, on old versions of Linux/GNU LIBC. Have you seen any recent Linux distros that need this macro defined? If so, maybe you could define it only for

Re: [sqlite] Mac OS X name mangling

2007-12-01 Thread drh
Peter Johnson <[EMAIL PROTECTED]> wrote: > That's an improvement, using 3.5.3. I have to define __DARWIN__ > instead of __MACOS__ now, but at it least compiles without modifying > any sources. > > (I wonder why the config stuff does set __DARWIN__) > > I still question whether or not I'm

Re: [sqlite] Mac OS X name mangling

2007-11-30 Thread Peter Johnson
That's an improvement, using 3.5.3. I have to define __DARWIN__ instead of __MACOS__ now, but at it least compiles without modifying any sources. (I wonder why the config stuff does set __DARWIN__) I still question whether or not I'm getting a thread safe build though. If I define

Re: [sqlite] Mac OS X name mangling

2007-11-30 Thread Peter Johnson
On Nov 30, 2007, at 1:32 PM, [EMAIL PROTECTED] wrote: Peter Johnson <[EMAIL PROTECTED]> wrote: I'm running into a problem building SQLite 3.5.1 targeting a minimum of Mac OS X 10.3, but building against the 10.4 (Universal) SDK. I think this issue has been addressed in 3.5.3. Have you tried

Re: [sqlite] Mac OS X name mangling

2007-11-30 Thread drh
Peter Johnson <[EMAIL PROTECTED]> wrote: > I'm running into a problem building SQLite 3.5.1 targeting a minimum > of Mac OS X 10.3, but building against the 10.4 (Universal) SDK. I think this issue has been addressed in 3.5.3. Have you tried using the latest sources? -- D. Richard Hipp

[sqlite] Mac OS X name mangling

2007-11-30 Thread Peter Johnson
I'm running into a problem building SQLite 3.5.1 targeting a minimum of Mac OS X 10.3, but building against the 10.4 (Universal) SDK. The problem is that the 10.4 SDK does name mangling on the pthread_join symbol in some cases. Specifically, if the _XOPEN_SOURCE symbol is defined,