[MacPorts] #37522: doxygen: UsingTheRightCompiler
#37522: doxygen: UsingTheRightCompiler ----------------------+--------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: doxygen ----------------------+--------------------- Here is a patch to fix the invocation of the compiler in the libmd5 subdirectory, see UsingTheRightCompiler. This patch also removes the obsolete lion.patch, that was still commented out in the Portfile and a small correction to the patch arguments by passing -p1 in pre_args, not post_args (previous command was `patch -p0 -p1`). Please apply this patch with `svn patch`, as it does not contain a full diff for the deleted file. -- Ticket URL: <https://trac.macports.org/ticket/37522> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by css@…): * status: new => assigned -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Comment (by g5pw@…): It still fails on my machine, ML with the +wizard variant, due to a stray "-arch i386". Attaching logfile. -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by jeremyhu@…): * status: assigned => closed * resolution: => fixed Comment: r102643 -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by ryandesign@…): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:4 g5pw@…]:
It still fails on my machine, ML with the +wizard variant, due to a stray "-arch i386". Attaching logfile.
That is a different problem: #37546 Replying to [comment:5 jeremyhu@…]:
r102643
That does not fix it for me. -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by ryandesign@…): * status: reopened => closed * resolution: => fixed Comment: After some investigation it turns out to be a parallel build issue. I guess libmd5 is depended on in multiple places, and in at least one place, the correct compiler name and flags are not passed along. Fixed in r103086 by turning parallel build off. -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by ryandesign@…): * status: closed => reopened * resolution: fixed => Comment: Not fixed. It still randomly uses `cc` instead of ${configure.cc}. Attaching both a "good" and a "bad" log. In the "good" case, Makefile.libmd5 actually gets replaced by the following command: {{{ env TMAKEPATH=/opt/local/var/macports/build/_Users_rschmidt_macports_dports_textproc_doxygen/doxygen/work/doxygen-1.8.3/tmake/lib/macosx-c++ /opt/local/bin/perl /opt/local/var/macports/build/_Users_rschmidt_macports_dports_textproc_doxygen/doxygen/work/doxygen-1.8.3/tmake/bin/tmake libmd5.pro >Makefile.libmd5 }}} -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37522: doxygen: UsingTheRightCompiler -----------------------+---------------------- Reporter: raimue@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: haspatch Port: doxygen | -----------------------+---------------------- Changes (by ryandesign@…): * cc: mmoll@… (added) * status: reopened => closed * resolution: => fixed Comment: The problem was caused by r101062 (committed less than a day before this ticket was filed) which added a reinplace on three tmake.conf files, Makefile.libmd5, and Makefile.libdoxycfg. But Makefile.libmd5 and Makefile.libdoxycfg are supposed to be regenerated by tmake, using the tmake.conf. The problem must be occurring when the tmake.conf file that is actually being used is modified in the same second as the Makefiles are modified, resulting in the build process believing that the Makefiles are already up to date and do not need to be regenerated. The solution is to reinplace only the tmake.conf file; then the Makefiles will be regenerated from it. And there's no need to reinplace three different tmake.conf files; the port will only use one of them, as defined by the port's ${tmake_conf} variable. Fixed in r103089. -- Ticket URL: <https://trac.macports.org/ticket/37522#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts