Date: Mon, 10 Jun 2002 17:15:24 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: obrien@freebsd.org Cc: Stanislav Grozev <tacho@daemonz.org>, Shizuka Kudo <shizukakudo_99@yahoo.com>, freebsd-current@freebsd.org Subject: Re: My postgresql7 not working for new gcc Message-ID: <3D05411C.9CD7D59C@mindspring.com> References: <20020601195008.GJ17045@elvis.mu.org> <20020605113540.62177.qmail@web11402.mail.yahoo.com> <20020610115150.GA91765@meerkat.dungeon> <3D04B166.950171E2@mindspring.com> <20020610083921.A37639@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > *sigh*, why not a *real* fix? Feel free to submit this to the Postgres project... they may even incorporate it. > You'll note that they bother with this kind of check for other headers, > but for some reason didn't consider it for openssl headers. Mostly the reason that this fix was not being bandied about is that the Postgres source code is largely under third party control. If the change can be made to the Makefile, etc., which is under direct control of FreeBSD, then the code will compile unmodified. That means if there are future changes, we won't end up with a local patch to third party code, which doesn't apply cleanly. Locally maintaining patches against large projects is a very big headache; in fact, this headache is one of the primary things people rely upon in order to ensure that people donate tactical fixes back to the FreeBSD project itself. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D05411C.9CD7D59C>