#24243: libproxy 0.4.0 build failure 10.4.11 --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Keywords: tiger | Port: libproxy --------------------------------+------------------------------------------- Changes (by jmr@…): * owner: macports-tickets@… => devans@… * cc: nox@…, rmsfisher@…, raimue@… (added) * keywords: => tiger Old description:

I believe this is not the failure in ticket #21427.

Build fails because libraries are expected to be in /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib, not /opt/local/lib.

I wonder if Apple g++-4.0 on 10.4.11 PPC confuses the -isysroot flag with the --sysroot flag. Or maybe it's CMake weirdness. I've never seen anything like this before.

See attached main.log for details.

I tried setting configure.cc to /opt/local/bin/gcc-mp-4.2 and configure.g++ to /opt/local/bin/g++-mp-4.3 in Portfile, but this fails at the configure stage because the MacPorts compilers don't support the "-arch ppc" flag.

New description: I believe this is not the failure in ticket #24127. Build fails because libraries are expected to be in /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib, not /opt/local/lib. I wonder if Apple g++-4.0 on 10.4.11 PPC confuses the -isysroot flag with the --sysroot flag. Or maybe it's CMake weirdness. I've never seen anything like this before. See attached main.log for details. I tried setting configure.cc to /opt/local/bin/gcc-mp-4.2 and configure.g++ to /opt/local/bin/g++-mp-4.3 in Portfile, but this fails at the configure stage because the MacPorts compilers don't support the "-arch ppc" flag. -- Comment: Please remember to cc the maintainer. -- Ticket URL: <http://trac.macports.org/ticket/24243#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#24243: libproxy 0.4.0 build failure 10.4.11 --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Keywords: tiger | Port: libproxy --------------------------------+------------------------------------------- Comment(by stephen@…): The workaround didn't work, because the link failed. The link failed because the old libwebkit links in libjpeg.7, which bit the dust quite a while ago. I tried uninstall -f'ing everything in the dependency chain (webkit-gtk -> libsoup -> libproxy). Of course building that fails dismally because building libproxy does depend on webkit-gtk. port dependents for libproxy reports only libsoup, for libsoup only webkit-gtk, and for webkit-gtk, none, of course. In fact, 'grep -l webkit' suggests that the binaries for doxygen and a library in wxWidgets- devel link to webkit. Reporting those bugs separately. -- Ticket URL: <http://trac.macports.org/ticket/24243#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#24243: libproxy 0.4.0 build failure 10.4.11 --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Keywords: tiger | Port: libproxy --------------------------------+------------------------------------------- Changes (by vinc17@…): * cc: vinc17@… (added) -- Ticket URL: <http://trac.macports.org/ticket/24243#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#24243: libproxy 0.4.0 build failure 10.4.11 --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Keywords: tiger | Port: libproxy --------------------------------+------------------------------------------- Comment(by rmsfisher@…): Stephen,[[br]] Is everything working properly now? If so this ticket could be closed as "worksforme". -- Ticket URL: <http://trac.macports.org/ticket/24243#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#24243: libproxy 0.4.0 build failure 10.4.11 --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Keywords: tiger | Port: libproxy --------------------------------+------------------------------------------- Comment(by elelay@…): yes, it is. Indeed, I had to disable PAC support to build libproxy on Tiger. -- Ticket URL: <http://trac.macports.org/ticket/24243#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#24243: libproxy 0.4.0 build failure 10.4.11 ---------------------------------+------------------------------------------ Reporter: stephen@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.99 Resolution: fixed | Keywords: tiger Port: libproxy | ---------------------------------+------------------------------------------ Changes (by devans@…): * status: new => closed * resolution: => fixed Comment: Updated to version 0.4.6 in r71365 which builds properly on Tiger. -- Ticket URL: <https://trac.macports.org/ticket/24243#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS