[HACKERS] 7.4 include file conflict
Hello, I saw another post on this list about some conflicts on building an rpm on redhat that seemed similar. I wanted to add that I was building PHP with the individual directory flags, (./configure --with-iodbc=/usr --with-pgsql=/usr/local ) and the compiler still choked (see below). Not sure if just moving the file sqltypes.h will fix this. Copied my message from another list to this one also. Thanks. Ray A. Hello, I have a question regarding the 7.4 library include file called /usr/local/pgsql/include/sqltypes.h It seems to only include supplementary type defs. The problem is that I installed the client libraries on a Mac XSERVE 10.3 server that comes with iODBC libraries in /usr/include. I was compiling PHP with iODBC support as well as with PgSQL support and it kept dying with syntax errors on the iODBC make. I found that the compiler was looking in the pgsql include directory first and found its version of sqltypes.h I was able to get around the errors by renaming the pg header file to something else, but I still have not checked if that had some impact on the pg functionality that was built. Is it necessary to have this include file named this or could it be renamed to something more specific to like pgsqltypes.h More info on this file would be appreciated. Thanks much. Ray A. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 include file conflict
I would like to mention that I am on MacOS 10.3 and have this issue when compiling PHP with both iODBC support and Postgres support at the same time. I have to specify the -I/usr/include and the -I/usr/local/pgsql/include in order for the build scripts to run correctly. the problem is that at build time when building iODBC it may or may not look in /usr/include first depending on when the flags were placed. Moving the file to ecpg/sqltypes.h should do the trick because anything other than postgres should not traverse into ecpg/ unless specifically looking for it. Not sure if that breaks any user programs as someone else noted. Thanks. Ray A. At 9:39 AM +0100 12/17/03, Michael Meskes wrote: On Tue, Dec 16, 2003 at 07:00:25PM -0500, Bruce Momjian wrote: Are you saying some programs will look in /usr/include before looking in -I specified directories, and that is the whole problem? If so, that is 100% wrong and we don't have to fix our files to workaround this. No I meant to say that you will alsways get our file and not the one in /usr/include. That means you must not specify our -I option if you need the file in /usr/include. Since this file may be needed together with pgsql The best way seems to be moving just the compat headers IMO. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[HACKERS] postgres Mac OS X startup script
Hello, I wanted to submit some changes to the bundled postgres startup script for Mac OS X. I added calls to utilize the bundled apache rotatelogs script in the DB startup for log rotation. Also modified startup parameters file to allow using the "SystemStarter" utility to start/stop/restart postgres with a rotating log file. The script credits David Wheeler, 2002. I wrote him a message about the changes an he suggested I post them here. I explain some of the changes below. Not sure how to submit the changes. I have 3 files, "PostgreSQL" script, "StartupParameters.plist" file, "pg_startupscript.diff" file. The diff file was run against the original "PostgreSQL" script file. I'll try attaching them to this message. If they get filtered I can resend if needed. Thanks. Ray A. 1) Changed the "Provides" parameter in StartupParameters.plist to "PostgreSQL" from "postgres database" simply for ease of typing. It seems that the SystemStarter utility uses the "Provides" value if you want to control the script. This way I did not have to enclose it in quotes on commandline. The modified StartupParameters.plist is now an XML document also. 2) For the startup script I added 2 user modifiable variables: # do you want to rotate the log files, 1=true 0=false ROTATELOGS=1 # logfile rotate in seconds ROTATESEC="604800" I also added a non modifiable variable: # The apache log rotation utility LOGUTIL="/usr/sbin/rotatelogs" I modified the StartService and RestartService functions to execute the new commands if the user wants log rotation. %PostgreSQL Description: application/applefile PostgreSQL Description: Binary data %StartupParameters.plist Description: application/applefile StartupParameters.plist Description: Binary data %pg_startupscript.diff Description: application/applefile pg_startupscript.diff Description: Binary data ---(end of broadcast)--- TIP 8: explain analyze is your friend