zlib fails to configure shared library when using 'configuredistcc yes'

[aj@…]

fresh install of macports. building zlib fails on make install on a copy $SHAREDLV line where $SHAREDLV is null.

Running configure manually in the build dir configures zlib properly to build the shared library and fill out the makefile properly. You can then use ports to install zlib, as make install will run correctly.

[ryandesign (Ryan Carsten Schmidt)]

Please Cc port maintainers.

In the past, I believe this problem was caused by attempting to install zlib while Xcode was not properly installed, then installing Xcode properly, then re-attempting to install zlib without having first cleaned it.

So please ensure the correct version of Xcode for your OS version is installed properly, clean zlib, and try again, and let us know if that works or not. If not, attach the main.log file.

[aj@…]

zlib build failure

[aj@…]

XCode is v3.2.2 gcc: is i686-apple-darwin10-gcc-4.2.1

[aj@…]

Line 40 in the main.log is where the configuration error happens

[ryandesign (Ryan Carsten Schmidt)]

I've never tried using distcc. Do you see the same problem without it?

[aj@…]

Indeed. That's it. It works fine without distcc on. Somehow the distcc failure kills the config. probably kills something in the environment or fails to set something up when distcc fails.

[dmitrij.ledkov@…]

Building with configure.compiler=clang installs only .a and .so. Building with default gcc-4.2 compiler install dylib. There is a makefile patch. Probably it needs updating.

[dmitrij.ledkov@…]

test -z "$CC" && echo Checking for ${CROSS_PREFIX}gcc...
cc=${CC-${CROSS_PREFIX}gcc}
cflags=${CFLAGS-"-O3"}
# to force the asm version use: CFLAGS="-O3 -DASMV" ./configure                 
case "$cc" in
  *gcc*) gcc=1 ;;
esac


if test "$gcc" -eq 1 && ($cc -c $cflags $test.c) 2>/dev/null; then

dylib options in the darwin case

else

no darwin case

endif

This is in the hand-written configure script. So if we are building with something that is not gcc, we are not getting dylib =(

[ryandesign (Ryan Carsten Schmidt)]

Changing a port's compiler is not something a user should be doing and is not supported (unless the port offers variants for doing that, which zlib does not).

[ryandesign (Ryan Carsten Schmidt)]

Replying to dmitrij.ledkov@…:

Building with configure.compiler=clang installs only .a and .so. Building with default gcc-4.2 compiler install dylib. There is a makefile patch. Probably it needs updating.

Replying to dmitrij.ledkov@…:

test -z "$CC" && echo Checking for ${CROSS_PREFIX}gcc...
cc=${CC-${CROSS_PREFIX}gcc}
cflags=${CFLAGS-"-O3"}
# to force the asm version use: CFLAGS="-O3 -DASMV" ./configure                 
case "$cc" in
  *gcc*) gcc=1 ;;
esac


if test "$gcc" -eq 1 && ($cc -c $cflags $test.c) 2>/dev/null; then

dylib options in the darwin case

else

no darwin case

endif

This is in the hand-written configure script. So if we are building with something that is not gcc, we are not getting dylib =(

This is an unrelated issue which was filed separately as #28656 and fixed.

[ryandesign (Ryan Carsten Schmidt)]

Back to the original issue this ticket was about:

Replying to aj@…:

Indeed. That's it. It works fine without distcc on. Somehow the distcc failure kills the config. probably kills something in the environment or fails to set something up when distcc fails.

Is this still a problem with the latest version of zlib, 1.2.11, and the latest version of distcc, 3.3.3?