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
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)---
TI
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 prob
"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)--
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
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 hav
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 r
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 cou
Marko Karppinen <[EMAIL PROTECTED]> writes:
> On lauantai, syys 20, 2003, at 23:37 Europe/Helsinki, Tom Lane wrote:
>> 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?
> -no-cpp-precomp replaced -traditio
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
hole 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
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 wi
>> 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
13 matches
Mail list logo
