Good idea. Patch attached. autoconf run.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Looking at configure.in, it looks pretty safe:
>
> > if test "$ac_env_CXXFLAGS" != set; then
> > if test
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Looking at configure.in, it looks pretty safe:
> if test "$ac_env_CXXFLAGS" != set; then
> if test "$GXX" = yes; then
> CXXFLAGS=-O2
> else
> case $template in
> osf)CXXFLAGS='-O4 -Olimit 2000' ;;
> unix
Peter Eisentraut wrote:
> > Interesting. I thought -O2 was only set in /template files, but I now
> > see it is set in configure too. The following patch fixes the libpqxx
> > compile problem on FreeBSD/alpha. The old code set -O2 for
> > FreeBSD/i386, but that is already set earlier. The new
Tom Lane writes:
> As a general rule, anything that affects one *BSD affects them all.
> I am always very suspicious of any patch that changes only one of
> the *BSD templates or makefiles. I'm not even convinced we should
> have separate makefiles/templates for 'em ...
If they could retroactiv
Bruce Momjian writes:
> jtv wrote:
> > On Wed, Jul 03, 2002 at 01:45:56PM -0400, Bruce Momjian wrote:
> > >
> > > Actually, I am confused. In src/template/freebsd I see:
> > >
> > > CFLAGS='-pipe'
> > >
> > > case $host_cpu in
> > > alpha*) CFLAGS="$CFLAGS -O";;
> > > i386*)CFLA
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > ... The following patch fixes the libpqxx
> > compile problem on FreeBSD/alpha. The old code set -O2 for
> > FreeBSD/i386, but that is already set earlier. The new patch just
> > updates the FreeBSD/alpha compile.
>
> As a general
Bruce Momjian <[EMAIL PROTECTED]> writes:
> ... The following patch fixes the libpqxx
> compile problem on FreeBSD/alpha. The old code set -O2 for
> FreeBSD/i386, but that is already set earlier. The new patch just
> updates the FreeBSD/alpha compile.
As a general rule, anything that affects on
jtv wrote:
> On Wed, Jul 03, 2002 at 01:45:56PM -0400, Bruce Momjian wrote:
> >
> > Actually, I am confused. In src/template/freebsd I see:
> >
> > CFLAGS='-pipe'
> >
> > case $host_cpu in
> > alpha*) CFLAGS="$CFLAGS -O";;
> > i386*)CFLAGS="$CFLAGS -O2";;
> >
On Wed, Jul 03, 2002 at 01:45:56PM -0400, Bruce Momjian wrote:
>
> Actually, I am confused. In src/template/freebsd I see:
>
> CFLAGS='-pipe'
>
> case $host_cpu in
> alpha*) CFLAGS="$CFLAGS -O";;
> i386*)CFLAGS="$CFLAGS -O2";;
> esac
>
> so w
Actually, I am confused. In src/template/freebsd I see:
CFLAGS='-pipe'
case $host_cpu in
alpha*) CFLAGS="$CFLAGS -O";;
i386*)CFLAGS="$CFLAGS -O2";;
esac
so why is he seeing the -O2 flag on FreeBSD/alpha?
---
And the problem is, what? Except for the -O2 warnings, looks fine to
me.
---
Christopher Kings-Lynne wrote:
> OK, this is what I'm seeing on FreeBSD/Alpha for libpq++. I haven't figured
> out how to build libpqxx yet.:
>
On Wed, Jul 03, 2002 at 02:25:46PM +0800, Christopher Kings-Lynne wrote:
> OK, this is what I'm seeing on FreeBSD/Alpha for libpq++.
[cut]
[paste]
> cc1plus: warning:
> ***
> *** The -O2 flag TRIGGERS KNOWN OPTIMIZER BUGS ON THIS PLATFORM
> ***
Doesn't say it doesn't work though... Have
OK, this is what I'm seeing on FreeBSD/Alpha for libpq++. I haven't figured
out how to build libpqxx yet.:
gmake[3]: Entering directory
`/home/chriskl/pgsql-head/src/interfaces/libpq++'
g++ -O2 -g -Wall -fpic -DPIC -I../../../src/interfaces/libpq -I../../../src/
include -c -o pgconnection.o pg
13 matches
Mail list logo