Thread: where's the build environment for odbc
How come the configure scripts are not in CVS ? How do I build this thing? -- Dave Cramer 519 939 0336 ICQ # 1467551
> -----Original Message----- > From: Dave Cramer [mailto:pg@fastcrypt.com] > Sent: 29 January 2004 01:55 > To: odbc list > Subject: [ODBC] where's the build environment for odbc > > How come the configure scripts are not in CVS ? > > How do I build this thing? Hi Dave, Instructions for generating configure etc. and building a tarball can be found in the README.unix file: http://gborg.postgresql.org/project/psqlodbc/cvs/co.php/psqlodbc/README. unix?r=1.3 Regards, Dave.
Dave, thanks, I actually tried that, and it failed the first time for some reason? Why isn't the configure environment in CVS ? Dave On Thu, 2004-01-29 at 03:49, Dave Page wrote: > > > -----Original Message----- > > From: Dave Cramer [mailto:pg@fastcrypt.com] > > Sent: 29 January 2004 01:55 > > To: odbc list > > Subject: [ODBC] where's the build environment for odbc > > > > How come the configure scripts are not in CVS ? > > > > How do I build this thing? > > Hi Dave, > > Instructions for generating configure etc. and building a tarball can be > found in the README.unix file: > http://gborg.postgresql.org/project/psqlodbc/cvs/co.php/psqlodbc/README. > unix?r=1.3 > > Regards, Dave. > -- Dave Cramer 519 939 0336 ICQ # 1467551
> -----Original Message----- > From: Dave Cramer [mailto:pg@fastcrypt.com] > Sent: 29 January 2004 12:35 > To: Dave Page > Cc: odbc list > Subject: RE: [ODBC] where's the build environment for odbc > > Dave, > > thanks, I actually tried that, and it failed the first time > for some reason? > > Why isn't the configure environment in CVS ? Because configure is a generated file and is therefore not under source control. What exactly failed? Regards, Dave.
> -----Original Message----- > From: Dave Cramer [mailto:pg@fastcrypt.com] > Sent: 29 January 2004 13:06 > To: Dave Page > Subject: RE: [ODBC] where's the build environment for odbc > > Well, it worked this time so I can't reproduce it, however it > was the make that failed, > > Why can't you include the code to generate configure ? Because it's GNU autoconf? That would be somewhat like shipping bison with PostgreSQL wouldn't it? Regards, Dave.
I missed the previous messages, but I suspect I've been stumbling over the same obstacles. Newer versions of autoconf don't like the configure.ac that's in CVS. I sent a patch to the list today that may help. At 1/29/2004, Dave Page wrote: > > > > -----Original Message----- > > From: Dave Cramer [mailto:pg@fastcrypt.com] > > Sent: 29 January 2004 12:35 > > To: Dave Page > > Cc: odbc list > > Subject: RE: [ODBC] where's the build environment for odbc > > > > Dave, > > > > thanks, I actually tried that, and it failed the first time > > for some reason? > > > > Why isn't the configure environment in CVS ? > >Because configure is a generated file and is therefore not under source >control. > >What exactly failed?
> -----Original Message----- > From: Jon Willeke [mailto:willeke@users.sourceforge.net] > Sent: 30 January 2004 22:47 > To: odbc list > Subject: Re: [ODBC] where's the build environment for odbc > > I missed the previous messages, but I suspect I've been > stumbling over the same obstacles. Newer versions of > autoconf don't like the configure.ac that's in CVS. I sent a > patch to the list today that may help. Looking back at your previous message, I see that you use the same version of autoconf (2.5.7) as I use to build the distribution tarballs. Did you follow the instructions in README.unix and perform the build from within a PostgreSQL source tree? Regards, Dave.
No, I did not build in a PostgreSQL source tree. I have the postgresql packages, as shipped in SuSE Linux 8.2. I used autoconf 2.57, automake 1.7.6, and libtool 1.4.3. I did not pass the -I $PGSRC/config switch to aclocal, because I have no such file. Otherwise, I followed the README. The resulting driver seems to work fine. At 1/31/2004, Dave Page wrote: >Looking back at your previous message, I see that you use the same >version of autoconf (2.5.7) as I use to build the distribution tarballs. > >Did you follow the instructions in README.unix and perform the build >from within a PostgreSQL source tree?
Hi Jon, I have run your patch past a developer who is familiar with the psqlODBC and PostgreSQL build systems (something which I am not). He made some comments based on which I will not be applying your patch to CVS as it currently stands: The changes to AC_INIT and AM_INIT_AUTOMAKE change from "new style" to "old style" and are therefore definitely wrong. The PGAC_ARG_* macros provide a more robust argument checking than the standard ones, so I would keep them. If there is a problem that you need to get these macros from the PostgreSQL source tree (only for CVS developers, not "to build"), then just copy over the required m4 files and put them in your CVS. The changes in AM_CONDITIONAL are then pointless if you keep using the PGAC_ARG_ macros. Also, "$with_unixodbc-no" is wrong. Replacing PGAC_VAR_INT_TIMEZONE by AC_STRUCT_TIMEZONE is wrong, because they don't do the same thing at all. Again, just copy the m4 file if you must. If you have time to submit a revised patch based on these comments, it would be appreciated. Regards, Dave. > -----Original Message----- > From: Jon Willeke [mailto:willeke@users.sourceforge.net] > Sent: 02 February 2004 16:53 > To: odbc list > Subject: Re: [ODBC] where's the build environment for odbc > > No, I did not build in a PostgreSQL source tree. I have the > postgresql packages, as shipped in SuSE Linux 8.2. > > I used autoconf 2.57, automake 1.7.6, and libtool 1.4.3. I > did not pass the -I $PGSRC/config switch to aclocal, because > I have no such file. Otherwise, I followed the README. > > The resulting driver seems to work fine. > > At 1/31/2004, Dave Page wrote: > > >Looking back at your previous message, I see that you use the same > >version of autoconf (2.5.7) as I use to build the > distribution tarballs. > > > >Did you follow the instructions in README.unix and perform the build > >from within a PostgreSQL source tree? > > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to > majordomo@postgresql.org) >
Thank you for your comments. I'll review the patch carefully, but I'm not sure any patch is required, except to my mental model. I learned a lot trying to build psqlodbc from CVS, and your message continues that education. Further responses inline. At 08:25 AM 2/3/2004 +0000, Dave Page wrote: >The changes to AC_INIT and AM_INIT_AUTOMAKE change from "new style" to >"old style" and are therefore definitely wrong. My research indicated the opposite. Thanks for the correction. >The PGAC_ARG_* macros provide a more robust argument checking than the >standard ones, so I would keep them. If there is a problem that you >need to get these macros from the PostgreSQL source tree (only for CVS >developers, not "to build"), then just copy over the required m4 files >and put them in your CVS. If this is the only reason for the PostgreSQL macros, I would question whether it's worth the dependency. I did not recognize them, so I thought they were, perhaps, for an older version of autoconf. >The changes in AM_CONDITIONAL are then pointless if you keep using the >PGAC_ARG_ macros. Also, "$with_unixodbc-no" is wrong. I was getting shell errors to the effect of "unary operator expected." I'll try again with the config file. >Replacing PGAC_VAR_INT_TIMEZONE by AC_STRUCT_TIMEZONE is wrong, because >they don't do the same thing at all. Again, just copy the m4 file if >you must. Another incorrect assumption, on my part, that this was some outdated construct.