Re: [GENERAL] Can't Build 7.3.4 on OS X
Eric Ridge [EMAIL PROTECTED] writes: I don't think the OS X 10.3 betas are readily available (I've payed to be in Apple's developer program), so if you don't have access to 10.3 but have some idea as to what would cause this problem with tas, I'll do whatever I can to help test. I have verified that CVS tip builds okay on 10.3 beta. I would recommend dropping the CVS-tip versions of s_lock.h and s_lock.c into the 7.3 source tree if you need to get 7.3 working on 10.3. regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Can't Build 7.3.4 on OS X
On Sep 27, 2003, at 3:43 PM, Tom Lane wrote: Eric Ridge [EMAIL PROTECTED] writes: I don't think the OS X 10.3 betas are readily available (I've payed to be in Apple's developer program), so if you don't have access to 10.3 but have some idea as to what would cause this problem with tas, I'll do whatever I can to help test. I have verified that CVS tip builds okay on 10.3 beta. I would recommend dropping the CVS-tip versions of s_lock.h and s_lock.c into the 7.3 source tree if you need to get 7.3 working on 10.3. Using s_lock.c and .h from at least 7.4 works too. Were you ever able to figure out why 7.3.4 wouldn't build? eric ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Can't Build 7.3.4 on OS X
Eric B. Ridge [EMAIL PROTECTED] writes: Were you ever able to figure out why 7.3.4 wouldn't build? Didn't really look, since the 7.4 inlined version of TAS is a better solution anyway. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Can't Build 7.3.4 on OS X
Eric B.Ridge wrote: On Sep 27, 2003, at 3:43 PM, Tom Lane wrote: Eric Ridge [EMAIL PROTECTED] writes: I don't think the OS X 10.3 betas are readily available (I've payed to be in Apple's developer program), so if you don't have access to 10.3 but have some idea as to what would cause this problem with tas, I'll do whatever I can to help test. I have verified that CVS tip builds okay on 10.3 beta. I would recommend dropping the CVS-tip versions of s_lock.h and s_lock.c into the 7.3 source tree if you need to get 7.3 working on 10.3. Using s_lock.c and .h from at least 7.4 works too. Were you ever able to figure out why 7.3.4 wouldn't build? eric ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings if you execute 'select_gcc 3.1' as root it should change your default GCC to a compiler that works. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [GENERAL] Can't Build 7.3.4 on OS X
if you execute 'select_gcc 3.1' as root it should change your default GCC to a compiler that works. That fixes the problems with -traditional-cpp v/s -no-cpp-precomp, but it doesn't fix: ld: Undefined symbol _tas eric ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Can't Build 7.3.4 on OS X
On Sep 27, 2003, at 7:41 PM, Tom Lane wrote: I'm not sure whether we are planning another 7.3 release or not. I'd like to push forward to a 7.4 release, myself. Do you have any idea when OS X 10.3 will be released? If it's further out than next month, we could probably plan that 7.4 will win the footrace. By no means is this official, cuz well, I ain't in the loop, but I recently read something about mid-late November. I suspect they'll want it out by the time all the G5's are shipped... and the 2x2gig started shipping on friday... well, at least mine did. eric ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] Can't Build 7.3.4 on OS X
On Sep 21, 2003, at 9:03 PM, Tom Lane wrote: That makes no sense at all --- AFAICT there were *no* darwin or ppc specific changes between 7.3.2 and 7.3.4. Can you double check? Not really knowing what I'm doing, I took s_lock.c and s_lock.h from 7.4beta3, copied 'em into the 7.3.4 src tree, and recompiled. Surprisingly, everything compiled and 7.3.4 seems to be running okay (I haven't run the regression tests or tried to stress test it yet). I'm not sure this contributes to this thread in a meaningful way, but I thought it was worth mentioning. eric ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [GENERAL] Can't Build 7.3.4 on OS X
On Sep 21, 2003, at 3:11 PM, Tom Lane wrote: BTW, is anyone interested in looking into whether we can be made to build without using either flag? I tried it and saw a number of I did this... before I knew about -no-cpp-precomp. :( I read all about -traditional-cpp in the gcc man page, but could never find the corresponding not traditional cpp flag. It boiled down to two things: use of macros that used the stringification syntax, and whitespace around marco arguments. Take src/include/nodes/nodes.h, around line 265 for example: #define makeNode(_type_) ((_type_ *) newNode(sizeof(_type_),T_#_type_)) ... #define IsA(nodeptr, _type_) (nodeTag(nodeptr) == T_#_type_) gcc 3.3 just didn't like this. So I had to fake it out: #define T_UNDER() T_ #define makeNode(_type_) ((_type_ *) newNode(sizeof(_type_),T_UNDER()_type_)) ... #define IsA(nodeptr,_type_) (nodeTag(nodeptr) == T_UNDER()_type_) But it gets better. Apparently with gcc 3.3 whitespace around macro arguments is preserved! So, in the case of calls to (at least) the IsA macro: before: if (IsA(foo, Short)) after: if (IsA(foo,Short)) ^- no space! From what I could tell, the statement would be expanded into (using my re-defined version above): if (nodeTag(nodeptr) == T_ Short) which of course isn't legal syntax b/c of the space. So I went through with some Perl and did a bunch of global substitutions on the files that gcc complained about. There were a few more than the above examples, but not too many. too. It would be interesting to understand what the problem is. There it is. eric ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] Can't Build 7.3.4 on OS X
Hunter Hillegas [EMAIL PROTECTED] writes: I cannot build the latest release on OS X Jaguar. Running GCC 3.3 from Apple: It seems -traditional-cpp has become nontraditional in 3.3. Or possibly Apple changed their system header files in a way that broke that preprocessor. What's certain is that gcc 3.3 rejects some of the Darwin header files when using -traditional-cpp. This is not our fault ;-). It seems to work okay if you change -traditional-cpp to -no-cpp-precomp in src/template/darwin (you will need to rerun configure afterwards). Experimenting, I find that Apple's gcc 3.1 and 3.3 both build PG fine with that switch. Their latest update of gcc 2.95 no longer seems to work at all (it generates invalid assembler code for xlog.c). I tried removing the cpp option entirely, but that blew up in other places, and I have no interest in figuring out why just now. Is anyone on the list still running OS X 10.1, or anyway still using a version of the OS X developer tools older than the Dec 2002 release? It would be good to check if -no-cpp-precomp creates any problems on any release that anyone still cares about. For the moment, I've made src/template/darwin unconditionally use -no-cpp-precomp, but we could probably hack it to use -traditional-cpp if there's still any interest in Darwin compiler versions that don't recognize -no-cpp-precomp. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Can't Build 7.3.4 on OS X
Is there an easy way to remove 'traditional-cpp' from the whole build? See src/template/darwin. Whatever change is needed, it probably will be in that file or src/makefiles/Makefile.darwin (or possibly src/include/port/darwin.h). Let us know what you find out ... BTW: the template file is an input to configure, so you must rerun configure if you change it. The other two files are live, you can just edit 'em and rebuild. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Can't Build 7.3.4 on OS X
Hunter Hillegas [EMAIL PROTECTED] writes: Jaguar 10.2.6. Okay, I think I was still on 10.2.4. I won't be able to try 10.2.6 till my laptop gets fixed. Is there an easy way to remove 'traditional-cpp' from the whole build? See src/template/darwin. Whatever change is needed, it probably will be in that file or src/makefiles/Makefile.darwin (or possibly src/include/port/darwin.h). Let us know what you find out ... regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Can't Build 7.3.4 on OS X
Jaguar 10.2.6. The differences is most likely the latest compilers, GCC 3.3 from Apple. You can get them from their developer site. Supposedly the new compiler generates MUCH better PPC code, so I was hoping to use it. Is there an easy way to remove 'traditional-cpp' from the whole build? Thanks, Hunter From: Tom Lane [EMAIL PROTECTED] Date: Mon, 28 Jul 2003 01:40:50 -0400 To: Hunter Hillegas [EMAIL PROTECTED] Cc: PostgreSQL [EMAIL PROTECTED] Subject: Re: [GENERAL] Can't Build 7.3.4 on OS X Hmph. It builds just fine on OS X for me, or at least it did last week (my Mac laptop is now in the shop, sob). Which OS X release have you got, exactly? Does it help if you take out -traditional-cpp ? regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
