[MacPorts] #46331: libtool contains references to ccache when it was built with ccache
#46331: libtool contains references to ccache when it was built with ccache --------------------------+---------------------- Reporter: ryandesign@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: libtool --------------------------+---------------------- If my MacPorts installation is configured to use ccache at the time that the libtool port is built and installed, then the installed copy of libtool contains references to ccache and uses ccache when other software uses libtool, even if those other ports have requested that ccache be disabled. {{{ $ grep ccache /opt/local/bin/glibtool LTCC="ccache /usr/bin/clang" CC="ccache /usr/bin/clang" CC="ccache /usr/bin/clang++" }}} In fact it looks like it contains references to the compiler (clang in this case) as well. -- Ticket URL: <https://trac.macports.org/ticket/46331> MacPorts <https://www.macports.org/> Ports system for OS X
#46331: libtool contains references to ccache when it was built with ccache ---------------------------+---------------------- Reporter: ryandesign@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libtool | ---------------------------+---------------------- Comment (by ryandesign@…): I'm attaching a logfile which shows how pdflib fails to build when libtool was built with ccache (even though the pdflib portfile already says "configure.ccache no". It would be nice if we could fix this somehow. The simplest would be to set "configure.ccache no" in the libtool portfile and increase its revision. -- Ticket URL: <https://trac.macports.org/ticket/46331#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#46331: libtool contains references to ccache when it was built with ccache ---------------------------+---------------------- Reporter: ryandesign@… | Owner: larryv@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libtool | ---------------------------+---------------------- Changes (by larryv@…): * status: new => assigned Comment: Sorry for taking so long to look into this (to put it mildly). I agree that there’s something mildly unsettling about the hardcoded references to ccache, but it's not clear to me that they’re the root cause of this build problem. Unfortunately, I’m unable to reproduce the problem with pdflib @7.0.5_2, even though I deleted MacPorts’s ccache…cache…and the build did copy over the “infected” libtool: {{{ % port installed libtool and active The following ports are currently installed: libtool @2.4.6_2+universal (active) % sudo rm -fR /opt/local/var/macports/build/.ccache % sudo port build pdflib +universal build.jobs=1 ---> Computing dependencies for pdflib ---> Fetching distfiles for pdflib ---> Verifying checksums for pdflib ---> Extracting pdflib ---> Applying patches to pdflib ---> Configuring pdflib ---> Building pdflib % ag ccache $(port work pdflib)/PDFlib-Lite-7.0.5/libtool 171:LTCC="ccache /usr/bin/clang" 324:CC="ccache /usr/bin/clang" 504: compile | *[\\/]compile | ccache | *[\\/]ccache ) ;; 11679:CC="ccache /usr/bin/clang++" % }}} Can you still reproduce this? -- Ticket URL: <https://trac.macports.org/ticket/46331#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts