#32552: Mesa 7.11 does not compile on Tiger/Mac OS X 10.4.11 because unsupported platform ---------------------------------------+------------------------------------ Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: duplicate | Keywords: Port: Mesa | ---------------------------------------+------------------------------------ Comment(by Peter_Dyballa@…): Replying to [comment:3 jeremyhu@…]:
Yes, that should be darwin ... r88037
Right now, around 10:30 UTC, after a selfupdate half an hour ago, I have: {{{ 3350046 16 -rw-r--r-- 1 root admin 5247 7 Dez 01:28 rsync.macports.org/release/ports/x11/mesa/Portfile 3152620 16 -rw-r--r-- 1 root wheel 5248 5 Okt 19:30 rsync.macports.org/release/tarballs/ports/x11/mesa/Portfile diff rsync.macports.org/release/ports/x11/mesa/Portfile rsync.macports.org/release/tarballs/ports/x11/mesa/Portfile 57c57 < build.target darwin ---
build.target default }}}
I was looking and then editing the latter, which is now "up-to-date" again. From 'port -vd clean mesa' I can see again that probably the latter Portfile is used for the build: {{{ DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/x11/mesa }}} Why do these two almost identical Portfiles exist? Is there no way to remove the useless variants? Anyway, 3 h laters, although the target "darwin" was made, I am back at the previous failure, just as in http://trac.macports.org/ticket/29860 described. OK! I'll have to have a closer look later! -- Ticket URL: <https://trac.macports.org/ticket/32552#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS