New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #26224 (new defect)

Opened 3 years ago

Last modified 3 years ago

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

Reported by: aj@… Owned by: ryandesign@…
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: landonf@…
Port: zlib

Description

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.

Attachments

main.log (18.5 KB) - added by aj@… 3 years ago.
zlib build failure

Change History

comment:1 Changed 3 years ago by ryandesign@…

  • Owner changed from macports-tickets@… to ryandesign@…
  • Cc landonf@… added

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.

Changed 3 years ago by aj@…

zlib build failure

comment:2 Changed 3 years ago by aj@…

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

comment:3 Changed 3 years ago by aj@…

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

comment:4 Changed 3 years ago by jmr@…

  • Summary changed from zlib fails to configure shared library to zlib fails to configure shared library when using 'configuredistcc yes'

comment:5 Changed 3 years ago by ryandesign@…

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

comment:6 Changed 3 years ago by 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.

comment:7 Changed 3 years ago by 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.

comment:8 Changed 3 years ago by 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 =(

comment:9 Changed 3 years ago by ryandesign@…

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).

Note: See TracTickets for help on using tickets.