On Nov 12, 2013, at 4:19 PM, Art McGee <[email protected]> wrote:
> Yep, did that, same result. If this were happening with other ports I'd think
> it was my macports setup or my system, but this only happens with crafty.
crafty has a custom extract phase.
extract {
file mkdir work
# extract the src zip
system "cd ${workpath} && unzip ${distpath}/${dist_srczip}"
reinplace "s|IPHONE|__APPLE__|g" ${worksrcpath}/chess.h
reinplace -E "s|BOOKDIR \+\".\"|BOOKDIR \"${prefix}/share/crafty\"|g"
${worksrcpath}/chess.h
}
This "file mkdir" statement assumes that non-absolute paths are determined
relative to ${portbuildpath}, which is probably false.
In any case, the custom script should be removed. Base can handle this easily
and more robustly.
https://trac.macports.org/ticket/41338
vq
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
