From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Shoaib Mir <shoaibmir(at)gmail(dot)com>, DEV <dev(at)umpa-us(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] WIN32 Build? |
Date: | 2006-08-09 21:44:04 |
Message-ID: | 29671.1155159844@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
[ redirecting to -hackers, as this seems utterly off-topic for -general ]
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Shoaib Mir wrote:
>> If you remove "inline" the build process goes fine and if you dont, it first
>> gives a few warning and in the end quits the build process with a fatal
>> error.
> OK, good to know. If we ever find a symbol that is defined for that
> compiler that we can test, we can fix this.
If we were running the actual configure script, presumably it would
figure out that "inline" doesn't work on this compiler. I suppose the
problem here is that there's 0 chance of that in a pure-Microsoft
build environment. Should we just dumb pg_config.h.win32 down to the
lowest common denominator, and make it #define inline as empty for any
Windows build environment that can't run configure? I don't think we
care that much about inline-ing on the client side anyway.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Reece Hart | 2006-08-09 22:13:25 | Re: Tuning to speed select |
Previous Message | Shoaib Mir | 2006-08-09 21:31:58 | Re: WIN32 Build? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-08-09 21:51:14 | Re: Buildfarm failure on ecpg/test/pgtypeslib |
Previous Message | Shoaib Mir | 2006-08-09 21:31:58 | Re: WIN32 Build? |