subversion-perlbindings-5.12 1.7.8_2: Leopard build error

[mklein-de (Michael Klein)]

for some parts gcc-4.2 is used, other parts use gcc-4.0, who doesn't know about -Werror=implicit-function-declaration

attaching build log

[mklein-de (Michael Klein)]

build log

[danielluke (Daniel J. Luke)]

This builds without errors on my darwin9 ppc box (and it does use gcc-4.0 which I believe is being selected because perl5.12 was built with it). The only obvious difference I see is that I don't build with +no_bdb.

Can you try it without +no_bdb and see if it builds for you then?

Note that my build doesn't have the -Werror you're seeing ether:

/usr/bin/gcc-4.0 -c  -I/opt/local/include/apr-1   -I/opt/local/include/apr-1 -I/opt/local/include  -I../../../../../subversion/bindings/swig/perl/libsvn_swig_perl  -I../../../../../subversion/include  -I../../../../../subversion  -I../../../../../subversion/bindings/swig -g -pipe -O2 -arch ppc    -pipe -O2  -fno-common -DPERL_DARWIN -I/opt/local/include -no-cpp-precomp -fno-strict-aliasing -fstack-protector -I/opt/local/include    -DVERSION=\"\" -DXS_VERSION=\"\"  "-I/opt/local/lib/perl5/5.12.4/darwin-thread-multi-2level/CORE"  -I/opt/local/include   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp core.c

I also don't have ruby installed on that machine (other than the system one) and it appears that that might be where the build is picking up -Werror=implicit-function-declaration for you.

[mklein-de (Michael Klein)]

Replying to dluke@…:

This builds without errors on my darwin9 ppc box (and it does use gcc-4.0 which I believe is being selected because perl5.12 was built with it). The only obvious difference I see is that I don't build with +no_bdb.

Can you try it without +no_bdb and see if it builds for you then?

The configure script still sees gcc-4.2, before it dies with "error: Berkeley DB 4.1.25 or newer wasn't found."

It seems the default compiler has somehow changed from gcc-4.0 to gcc-4.2, probably earlier today when I did a "port selfupdate", followed by a source install.

So it doesn't seem to be a problem of the subversion-perlbinding port.

I also don't have ruby installed on that machine (other than the system one) and it appears that that might be where the build is picking up -Werror=implicit-function-declaration for you.

I don't think so; It's the subversion configure script which checks for this.

[ryandesign (Ryan Carsten Schmidt)]

The default compiler for Leopard in MacPorts 2.1.x is gcc-4.0, as it has been in every prior MacPorts version. It might change to gcc-4.2 in a future MacPorts version.

If subversion-perlbindings-5.x is building using the compiler perl was built with, that is a bug. It should be UsingTheRightCompiler—that is, using the compiler identified by the configure.compiler variable.

[mklein-de (Michael Klein)]

Replying to ryandesign@…:

The default compiler for Leopard in MacPorts 2.1.x is gcc-4.0, as it has been in every prior MacPorts version. It might change to gcc-4.2 in a future MacPorts version.

It seems the default compiler has changed in r92109

My MacPorts base is installed from subversion (​http://guide.macports.org/#installing.macports.subversion)

$ port version
Version: 2.1.99

Does that still count as 2.1.x or is this now a 2.2.x prerelease?

If subversion-perlbindings-5.x is building using the compiler perl was built with, that is a bug. It should be UsingTheRightCompiler—that is, using the compiler identified by the configure.compiler variable.

[mklein-de (Michael Klein)]

Builds ok after adding the following line in macports.conf:

default_compilers gcc-4.0 gcc-4.2 clang llvm-gcc-4.2 macports-clang-3.2 macports-llvm-gcc-4.2 apple-gcc-4.2