Nabble - PostgreSQL - ports

libpq windows 64bit support

2008-09-29T02:09:13Z

hi,

Is there any plan to support windows 64bit? I tested the latest stable
release but it fails to build (I created my own configuration using
the existing sln).

Cheers,
--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-07-23T14:29:27Z

hi Magnus!

On Tue, May 6, 2008 at 8:01 PM, Magnus Hagander <magnus@...> wrote:
> Pierre Joye wrote:
>> > > We use the last SDK working with VC6 (2003/02). That's sadly a
>> > > requirement for php 5.x. We are working on supporting 2k5 and
>> > > the latest SDK for 5.3+. However VC6 support has to be kept for
>> > > the 5.x branches (at least).
>> >
>> > There's your problem, really. 8.3+ does not support VC6 anymore. We
>> > need 7.1 or newer.

Ok, time for some news :)

We have finally decide of a death sentence for VC6 (php 5.3.x is the
last release to support it). Then only VC9 binaries will be provided
(be 5.4 or 6).

>> I was suspecting this problem. Do you have any experiences of using
>> these 2k5 binaries with VC6 (especially in threaded environment)? We
>> may give it a try in the next weeks and update it again in 5.2.7 and
>> 5.3 if it works well.
>
> It shouldn't be a problem, other than requiring both runtimes to be
> present. Unless you use PQtrace() in which case it will be a big
> problem.
>
> Basically, as long as you don't free() something in one runtime that
> was malloced():d in a nother one, and as long as you don't pass "CRT
> pointers" between the two runtimes, you are fine. And we do pass a CRT
> pointer around in PQtrace, but that's the only case. We used to have a
> problem with some Kerberos structure that was malloced in one place and
> free()d in another, but that has been fixed.

I managed to compile the latest libpq with VC6, it requires only some
minor changes. I describe the procedure here (not asking to merge the
changes but it may help someone reading this list or the archive):

http://wiki.php.net/internals/windows/libs/libpg (should be pq =)

VC8 and VC9 works out of the box except that the command line options
are ignored (I will try to find the cause and report a bug for it).
You made a great work :)

I'm about to update the PHP Snapbox with the new versions, if you know
some pgsql+php Windows users, it would be the right time to test
(online on Monday 28th of July).

Thanks for your fantastic work and help :)

Cheers,
--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

this mailing list is proposed to be retired

2008-07-08T06:01:42Z

Some PostgreSQL mailing lists, including the one you are reading now, are
proposed to be retired, because they receive very little or mostly off-topic
traffic.

If you disagree with this proposal, please make your objections known before
the end of the month. Otherwise we will proceed with this plan.

The current first stage of retirement proposals affects the following lists:

* pgsql-ports

In the future, please post issues to one of the following mailing lists:

- Questions on compiling PostgreSQL to pgsql-general
- Complaints if PostgreSQL does not compile to pgsql-bugs
- Porting PostgreSQL to new platforms to pgsql-hackers

* pgsql-cygwin

In the future, please post issues to another mailing list, as described above
for pgsql-ports.

* pgsql-interfaces

Many PostgreSQL interfaces have their own mailing lists. Posts that don't fit
anywhere else could go to pgsql-general.

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: contrib - fuzzystrmatch installation issue

2008-07-06T14:16:06Z

Tom Lane wrote:

>> psql:fuzzystrmatch.sql:32: ERROR: could not find function "dmetaphone_alt"
>> in file "/usr/lib/pgsql/fuzzystrmatch.so"
>
> I'm suspicious that /usr/lib/pgsql/fuzzystrmatch.so is actually the 7.4
> version of that module (which is what shipped in RHEL4 to begin with,
> and which would've lacked exactly those three functions). However a
> hole in this theory is that an 8.3 server should've refused to load
> a 7.4 extension module at all. Anyway, double check versions,
> installation locations, etc. A self-configured Postgres installation
> would not default to installing into /usr/lib/pgsql, so it certainly
> seems possible that that file isn't your newly built version.

He had also written me directly off list -- version mismatch it was. See
below. I should have thought to copy the list on my reply -- sorry about
that.

Joe

----------------------
Kenaniah Cerny wrote:
> Joe,
>
> You hit the nail right on the head. Apparently, I was trying to use
> Postgres 7.4.x with the 8.1.11 contrib version. Upgrading Postgres to
> 8.1 solved the issue. Can't believe I did that.
>
> Thanks for pointing it out. It would be a great addition to the
> documentation if the contrib functions were labeled with the versions
> that they first appear in the stable distro. It would most definitely
> help out people like me :-/
>
> And sorry for the double-email.
>
> Thanks,
> Kenaniah
>
> On Sat, Jul 5, 2008 at 4:10 PM, Joe Conway <mail@...
> <mailto:mail@...>> wrote:
>
> Kenaniah Cerny wrote:
>
> The compiler didn't return any errors during the build process,
> leaving me clueless as to why it's not working correctly.
>
> If you have any insight, please feel free to shoot me back an
> email or to call me at (951) 385-9506, as it is slightly urgent.
>
>
> I see that you simultaneously wrote to the list, but please do that
> first next time.
>
> You haven't provided enough information to be sure, but it sounds to
> me like you have at least two different versions of Postgres
> installed -- probably both 8.3.3 and 7.4.x. Try doing:
>
> locate fuzzystrmatch.so
>
> In 7.4.x the functions being complained about did not exist. You
> could also try doing:
>
>
> psql -d template1 -U postgres
> template1=# select version();
>
> and see what version of postgres you wind up attached to.
>
> Joe
>
>

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: contrib - fuzzystrmatch installation issue

2008-07-06T14:12:11Z

"Kenaniah Cerny" <kenaniah@...> writes:
> I am running Postgres 8.3.3 on a CentOS box and I had a few issues when
> trying to install the fuzzystrmatch library. The library seemed to compile
> and make install correctly, but when I ran the sql scripts to add the
> functions to a database, I came up with this issue:

> # psql -d template1 -U postgres -f fuzzystrmatch.sql
> SET
> CREATE FUNCTION
> CREATE FUNCTION
> CREATE FUNCTION
> CREATE FUNCTION
> psql:fuzzystrmatch.sql:24: ERROR: could not find function "difference" in
> file "/usr/lib/pgsql/fuzzystrmatch.so"
> psql:fuzzystrmatch.sql:28: ERROR: could not find function "dmetaphone" in
> file "/usr/lib/pgsql/fuzzystrmatch.so"
> psql:fuzzystrmatch.sql:32: ERROR: could not find function "dmetaphone_alt"
> in file "/usr/lib/pgsql/fuzzystrmatch.so"

I'm suspicious that /usr/lib/pgsql/fuzzystrmatch.so is actually the 7.4
version of that module (which is what shipped in RHEL4 to begin with,
and which would've lacked exactly those three functions). However a
hole in this theory is that an 8.3 server should've refused to load
a 7.4 extension module at all. Anyway, double check versions,
installation locations, etc. A self-configured Postgres installation
would not default to installing into /usr/lib/pgsql, so it certainly
seems possible that that file isn't your newly built version.

Another thing that seems pretty odd is that the above complains about
difference(), which *is* present in the .so according to nm.

BTW, why are you compiling fuzzystrmatch for yourself at all, instead
of just installing the postgresql-contrib RPM?

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-07-04T19:56:46Z

Tom Lane wrote:
> > When I blow away /sw/bin/awk, so that make uses /usr/bin/awk instead,
> > I get a make that executes perfectly and a make check with "All 114
> > tests passed."
>
> <spock>Fascinating.</spock>

OK, that wins the most creative tag award from me.

--
Bruce Momjian <bruce@...> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

contrib - fuzzystrmatch installation issue

2008-07-04T18:31:49Z

Hi everyone,

I am running Postgres 8.3.3 on a CentOS box and I had a few issues when trying to install the fuzzystrmatch library. The library seemed to compile and make install correctly, but when I ran the sql scripts to add the functions to a database, I came up with this issue:

# psql -d template1 -U postgres -f fuzzystrmatch.sql
SET
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
psql:fuzzystrmatch.sql:24: ERROR: could not find function "difference" in file "/usr/lib/pgsql/fuzzystrmatch.so"
psql:fuzzystrmatch.sql:28: ERROR: could not find function "dmetaphone" in file "/usr/lib/pgsql/fuzzystrmatch.so"
psql:fuzzystrmatch.sql:32: ERROR: could not find function "dmetaphone_alt" in file "/usr/lib/pgsql/fuzzystrmatch.so"

Apparently, these three functions did not compile into the module. I'm not much of a C/C++ programmer, but according to the Makefile, both object files were included in the resulting fuzzystrmatch shared object, and the three functions in question where definitely present in fuzzystrmatch.c to begin with.

The following is a list of symbols inside the shared object:

# nm libfuzzystrmatch.so
00002ee4 A __bss_start
00000938 t call_gmon_start
00002ec4 D _codes
00002ee4 b completed.1
00002d7c d __CTOR_END__
00002d78 d __CTOR_LIST__
         U __ctype_b_loc@@GLIBC_2.3
         U __ctype_toupper_loc@@GLIBC_2.3
         U CurrentMemoryContext
         w __cxa_finalize@@GLIBC_2.1.3
00001a64 T difference
         U DirectFunctionCall1
00001ae8 t __do_global_ctors_aux
0000095c t __do_global_dtors_aux
00002ebc d __dso_handle
00002d84 d __DTOR_END__
00002d80 d __DTOR_LIST__
00002d8c A _DYNAMIC
00002ee4 A _edata
         U elog_finish
         U elog_start
00002ee8 A _end
         U errcode
         U errfinish
         U errmsg
         U errstart
00001b18 T _fini
000009b8 t frame_dummy
00001d74 r __FRAME_END__
00001bd4 r __func__.2
00001ca4 r __func__.3
00001bc4 r __func__.5
00002e78 A _GLOBAL_OFFSET_TABLE_
         w __gmon_start__
00000830 T _init
00002d88 d __JCR_END__
00002d88 d __JCR_LIST__
         w _Jv_RegisterClasses
00000f7e t .L1027
000011d7 t .L1034
00001340 t .L110
000012f5 t .L180
000013a8 t .L185
00000d8f t .L208
00000eac t .L253
00001132 t .L254
00001096 t .L266
0000102d t .L392
00000e27 t .L487
00000f90 t .L667
00000f1d t .L760
0000105e t .L774
00000f40 t .L785
0000117f t .L789
00000d55 t .L83
000012a4 t .L874
0000116a t .L930
000011fe t .L932
00000f5c t .L977
000013c7 t .L98
00001251 t .L982
00000a24 T levenshtein
00000bf4 T Lookahead
         U MemoryContextAlloc
000016ac T metaphone
00000c24 T _metaphone
00001cb4 r my_finfo.0
00001cb0 r my_finfo.1
00001bd0 r my_finfo.4
00001bc0 r my_finfo.6
00002ec0 d p.0
         U pg_detoast_datum
00001a4c T pg_finfo_difference
00000a0c T pg_finfo_levenshtein
00000bdc T pg_finfo_metaphone
000018f8 T pg_finfo_soundex
00001bac r Pg_magic_data.7
000009f4 T Pg_magic_func
00001a00 T soundex
00001910 t _soundex
00002ee0 d soundex_table
         U textin
         U textout

The compiler didn't return any errors during the build process, leaving me clueless as to why it's not working correctly. Any help would be greatly appreciated.

Thanks,
Kenaniah Cerny

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-07-03T08:56:44Z

On Wed, Jul 2, 2008 at 10:11 AM, Randall Lucas <rlucas@...> wrote:

> On Tue, Jul 1, 2008 at 7:50 PM, Tom Lane <tgl@...> wrote:
>
>> I believe the most likely theory is that your copy of /sw/bin/awk
>> got corrupted during the transfer from your old machine, and the
>> second most likely theory is that the executable is bitwise the same
>> but it doesn't play nice with the system libraries on your new box,
>> and the third is that there was something wrong with that specific
>> Fink-port build (though if so, it should have failed on your old
>> machine too). In any case it sounds like a very local problem.
>
>
> I will try compiling 8.3.3 (and testing gawk) on my old 10.4 Intel Mac
> which was the source of the gawk binary. I'll also report if the
> binary is bitwise identical. No reply solicited for that; I just want
> to keep it all in the same thread for archival / search engine
> purposes.

$ /sw/bin/awk -W version
GNU Awk 3.1.5

Confirming that reinstalling Fink de novo on OS X 10.5 gives me a
properly working gawk.

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-07-02T10:11:18Z

On Tue, Jul 1, 2008 at 7:50 PM, Tom Lane <tgl@...> wrote:
> "Randall Lucas" <rlucas@...> writes:
>> I dug in a bit more. It turns out that the Apple process of
>> transferring my data over from my old box transferred my
>> Fink-installed UNIX apps, including PostgreSQL 8.1.
>
> And the contents of /sw/bin, no doubt?

Yes. Although, I'd been doing UNIX-y things for the past couple weeks
and nothing seemed broken, which makes this problem more pernicious.

> Given that we've never heard the like from anyone else, I think that
> (1) accusations against the upstream gawk maintainers seem misplaced,

Naturally; my incredulity at the brokenness of gawk didn't come
through, I guess ;)

> I believe the most likely theory is that your copy of /sw/bin/awk
> got corrupted during the transfer from your old machine, and the
> second most likely theory is that the executable is bitwise the same
> but it doesn't play nice with the system libraries on your new box,
> and the third is that there was something wrong with that specific
> Fink-port build (though if so, it should have failed on your old
> machine too). In any case it sounds like a very local problem.

I like this last theory best. It is somewhat surprising to me that
more folks haven't hollered about it, given the ubiquity (?) of
upgrades to 10.5 from people who had installed Fink on 10.4.

I will try compiling 8.3.3 (and testing gawk) on my old 10.4 Intel Mac
which was the source of the gawk binary. I'll also report if the
binary is bitwise identical. No reply solicited for that; I just want
to keep it all in the same thread for archival / search engine
purposes.

Thanks again,

Randall

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-07-01T19:50:36Z

"Randall Lucas" <rlucas@...> writes:
> I dug in a bit more. It turns out that the Apple process of
> transferring my data over from my old box transferred my
> Fink-installed UNIX apps, including PostgreSQL 8.1.

And the contents of /sw/bin, no doubt?

> When I blow away /sw/bin/awk, so that make uses /usr/bin/awk instead,
> I get a make that executes perfectly and a make check with "All 114
> tests passed."

<spock>Fascinating.</spock>

> Comments are most welcome here before I move over to the GNU awk list
> and start accusing pretty much the oldest program in existence of
> being broken ...

Given that we've never heard the like from anyone else, I think that
(1) accusations against the upstream gawk maintainers seem misplaced,
and (2) there's not anything wrong with that Makefile item either.

I believe the most likely theory is that your copy of /sw/bin/awk
got corrupted during the transfer from your old machine, and the
second most likely theory is that the executable is bitwise the same
but it doesn't play nice with the system libraries on your new box,
and the third is that there was something wrong with that specific
Fink-port build (though if so, it should have failed on your old
machine too). In any case it sounds like a very local problem.

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-07-01T15:36:12Z

On Fri, Jun 27, 2008 at 7:58 PM, Tom Lane <tgl@...> wrote:
>
> I'm thinking maybe you have old or broken PG shared libraries
> in that directory that're messing up the link.

Thanks for having a look. As you'll see below, that was a red
herring. Apologies for the long email, but I want to include as much
search-engine bait as possible for folks with the same problem.

I dug in a bit more. It turns out that the Apple process of
transferring my data over from my old box transferred my
Fink-installed UNIX apps, including PostgreSQL 8.1. So I *do* have an
old set of libraries installed in /sw/lib/postgresql-8.1

I manually went into src/Makefile.global and changed LDFLAGS (the
source of the duplicate "-L/sw/lib" entry) to blank. (I couldn't seem
to get configure to do so.)

The result is below. No more -L/sw/lib in the gcc command line that
barfs, but the same error message comes out:

gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith
-Winline -Wdeclaration-after-statement -Wendif-labels
-fno-strict-aliasing -fwrapv -dynamiclib -install_name
/usr/local/pgsql-8.3/lib/libecpg.6.dylib -compatibility_version 6
-current_version 6.0 -exported_symbols_list exports.list
-multiply_defined suppress execute.o typename.o descriptor.o data.o
error.o prepare.o memory.o connect.o misc.o path.o pgstrcasecmp.o
thread.o -L../pgtypeslib -L../../../../src/interfaces/libpq
-L../../../../src/port -lpgtypes -lpq -lm -o libecpg.6.0.dylib
Undefined symbols:
"_PGTYPESdate_from_asc", referenced from:
_ecpg_get_data in data.o
_ecpg_get_data in data.o
"_PQfinish", referenced from:
_ecpg_finish in connect.o
"_PQsetdbLogin", referenced from:
_ECPGconnect in connect.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[4]: *** [libecpg.6.0.dylib] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2

So then I started digging in and poking around the actual makefiles.
It looks like the symbols that data.c is referencing come from
src/interfaces/ecpg/pgtypeslib

The file exports.list in src/interfaces/ecpg/pgtypeslib does NOT
contain the missing symbol _PGTYPESdate_from_asc

I checked the output of make, and this line caught my eye:

awk '/^[^#]/ {printf "_%s\n",$1}' exports.txt >exports.list

This should be dumping out any the first word of any line that doesn't
start with a # to exports.list, prepended with "_", right?

Well, as it turns out, lines 1-2 of exports.txt are comments, and
lines 3-11 look like:

PGTYPESdate_dayofweek 1
PGTYPESdate_defmt_asc 2
PGTYPESdate_fmt_asc 3
PGTYPESdate_free 4
PGTYPESdate_from_asc 5
PGTYPESdate_from_timestamp 6
PGTYPESdate_julmdy 7
PGTYPESdate_mdyjul 8
PGTYPESdate_new 9

(Note the presence of our missing symbol, date_from_asc)

All of these first nine symbols are missing from my copy of
exports.list! (The rest of the symbols, 10-n, appear fine.)

Sure enough, one of the other offenders -- PQfinish -- is present in
the first nine symbols in src/interfaces/libpq/exports.txt but missing
from src/interfaces/libpq/exports.list

Could it be that my awk is buggy or not playing nice?

$ which awk
/sw/bin/awk
$ ls -al /sw/bin/awk
lrwxr-xr-x 1 root admin 4 Jun 19 18:50 /sw/bin/awk -> gawk
$ awk -W version
GNU Awk 3.1.4

I also have a system awk in /usr/bin/awk, but my $PATH (using standard
Fink init.sh practice of prepending) puts /sw/bin first.

It appears that PG knows that I have gawk:

$ grep 'awk' config.log
configure:5084: checking for gawk
configure:5100: found /sw/bin/gawk
configure:5110: result: gawk
ac_cv_prog_AWK=gawk
AWK='gawk'

When I blow away /sw/bin/awk, so that make uses /usr/bin/awk instead,
I get a make that executes perfectly and a make check with "All 114
tests passed."

So, at least for now, my problem is solved. But I remain very much
puzzled. Does anyone here know if my gawk is behaving properly? (I
tried it with both --compat and --posix flags to see if that fixed the
behavior; no effect.) And if it is, and PG knows that gawk behaves
that way and detected it, shouldn't the PG makefile have adapted its
awk invocation to use the gawk syntax?

Comments are most welcome here before I move over to the GNU awk list
and start accusing pretty much the oldest program in existence of
being broken ...

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-06-27T19:58:04Z

"Randall Lucas" <rlucas@...> writes:

> gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith
> -Winline -Wdeclaration-after-statement -Wendif-labels
> -fno-strict-aliasing -fwrapv -dynamiclib -install_name
> /usr/local/pgsql-8.3/lib/libecpg.6.dylib -compatibility_version 6
> -current_version 6.0 -exported_symbols_list exports.list
> -multiply_defined suppress execute.o typename.o descriptor.o data.o
> error.o prepare.o memory.o connect.o misc.o path.o pgstrcasecmp.o
> thread.o -L../pgtypeslib -L../../../../src/interfaces/libpq
> -L../../../../src/port -L/sw/lib -L/sw/lib -lpgtypes -lpq -lm -o
> libecpg.6.0.dylib
> Undefined symbols:

Comparing this to a fresh build log on my own machine, the only obvious
difference is the (duplicated) -L/sw/lib that your log has and mine
doesn't. I'm thinking maybe you have old or broken PG shared libraries
in that directory that're messing up the link. I'm not convinced of
that, because these -L switches are last in the command and so really
shouldn't be determining anything; but it's a place to start looking.

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-06-27T19:45:50Z

"Randall Lucas" <rlucas@...> writes:
> Compiling of PostgreSQL 8.3.3 on Mac OS X 10.5.2 (9C2031) fails with
> the following error.

Weird. It works on the laptop I'm typing on, and there are several OSX
buildfarm machines that aren't complaining either. Are you sure you're
using an up-to-date install of the developer tools? I seem to recall
that it's possible to update, eg, 10.4 to 10.5 without updating your
developer tools, but the tools don't actually work thereafter ...

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: 8.3.3 compile fails on Mac OS X 10.5.2

2008-06-27T17:00:25Z

Just confirmed after make distclean and ./configure that the same
error persists in Mac OS X 10.5.3 (9D34).

Best,

Randall

On Fri, Jun 27, 2008 at 4:08 PM, Randall Lucas <rlucas@...> wrote:

> Compiling of PostgreSQL 8.3.3 on Mac OS X 10.5.2 (9C2031) fails with
> the following error. I got the same error whether I did a "vanilla"
> ./configure or whether I used a variety of --with-X flags (e.g. perl,
> libxslt). The use or non-use of --with-libedit-preferred does not
> change the outcome (as suggested in this blog post:
> http://www.stereoplex.com/two-voices/error-compiling-postgresql-8.3-on-leopard-rl_completion_matches
> )
>
> This is a fairly stock 10.5 machine (quad-core Mac Pro) that I just
> got last week, but I do have developer tools installed on it.
>
> Also, a pending software update is about to require me to reboot. (I
> will post again if the update fixes the issue).
>
> Any suggestions? More info needed?
>
> Error:
>
> gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith
> -Winline -Wdeclaration-after-statement -Wendif-labels
> -fno-strict-aliasing -fwrapv -dynamiclib -install_name
> /usr/local/pgsql-8.3/lib/libecpg.6.dylib -compatibility_version 6
> -current_version 6.0 -exported_symbols_list exports.list
> -multiply_defined suppress execute.o typename.o descriptor.o data.o
> error.o prepare.o memory.o connect.o misc.o path.o pgstrcasecmp.o
> thread.o -L../pgtypeslib -L../../../../src/interfaces/libpq
> -L../../../../src/port -L/sw/lib -L/sw/lib -lpgtypes -lpq -lm -o
> libecpg.6.0.dylib
> Undefined symbols:
> "_PGTYPESdate_from_asc", referenced from:
> _ecpg_get_data in data.o
> _ecpg_get_data in data.o
> "_PQfinish", referenced from:
> _ecpg_finish in connect.o
> "_PQsetdbLogin", referenced from:
> _ECPGconnect in connect.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[4]: *** [libecpg.6.0.dylib] Error 1
> make[3]: *** [all] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [all] Error 2
> make: *** [all] Error 2
>

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Fwd: 8.3.3 compile fails on Mac OS X 10.5.2

2008-06-27T16:08:44Z

Compiling of PostgreSQL 8.3.3 on Mac OS X 10.5.2 (9C2031) fails with
the following error. I got the same error whether I did a "vanilla"
./configure or whether I used a variety of --with-X flags (e.g. perl,
libxslt). The use or non-use of --with-libedit-preferred does not
change the outcome (as suggested in this blog post:
http://www.stereoplex.com/two-voices/error-compiling-postgresql-8.3-on-leopard-rl_completion_matches
)

This is a fairly stock 10.5 machine (quad-core Mac Pro) that I just
got last week, but I do have developer tools installed on it.

Also, a pending software update is about to require me to reboot. (I
will post again if the update fixes the issue).

Any suggestions? More info needed?

Error:

gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith
-Winline -Wdeclaration-after-statement -Wendif-labels
-fno-strict-aliasing -fwrapv -dynamiclib -install_name
/usr/local/pgsql-8.3/lib/libecpg.6.dylib -compatibility_version 6
-current_version 6.0 -exported_symbols_list exports.list
-multiply_defined suppress execute.o typename.o descriptor.o data.o
error.o prepare.o memory.o connect.o misc.o path.o pgstrcasecmp.o
thread.o -L../pgtypeslib -L../../../../src/interfaces/libpq
-L../../../../src/port -L/sw/lib -L/sw/lib -lpgtypes -lpq -lm -o
libecpg.6.0.dylib
Undefined symbols:
"_PGTYPESdate_from_asc", referenced from:
_ecpg_get_data in data.o
_ecpg_get_data in data.o
"_PQfinish", referenced from:
_ecpg_finish in connect.o
"_PQsetdbLogin", referenced from:
_ECPGconnect in connect.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[4]: *** [libecpg.6.0.dylib] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: PGSQL non installer for linux

2008-06-20T11:52:39Z

On Friday 20 June 2008 10:05:54 Tom Lane wrote:
> "Sivaramakrishnan Nageswaran" <sivaramakrishnan.nageswaran@...>
writes:

> > Does pgsql have anything like non-installer for linux i.e tar-gzipped
> > bundle (as is available for linux in the form of zip file) which I can
> > untar /unzip in the target machine? Basically I do not want to use rpm to
> > install as it might fail due to dependency issues.
>
> To be blunt, you're out of your mind. You're going to end up
> reinventing rpm, badly. If an rpm install fails due to dependencies
> it's a good indication that the software wouldn't have worked when
> installed.
>

That said, I believe postgres plus will do this for you. See
http://www.postgresrocks.com for download options.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: PGSQL non installer for linux

2008-06-20T07:05:54Z

"Sivaramakrishnan Nageswaran" <sivaramakrishnan.nageswaran@...> writes:
> Does pgsql have anything like non-installer for linux i.e tar-gzipped bundle
> (as is available for linux in the form of zip file) which I can untar /unzip
> in the target machine? Basically I do not want to use rpm to install as it
> might fail due to dependency issues.

To be blunt, you're out of your mind. You're going to end up
reinventing rpm, badly. If an rpm install fails due to dependencies
it's a good indication that the software wouldn't have worked when
installed.

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

PGSQL non installer for linux

2008-06-20T01:52:24Z

Hi,

Does pgsql have anything like non-installer for linux i.e tar-gzipped bundle (as is available for linux in the form of zip file) which I can untar /unzip in the target machine? Basically I do not want to use rpm to install as it might fail due to dependency issues. So, if I have a custom built (for various flavours and versions of linux) bundle, I can just unbundle the same in a specified directory and start using it. Right now, if I use rpm for installing pgsql, it installs the files in various directories (like in /usr/bin, /var/lib/pgsql etc). Basically I wanted all the libraries, binaries and the database to come under a common parent directory.

Hope I have made sense. Any help is highly appreciated.
Thanks for any help.
Regards
- Siva

Always do right. This will gratify some people and astonish the rest.
- Mark Twain
(Home page: http://rushto_siva.tripod.com)

Compiling table_log and other C-functions on the windows port of 8.3

2008-06-09T23:44:15Z

Can the C-functions oftable_log (http://pgfoundry.org/projects/tablelog/) and/or the exampleC-functions in the postgresql docs be compiled for the windows port ofpg 8.3 using Visual C++ (preferentially VC++ 2008) with the header and library files supplied withthe binary installer? If so, which Visual C++ compiler/linkersettings/switches are needed to produce a dll that can be successfullyloaded by postgresql? It would be good to have this information in thesection on compiler settings for compilation of C-functions in docs 34.9, like there is for othercompilers in 34.9.6.

Thanks,
KP

Re: porting postgrers 8.3 on SCO 5.0.7

2008-06-09T12:43:55Z

"Edmundo Robles L." <erobles@...> writes:
> gmake[4]: Entering directory `/u/erobles/postgresql-8.3.1/src/backend/utils/adt'
> cc -b elf -O -I../../../../src/include -I/usr/local/include -c -o cash.o cash.c
> "cash.c", line 814: error: invalid token: 100ll
> "cash.c", line 814: error: Syntax error before or at: ;

Hmm, seems our buildfarm is lacking machines that won't take that
construct, else we'd have noticed this long ago. These should all
be using the INT64CONST() macro.

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

porting postgrers 8.3 on SCO 5.0.7

2008-06-09T11:55:58Z

Hello there!

I trying to compile postgres 8.3 on SCO Open Server 5.0.7 but i got an error to compile cash.o:

gmake[4]: Entering directory `/u/erobles/postgresql-8.3.1/src/backend/utils/adt'
cc -b elf -O -I../../../../src/include -I/usr/local/include -c -o cash.o cash.c
"cash.c", line 814: error: invalid token: 100ll
"cash.c", line 814: error: Syntax error before or at: ;
"cash.c", line 815: error: invalid token: 100ll
"cash.c", line 815: error: Syntax error before or at: )
"cash.c", line 816: error: invalid token: 100000ll
"cash.c", line 816: error: Syntax error before or at: )
"cash.c", line 817: error: invalid token: 100000000ll
"cash.c", line 817: error: Syntax error before or at: %
"cash.c", line 818: error: invalid token: 100000000000ll
"cash.c", line 818: error: Syntax error before or at: %
"cash.c", line 819: error: invalid token: 100000000000000ll
"cash.c", line 819: error: Syntax error before or at: %
"cash.c", line 820: error: invalid token: 100000000000000000ll
"cash.c", line 820: error: Syntax error before or at: %
gmake[4]: *** [cash.o] Error 1

i image the cause that is because the cast to long long doesn't exist on cc from SCO.
i'll be glad if you could help with that issue.

Regards from MEXICO!!

Ing. Edmundo Robles Lopez.
Analista Programador.

--
Di NO a la pirateria, usa software libre.
Say NO to piracy, use free(dom) software.

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: [DOCS] problem in installing pgsql-8.3.1

2008-05-15T18:49:21Z

Problem is solved.
Problem was in my system clock setting.
Make get into a loop like this when the source files all appeared to have timestamps in the future.

Thank you all very much.

With regards:
Shohorab Hossain

----- Original Message ----
From: shohorab hossain <shohorab23@...>
To: pgsql-docs@...; pgsql-bugs@...; pgsql-ports@...; pgsql-admin@...
Cc: shohorab23@...
Sent: Thursday, May 15, 2008 17:21:30
Subject: [DOCS] problem in installing pgsql-8.3.1

Dear sir/madam,

This is to inform you that I am an oracle database user/administrator. But I am going to join in a company where I have to administrate postgresql database. I am new to this database system. For few days I am trying to install postgresql-8.3.1 in RHEL4. My machine configuration is Intel Pentium IV. I have followed the installation document of postgresql that was included with source distribution.

I am facing the problem during the building step of source. The problem is that when I start building with gmake command, it continuously shows messages in console like ‘checking for …………. yes / no’ and I have waited approximately for 3 hours but it continues. At last I have cancelled the building process.

Please give me your appropriate and valuable solution in this regard. I am eagerly looking forward for your quick reply.

Thanks in advance:
---------------------------
Hopeless
Shohorab

Send instant messages to your online friends http://uk.messenger.yahoo.com

Send instant messages to your online friends http://uk.messenger.yahoo.com

--
Sent via pgsql-docs mailing list (pgsql-docs@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Send instant messages to your online friends http://uk.messenger.yahoo.com

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: [ADMIN] problem in installing pgsql-8.3.1

2008-05-15T09:30:31Z

Hi,

On Thu, 2008-05-15 at 04:21 -0700, shohorab hossain wrote:

> For few days I am trying to install postgresql-8.3.1 in RHEL4. My
> machine configuration is Intel Pentium IV. I have followed the
> installation document of postgresql that was included with source
> distribution.
>
> I am facing the problem during the building step of source. The
> problem is that when I start building with gmake command, it
> continuously shows messages in console like ‘checking for …………. yes /
> no’ and I have waited approximately for 3 hours but it continues. At
> last I have cancelled the building process.

You may want to install prebuilt RPMs. First install this package:

http://yum.pgsqlrpms.org/reporpms/8.3/pgdg-redhat-8.3-4.noarch.rpm

and then install PostgreSQL with yum:

yum install postgresql-server

Regards,
--
Devrim GÜNDÜZ , RHCE
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

signature.asc (196 bytes) Download Attachment

Win32 port: where are .a libraries in 8.3

2008-05-15T07:53:03Z

Hope I'm addressing this to the correct list...

In 8.2 (and earlier, I presume) there are .a libraries useful when developing
and linking with the Mingw C compiler (the MS .lib variety are also there).
The .a libs seem to be missing in the 8.3 install while the MS libraries are
all there.

Is there any way to get them back?

C:\Program Files\PostgreSQL\8.2\lib>ls *.a
2008-03-17 05:23a 55,110 libecpg.a
2008-03-17 05:23a 30,188 libecpg_compat.a
2008-03-17 05:22a 64,178 libpgport.a
2008-03-17 05:23a 57,050 libpgtypes.a
2008-03-17 05:22a 3,510,324 libpostgres.a
2008-03-17 05:22a 98,348 libpq.a

C:\Program Files\PostgreSQL\8.3\lib>ls *.a
File Not Found

I'm using the official Win32 installer downloaded from postgresql.org.

Thanks,
Michael Hipp
Heber Springs, Arkansas, USA

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

problem in installing pgsql-8.3.1

2008-05-15T07:27:01Z

Dear sir/madam,

This is to inform you that I am an oracle database user/administrator. But I am going to join in a company where I have to administrate postgresql database. I am new to this database system. For few days I am trying to install postgresql-8.3.1 in RHEL4. My machine configuration is Intel Pentium IV. I have followed the installation document of postgresql that was included with source distribution.

I am facing the problem during the building step of source. The problem is that when I start building with gmake command, it continuously shows messages in console like ‘checking for …………. yes / no’ and I have waited approximately for 3 hours but it continues. At last I have cancelled the building process.

Please give me your appropriate and valuable solution in this regard. I am eagerly looking forward for your quick reply.

Thanks in advance:
---------------------------
Hopeless
Shohorab

Send instant messages to your online friends http://uk.messenger.yahoo.com

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

i5 OS/400 licensed programs...

2008-05-14T08:30:40Z

Hello All,

Are there any binary ports of Postgres 8.3 or 8.2 for the i5 os/400? As of current we do not have the option to use the AIX/Linux partition on the i5 which leaves only the os/400 side of things.

Thanks in advance...

- Joe

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T11:01:47Z

Pierre Joye wrote:

> > > We use the last SDK working with VC6 (2003/02). That's sadly a
> > > requirement for php 5.x. We are working on supporting 2k5 and
> > > the latest SDK for 5.3+. However VC6 support has to be kept for
> > > the 5.x branches (at least).
> >
> > There's your problem, really. 8.3+ does not support VC6 anymore. We
> > need 7.1 or newer.
>
> I was suspecting this problem. Do you have any experiences of using
> these 2k5 binaries with VC6 (especially in threaded environment)? We
> may give it a try in the next weeks and update it again in 5.2.7 and
> 5.3 if it works well.

It shouldn't be a problem, other than requiring both runtimes to be
present. Unless you use PQtrace() in which case it will be a big
problem.

Basically, as long as you don't free() something in one runtime that
was malloced():d in a nother one, and as long as you don't pass "CRT
pointers" between the two runtimes, you are fine. And we do pass a CRT
pointer around in PQtrace, but that's the only case. We used to have a
problem with some Kerberos structure that was malloced in one place and
free()d in another, but that has been fixed.

//Magnus

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T05:44:31Z

On Tue, May 6, 2008 at 2:36 PM, Magnus Hagander <magnus@...> wrote:

> Pierre Joye wrote:
> > Hi Magnus,
> >
> > On Tue, May 6, 2008 at 1:36 PM, Magnus Hagander <magnus@...>
> > wrote:
> > > Pierre Joye wrote:
> > > > hi,
> > > >
> > > > While trying to update the PHP postgresql extension to 8.3.1, I
> > > > met a couple of issues.
> > > >
> > > > The first was about not using kerberos, the makefile is
> > > > incorrect as an error will be raised when kerberos is used and
> > > > no kerberos is used.
> > >
> > > First of all, what version of MSVC are you building this with? And
> > > what version of the Platform SDK?
> >
> > We use the last SDK working with VC6 (2003/02). That's sadly a
> > requirement for php 5.x. We are working on supporting 2k5 and the
> > latest SDK for 5.3+. However VC6 support has to be kept for the 5.x
> > branches (at least).
>
> There's your problem, really. 8.3+ does not support VC6 anymore. We
> need 7.1 or newer.

I was suspecting this problem. Do you have any experiences of using
these 2k5 binaries with VC6 (especially in threaded environment)? We
may give it a try in the next weeks and update it again in 5.2.7 and
5.3 if it works well.

> > > And third, I'd recommend you try to build it using the "main
> > > method" which is using the tools in src/tools/msvc, and not the
> > > win32.mak method. It's much more complete. You can build "just
> > > libpq" that way as well.
> >
> > I did not know this one, thanks! I will give it tonight.
>
> That one will require Visual Studio 2005...

Ok, that will be usefull for the 2k5 move :)

--
Pierre
http://blog.thepimp.net | http://www.libgd.org

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T05:36:10Z

Pierre Joye wrote:

> Hi Magnus,
>
> On Tue, May 6, 2008 at 1:36 PM, Magnus Hagander <magnus@...>
> wrote:
> > Pierre Joye wrote:
> > > hi,
> > >
> > > While trying to update the PHP postgresql extension to 8.3.1, I
> > > met a couple of issues.
> > >
> > > The first was about not using kerberos, the makefile is
> > > incorrect as an error will be raised when kerberos is used and
> > > no kerberos is used.
> >
> > First of all, what version of MSVC are you building this with? And
> > what version of the Platform SDK?
>
> We use the last SDK working with VC6 (2003/02). That's sadly a
> requirement for php 5.x. We are working on supporting 2k5 and the
> latest SDK for 5.3+. However VC6 support has to be kept for the 5.x
> branches (at least).

There's your problem, really. 8.3+ does not support VC6 anymore. We
need 7.1 or newer.

> > And third, I'd recommend you try to build it using the "main
> > method" which is using the tools in src/tools/msvc, and not the
> > win32.mak method. It's much more complete. You can build "just
> > libpq" that way as well.
>
> I did not know this one, thanks! I will give it tonight.

That one will require Visual Studio 2005...

> > > The last two problems are more tricky. It is about addrinfo and
> > > sockaddr. addrinfo is actually defined on windows and seems to
> > > have the correct order of the structure elements (see the
> > > comment in src/include/getaddrinfo.h). Removing this declaration
> > > seems to work (not tested yet).
> >
> > Again, you seem to be doing *something* wrong here, because it
> > builds perfectly fine for others. :-) Anything "unusual" about your
> > environment, that you would guess?
>
> Besides the museum piece of software that is the 2003's SDK,
> nothing ;)

:-D

//Magnus

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T05:27:36Z

Hi Magnus,

On Tue, May 6, 2008 at 1:36 PM, Magnus Hagander <magnus@...> wrote:

> Pierre Joye wrote:
> > hi,
> >
> > While trying to update the PHP postgresql extension to 8.3.1, I met a
> > couple of issues.
> >
> > The first was about not using kerberos, the makefile is incorrect as
> > an error will be raised when kerberos is used and no kerberos is used.
>
> First of all, what version of MSVC are you building this with? And what
> version of the Platform SDK?

We use the last SDK working with VC6 (2003/02). That's sadly a
requirement for php 5.x. We are working on supporting 2k5 and the
latest SDK for 5.3+. However VC6 support has to be kept for the 5.x
branches (at least).

> Second, is there any particular reason you need to build it yourself,
> instead of using the binaries that we ship already?

Mainly because of VC6, we had many issues in the pasts with builds not
using the exact same crt than PHP.

> And third, I'd recommend you try to build it using the "main method"
> which is using the tools in src/tools/msvc, and not the win32.mak
> method. It's much more complete. You can build "just libpq" that way as
> well.

I did not know this one, thanks! I will give it tonight.

> > The 2nd problem is about Shell32.lib, it is missing in the lib list.
> > It is required for SHGetFolderPath.
>
> That's strange, because if that was so then nobody should be able to
> build it. We should be getting the symbol from shfolder.lib.

I got an unknown symbol "SHGetFolderPath" using win32.mak.

> > The last two problems are more tricky. It is about addrinfo and
> > sockaddr. addrinfo is actually defined on windows and seems to have
> > the correct order of the structure elements (see the comment in
> > src/include/getaddrinfo.h). Removing this declaration seems to work
> > (not tested yet).
>
> Again, you seem to be doing *something* wrong here, because it builds
> perfectly fine for others. :-) Anything "unusual" about your
> environment, that you would guess?

Besides the museum piece of software that is the 2003's SDK, nothing ;)

> (And do try the "real" backend build way instead of win32.mak. Even if
> it doesn't fix your issue, it might help with showing us what actually
> is wrong)

Yes, I will definitively try the "normal" way. It will certainly fix
all the issues. I'll come back to you after my tests.

Thanks for your quick reply and the tips!

--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T04:36:47Z

Pierre Joye wrote:
> hi,
>
> While trying to update the PHP postgresql extension to 8.3.1, I met a
> couple of issues.
>
> The first was about not using kerberos, the makefile is incorrect as
> an error will be raised when kerberos is used and no kerberos is used.

First of all, what version of MSVC are you building this with? And what
version of the Platform SDK?

Second, is there any particular reason you need to build it yourself,
instead of using the binaries that we ship already?

And third, I'd recommend you try to build it using the "main method"
which is using the tools in src/tools/msvc, and not the win32.mak
method. It's much more complete. You can build "just libpq" that way as
well.

> The 2nd problem is about Shell32.lib, it is missing in the lib list.
> It is required for SHGetFolderPath.

That's strange, because if that was so then nobody should be able to
build it. We should be getting the symbol from shfolder.lib.

> The last two problems are more tricky. It is about addrinfo and
> sockaddr. addrinfo is actually defined on windows and seems to have
> the correct order of the structure elements (see the comment in
> src/include/getaddrinfo.h). Removing this declaration seems to work
> (not tested yet).

Again, you seem to be doing *something* wrong here, because it builds
perfectly fine for others. :-) Anything "unusual" about your
environment, that you would guess?

(And do try the "real" backend build way instead of win32.mak. Even if
it doesn't fix your issue, it might help with showing us what actually
is wrong)

//Magnus

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Libpq visual c++ build errors, addrinfo and sockaddr_storage redefinition error

2008-05-06T01:29:02Z

hi,

While trying to update the PHP postgresql extension to 8.3.1, I met a
couple of issues.

The first was about not using kerberos, the makefile is incorrect as
an error will be raised when kerberos is used and no kerberos is used.
I added the following lines to avoid libpath error:

