Re: Macports stopped working after xcode 4.6 upgrade
On 2013-02-21 09:42, Harald Hanche-Olsen wrote: [Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)] Very annoying. I've actually filed a Radar about this. http://openradar.appspot.com/radar?id=2620402 Good. (Should this be in the FAQ?) Considering that we don't recommend using /etc/paths or /etc/paths.d anywhere, I'm not sure it needs to be. The reason would be to inform people who know about these, or discover them, may want to use them in the way I suggested. But if it doesn't satisfy the F in FAQ, then perhaps it should not be included. Tha balancing act between supplying too little information and too much is always tricky. Besides the FAQ [1], we also have the ProblemHotlist [2]. It's not frequently asked and also not a hot problem, so maybe we should have another list of common problems? Or maybe just decide for one of the existing wiki pages and add it there... I would appreciate to have a place in the wiki to point to for topics like this (Why isn't MacPorts doing/using XYZ?). Rainer [1] https://trac.macports.org/wiki/FAQ [2] https://trac.macports.org/wiki/ProblemHotlist ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
On Feb 22, 2013, at 12:37, Rainer Müller rai...@macports.org wrote: On 2013-02-21 09:42, Harald Hanche-Olsen wrote: [Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)] Very annoying. I've actually filed a Radar about this. http://openradar.appspot.com/radar?id=2620402 Good. (Should this be in the FAQ?) Considering that we don't recommend using /etc/paths or /etc/paths.d anywhere, I'm not sure it needs to be. The reason would be to inform people who know about these, or discover them, may want to use them in the way I suggested. But if it doesn't satisfy the F in FAQ, then perhaps it should not be included. Tha balancing act between supplying too little information and too much is always tricky. Besides the FAQ [1], we also have the ProblemHotlist [2]. It's not frequently asked and also not a hot problem, so maybe we should have another list of common problems? We already have far too many lists of problems; we should be working on consolidating them, not making new ones. Or maybe just decide for one of the existing wiki pages and add it there... I'd be in favor of that. The more-frequently-asked questions would go at nearer to the top of the page. I would appreciate to have a place in the wiki to point to for topics like this (Why isn't MacPorts doing/using XYZ?). We can also just create individual pages in the wiki to point people to. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
[Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)] Very annoying. I've actually filed a Radar about this. http://openradar.appspot.com/radar?id=2620402 Good. (Should this be in the FAQ?) Considering that we don't recommend using /etc/paths or /etc/paths.d anywhere, I'm not sure it needs to be. The reason would be to inform people who know about these, or discover them, may want to use them in the way I suggested. But if it doesn't satisfy the F in FAQ, then perhaps it should not be included. Tha balancing act between supplying too little information and too much is always tricky. – Harald ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
[Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)] Sorry about the typo. export PATH=/opt/local/bin:/opt/local/sbin:$PATH Another way to do that is to put this in a file in /etc/paths.d/: /opt/local/bin /opt/local/sbin - Harald ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
On Feb 20, 2013, at 3:22 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote: [Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)] Sorry about the typo. export PATH=/opt/local/bin:/opt/local/sbin:$PATH Another way to do that is to put this in a file in /etc/paths.d/: /opt/local/bin /opt/local/sbin These are not equivalent. Directory entries added via /etc/paths.d are tacked onto the *end* of the default PATH, while the quoted export statement adds them to the *beginning*. The latter is necessary if you want your shell to find MacPorts executables before system ones. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
[Lawrence Velázquez lar...@macports.org (2013-02-20 08:47:13 UTC)] On Feb 20, 2013, at 3:22 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote: [Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)] export PATH=/opt/local/bin:/opt/local/sbin:$PATH Another way to do that is to put this in a file in /etc/paths.d/: /opt/local/bin /opt/local/sbin These are not equivalent. Directory entries added via /etc/paths.d are tacked onto the *end* of the default PATH, while the quoted export statement adds them to the *beginning*. The latter is necessary if you want your shell to find MacPorts executables before system ones. True. If that is what you want, you can tack the directories onto the front of /etc/paths instead. Not sure if either will survive a system upgrade, though. But on the other hand, it will work for all users on the machine. - Harald ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
On Feb 20, 2013, at 4:09 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote: True. If that is what you want, you can tack the directories onto the front of /etc/paths instead. Not sure if either will survive a system upgrade, though. But on the other hand, it will work for all users on the machine. For the curious. https://trac.macports.org/ticket/20524 https://trac.macports.org/ticket/24105 https://trac.macports.org/ticket/30458 https://trac.macports.org/ticket/36323 vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
[Lawrence Velázquez lar...@macports.org (2013-02-20 09:16:27 UTC)] On Feb 20, 2013, at 4:09 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote: True. If that is what you want, you can tack the directories onto the front of /etc/paths instead. Not sure if either will survive a system upgrade, though. But on the other hand, it will work for all users on the machine. For the curious. […] Argh. So that doesn't work either, then. path_helper starts with the current PATH, then append pathnames from /etc/paths and /etc/paths.d/* excepting, presumably, patnames that have already been included – so you can't prepend a pathname to PATH this way. Good to know. (Should this be in the FAQ?) - Harald ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
On Feb 20, 2013, at 4:31 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote: Argh. So that doesn't work either, then. path_helper starts with the current PATH, then append pathnames from /etc/paths and /etc/paths.d/* excepting, presumably, patnames that have already been included – so you can't prepend a pathname to PATH this way. Good to know. For all situations other than fresh login shells, path_helper is all sorts of irritating. For instance, say path_helper initially sets up this PATH. PATH=foo:bar:baz Hurrah. Then you prepend an entry yourself, in your .profile or whatever. PATH=quux:foo:bar:baz If you run path_helper again (e.g., you start an interactive non-login bash shell on OS X), it won't be satisfied that the 3 directories it wants to add are already there. Oh no, it has to make sure they're first in line. PATH=foo:bar:baz:quux Very annoying. I've actually filed a Radar about this. http://openradar.appspot.com/radar?id=2620402 (Should this be in the FAQ?) Considering that we don't recommend using /etc/paths or /etc/paths.d anywhere, I'm not sure it needs to be. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
sh: port: command not found
Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the version
of Macports but I downloaded it in December last year. Any help would be
greatly appreciated. Thanks.
The error means `port` is no longer in your $PATH. You should be able to run
`/opt/local/bin/port` in the meantime.
Here's how to fix $PATH (from macports.org/install.php):
You will need to manually adapt your shell's environment to work with MacPorts
and your chosen installation prefix (the value passed to configure's --prefix
flag, defaulting to /opt/local):
• Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH
environment variable so that MacPorts-installed programs take precedence over
system-provided programs of the same name.
• If a standard MANPATH environment variable already exists (that is,
one that doesn't contain any empty components), add the ${prefix}/share/man
path to it so that MacPorts-installed man pages are found by your shell.
• For Tiger and earlier only, add an appropriate X11 DISPLAY
environment variable to run X11-dependent programs, as Leopard takes care of
this requirement on its own.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
Hi Jeremy,
Thanks for your quick reply. Its working now. I didn't realized that.
I just added the below in my ~/.bash_profile
export PATH=/opt/local/bin:opt/local/sbin:$PATH
Thanks.
Best Regards,
Richard R. Cahilig
chr05210...@gmail.com
On Feb 19, 2013, at 10:40 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
sh: port: command not found
Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the
version of Macports but I downloaded it in December last year. Any help
would be greatly appreciated. Thanks.
The error means `port` is no longer in your $PATH. You should be able to run
`/opt/local/bin/port` in the meantime.
Here's how to fix $PATH (from macports.org/install.php):
You will need to manually adapt your shell's environment to work with
MacPorts and your chosen installation prefix (the value passed to configure's
--prefix flag, defaulting to /opt/local):
• Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH
environment variable so that MacPorts-installed programs take precedence over
system-provided programs of the same name.
• If a standard MANPATH environment variable already exists (that is,
one that doesn't contain any empty components), add the ${prefix}/share/man
path to it so that MacPorts-installed man pages are found by your shell.
• For Tiger and earlier only, add an appropriate X11 DISPLAY
environment variable to run X11-dependent programs, as Leopard takes care of
this requirement on its own.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports stopped working after xcode 4.6 upgrade
Sorry about the typo.
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
Best Regards,
Richard R. Cahilig
chr05210...@gmail.com
On Feb 19, 2013, at 11:32 PM, Richard R. Cahilig chr05210...@gmail.com wrote:
Hi Jeremy,
Thanks for your quick reply. Its working now. I didn't realized that.
I just added the below in my ~/.bash_profile
export PATH=/opt/local/bin:opt/local/sbin:$PATH
Thanks.
Best Regards,
Richard R. Cahilig
chr05210...@gmail.com
On Feb 19, 2013, at 10:40 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
sh: port: command not found
Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the
version of Macports but I downloaded it in December last year. Any help
would be greatly appreciated. Thanks.
The error means `port` is no longer in your $PATH. You should be able to run
`/opt/local/bin/port` in the meantime.
Here's how to fix $PATH (from macports.org/install.php):
You will need to manually adapt your shell's environment to work with
MacPorts and your chosen installation prefix (the value passed to
configure's --prefix flag, defaulting to /opt/local):
• Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH
environment variable so that MacPorts-installed programs take precedence
over system-provided programs of the same name.
• If a standard MANPATH environment variable already exists (that is,
one that doesn't contain any empty components), add the ${prefix}/share/man
path to it so that MacPorts-installed man pages are found by your shell.
• For Tiger and earlier only, add an appropriate X11 DISPLAY
environment variable to run X11-dependent programs, as Leopard takes care of
this requirement on its own.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
