[MacPorts] #42673: kde4-baseapps build failure on OS X 10.6.8
MacPorts
noreply at macports.org
Sun Apr 27 09:31:01 PDT 2014
#42673: kde4-baseapps build failure on OS X 10.6.8
----------------------------+---------------------
Reporter: rjvbertin@… | Owner: nicos@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: kde4-baseapps |
----------------------------+---------------------
Comment (by rjvbertin@…):
Replying to [comment:11 nicos@…]:
> Destroot should trigger the use of source directly, I think. The other
thing is:
> {{{
> :info:build cd
/opt/local/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_kde_kde4
> }}}
> From this line, it seems to me that you are using an additional
Portfiles directory. It is not likely, but depending on your install, it
may prevent the use of binaries.
This has always stymied me a bit. My /opt/local is a symlink to
/Volumes/Debian/MacPorts (the partition name just stuck :) ), and AFAIK
there's nothing in macports.conf that tells MacPorts that this is the
case. Somewhere it does a symlink normalisation, but in any case I'm not
using an additional Portfiles directory.
Some ports install from prebuilt binaries, others are always rebuilt from
source, and I've never yet tried to understand why (apart from the ports
where the answer is obvious, like ffmpeg with non-free contributions).
> I admit that this problem is rather puzzling, as neither I nor the bots
can reproduce it. And as far as I can be aware, there has been no other
report of this issue.
As long as there's a binary build for 10.6 it's just that, a puzzle ...
and I hope it'll remain that way!
--
Ticket URL: <https://trac.macports.org/ticket/42673#comment:12>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list