!IFDEF USE_SSL
CPP_PROJ=$(CPP_PROJ) /D USE_SSL
SSL_LIBS=ssleay32.lib libeay32.lib gdi32.lib
SSL_LIBPATH_ARG= /libpath:"$(SSL_LIB_PATH)"
!ENDIF

!IFDEF USE_KFW
CPP_PROJ=$(CPP_PROJ) /D KRB5
KFW_LIBS=krb5_32.lib comerr32.lib gssapi32.lib
KFW_LIBPATH_ARG= /libpath:"$(KFW_LIB_PATH)"
!ENDIF

and use XXX_LIBPATH_ARG in the LINK32_FLAG

The 2nd problem is about Shell32.lib, it is missing in the lib list.
It is required for SHGetFolderPath.

The last two problems are more tricky. It is about addrinfo and
sockaddr. addrinfo is actually defined on windows and seems to have
the correct order of the structure elements (see the comment in
src/include/getaddrinfo.h). Removing this declaration seems to work
(not tested yet).

I'm now trying to figure out the sockaddr_storage redclaration. The
windows struct is different
(http://msdn.microsoft.com/en-us/library/aa917505.aspx) and I'm not
sure it is a good idea to force the related HAVE_* definitions. Does
anyone have an idea about how to fix these two problems? If not, I can
try to fix them and run some tests using PHP, any help welcome as I'm
not a pgsql user (only building php releases and snapshots,
www.php.net/download and snaps.php.net).

The last version of my win32.mak file is available here:

http://pecl2.php.net/downloads/php-windows-builds/source/libpq/win32.mak

Cheers,
--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Compile error: command not found

2008-05-02T12:23:50Z

No need, I got it to run! I followed the directions in the manual on
how to set the environment variables correctly, and after I did that,
presto!

Thanks to everyone who took the time to respond to my problem!

--
Regards,
Nathan Garlington

On Fri, May 2, 2008 at 1:20 PM, Peter Eisentraut <peter_e@...> wrote:

> Nathan Garlington wrote:
> > That did it! Thanks for the help.
> > Now, I'm trying to setup the data cluster, so I use:
> >
> > initdb -D /usr/local/pgsql/data
> >
> > as the postgres user but the shell tells me that the 'initdb' does not
> > exist.
> >
> > I rebooted the computer and tried it again, but still won't work.
>
> Please write to an appropriate mailing list for user support.

--
Regards,
Nathan Garlington

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Compile error: command not found

2008-05-02T10:16:40Z

well, after I unzipped and untarred the source,

I changed dir into the postgres-8.3.1 dir and executed:

$: ./configure

when complete, did

$: gmake

which took a while, and then did

$: gmake install

I did all of this as per the instructions in the pgsql manual for ver.
8.3.1. When the install completed, I was told the postgres was
successfully installed on my system

But if there is a problem with $PATH environment var, it looks like
there are some other instructions I can follow. I will try those in
the meantime.

On Fri, May 2, 2008 at 10:59 AM, Tom Lane <tgl@...> wrote:

> "Nathan Garlington" <garlinto@...> writes:
> > Now, I'm trying to setup the data cluster, so I use:
> > initdb -D /usr/local/pgsql/data
> > as the postgres user but the shell tells me that the 'initdb' does not exist.
>
> Either you forgot the "make install" step, or it installed the programs
> into someplace that isn't in your $PATH.
>
> regards, tom lane
>

--
Regards,
Nathan Garlington

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports

Re: Compile error: command not found

2008-05-02T09:59:06Z

"Nathan Garlington" <garlinto@...> writes:
> Now, I'm trying to setup the data cluster, so I use:
> initdb -D /usr/local/pgsql/data
> as the postgres user but the shell tells me that the 'initdb' does not exist.

Either you forgot the "make install" step, or it installed the programs
into someplace that isn't in your $PATH.

regards, tom lane

--
Sent via pgsql-ports mailing list (pgsql-ports@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ports