[MacPorts] #38795: Follow-up on ticket 34538
MacPorts
noreply at macports.org
Tue Apr 16 14:11:54 PDT 2013
#38795: Follow-up on ticket 34538
-------------------------------------------+-------------------------------
Reporter: ozanyarman@… | Owner: macports-
Type: defect | tickets@…
Priority: Normal | Status: new
Component: ports | Milestone:
Resolution: | Version: 2.1.3
Port: soprano, graphite2, kdenlive | Keywords:
-------------------------------------------+-------------------------------
Comment (by ryandesign@…):
Replying to [comment:11 ozanyarman@…]:
> I temporarily trashed the TestBigEndian.cmake and its alias
You should delete the alias or symlink in /opt/local/share/cmake/modules,
since MacPorts said it didn't install it. You should not delete the
original in /opt/local/share/cmake-2.8/Modules since MacPorts said that
was installed by the cmake port and is presumably needed for something. If
you already deleted the original from /opt/local/share/cmake-2.8/Modules,
you can get it back by deactivating and re-activating the cmake port:
{{{
sudo port -f deactivate cmake
sudo port activate cmake
}}}
> and the following error occured again at the step where graphite2 was
being installed:
>
> {{{
> :info:configure CMake Error: Error in cmake code at
> :info:configure
/opt/local/share/cmake/modules/CMakeUnixFindMake.cmake:1:
> :info:configure Parse error. Expected a command name, got unquoted
argument with text "book".
> }}}
Looks like the same problem with another file. Do the same thing: find out
if that file was provided by MacPorts; if not, delete it.
> Upon multiple failures these past months in installing KDENLIVE, I had
had installed some weeks ago a CMAKE 2.8-10 Mac OS App, which is in my
Utilities folder now. But it didn't help with stuff either. Perhaps it
made matters worse with installing superfluous .cmake files? Maybe I ought
to do complete overhaul and reinstall a single instance of a CMAKE?
If you would like a separate copy of cmake installed outside of MacPorts,
you're of course welcome to have that, but MacPorts certainly doesn't need
it; MacPorts will use its own version of cmake. One would hope that the
separate copy of cmake would not install any files into the MacPorts
/opt/local directory but I've never used it so I can't say for certain.
> Else, should I do something about the '''macports.conf''' file? Or
should I force all ports to rebuild with '''x86_64''' architecture?
If you have not followed the migration procedures after upgrading to a new
major version of OS X, then yes, you should do so.
Replying to [comment:12 ozanyarman@…]:
> This is my current macports.conf file under /opt/local/etc/macports:
Certainly at least this line is wrong:
{{{
macportsuser root
}}}
Perform the steps in the migration instructions to manually compare your
old macports.conf with the new macports.conf.default and adopt any changes
that we've made in macports.conf.default over the years.
--
Ticket URL: <https://trac.macports.org/ticket/38795#comment:13>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list