--- On Thu, 3/24/11, Ryan Schmidt <[email protected]> wrote:
> You really should choose this "UNIX Development" option as recommended
> in the guide [1].
It's not a recommendation; it's a requirement for using MacPorts the way it's
currently programmed.
I unfortunately conflated two questions that aren't really related; I'm sorry
for that.
The important question for me is "Can I install Macports without
tclConfig.sh?" The answer seems to be "No", which is a problem because,
regardless of whether I install Xcode in a standard or non-standard location,
it's not installing tclConfig.sh; and my installation of Snow Leopard (from a
master image at $WORK) doesn't include that file either. (I don't have the
disks for Snow Leopard, so I can't re-install it; and Xcode is freshly
downloaded from developer.apple.com, so I think it's not the problem.) Thus,
my question is: Given that I don't currently have tclConfig.sh, how can I
generate it, or otherwise get past this step of ./configure?
(The *other*, less important question, is "Can I install Macports if my Xcode
is in a non-standard location?" Your answer seems to be "No", but, aside from
this problem with tclConfig.sh --which is *missing*, not just in the wrong
location!-- it seems to have gone OK so far.)
Thanks for your help. I'm sorry again for posing the question badly.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
