[MacPorts] #26834: xemacs and ctags conflict (was: xemacs and macvim ctags conflict)
MacPorts
noreply at macports.org
Wed Oct 13 19:52:53 PDT 2010
#26834: xemacs and ctags conflict
------------------------------------------+---------------------------------
Reporter: ilevy@… | Owner: mww@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: | Port: xemacs ctags
------------------------------------------+---------------------------------
Changes (by jmr@…):
* owner: macports-tickets@… => mww@…
* port: MacVim => xemacs ctags
Old description:
> Hi all,
>
> newbie to macports / mac. I'm trying to install xemacs and macvim
> (overkill, I know, since I should just choose one). Anyway, if I have
> one activated and try to install/activate the other, I get:
>
> ---> Activating xemacs @21.4.22_2
> Error: Target org.macports.activate returned: Image error:
> /opt/local/bin/ctags is being used by the active ctags port. Please
> deactivate this port first, or use 'port -f activate xemacs' to force the
> activation.
> Log for xemacs is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_xemacs_21.4.22_2/main.log
> Warning: Failed to execute portfile from registry for xemacs @21.4.22_2
> ---> Activating xemacs
> Error: port activate failed: Image error: /opt/local/bin/ctags is being
> used by the active ctags port. Please deactivate this port first, or use
> 'port -f activate xemacs' to force the activation.
>
>
> The log file doesn't have any more information. I did have a weird
> python install, if that makes a difference. I installed python2.7 from
> their website as a normal installer, and it put it's own path in my
> .profile. So python actually linked to 2.7 instead of what macports
> thought.
>
> But besides that everything is fairly standard.
New description:
Hi all,
newbie to macports / mac. I'm trying to install xemacs and macvim
(overkill, I know, since I should just choose one). Anyway, if I have one
activated and try to install/activate the other, I get:
{{{
---> Activating xemacs @21.4.22_2
Error: Target org.macports.activate returned: Image error:
/opt/local/bin/ctags is being used by the active ctags port. Please
deactivate this port first, or use 'port -f activate xemacs' to force the
activation.
Log for xemacs is at:
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_xemacs_21.4.22_2/main.log
Warning: Failed to execute portfile from registry for xemacs @21.4.22_2
---> Activating xemacs
Error: port activate failed: Image error: /opt/local/bin/ctags is being
used by the active ctags port. Please deactivate this port first, or use
'port -f activate xemacs' to force the activation.
}}}
The log file doesn't have any more information. I did have a weird python
install, if that makes a difference. I installed python2.7 from their
website as a normal installer, and it put it's own path in my .profile.
So python actually linked to 2.7 instead of what macports thought.
But besides that everything is fairly standard.
--
Comment:
Please remember to preview and use WikiFormatting, and to cc the
maintainer.
--
Ticket URL: <https://trac.macports.org/ticket/26834#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list