#14004 closed defect (worksforme)
Failure to activate MacPorts_Framework.
Reported by: | grahamperrin@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: | MacPorts_Framework |
Description
sudo port install pallet ---> Fetching MacPorts_Framework ---> Verifying checksum(s) for MacPorts_Framework ---> Extracting MacPorts_Framework ---> Configuring MacPorts_Framework ---> Building MacPorts_Framework ---> Staging MacPorts_Framework into destroot ---> Installing MacPorts_Framework 0.0.1_0 ---> Activating MacPorts_Framework 0.0.1_0 Error: Target org.macports.activate returned: Image error: /Library/Frameworks/MacPorts.framework/Headers already exists and does not belong to a registered port. Unable to activate port MacPorts_Framework. Error: The following dependencies failed to build: MacPorts_Framework Error: Status 1 encountered during processing.
If it's relevant: I had previously set aside then restored
/usr/local/include/db.h
to allow installation of subversion.
Change History (8)
comment:1 follow-up: 3 Changed 17 years ago by afb@…
comment:2 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
Milestone: | → Port Bugs |
---|---|
Summary: | Target org.macports.activate returned: Image error: /Library/Frameworks/MacPorts.framework/Headers already exists and does not belong to a registered port. Unable to activate port MacPorts_Framework. → Failure to activate MacPorts_Framework. |
comment:3 Changed 17 years ago by grahamperrin@…
Replying to afb@macports.org:
multiple installations of the MacPorts.framework ?
Not knowingly, this is a relatively clean installation. AFAIR the only thing I have done since my most recent clean installation of MacPorts on this MacBook Pro is attempt to produce a disk image of wv.
Remove the one you have installed yourself, or -f the activation of the port to move it aside...
[macbookpro03:~] gjp22% sudo port uninstall MacPorts_Framework ---> Deactivating MacPorts_Framework 0.0.1_0 ---> Uninstalling MacPorts_Framework 0.0.1_0 [macbookpro03:~] gjp22% sudo port -f install MacPorts_Framework ---> Fetching MacPorts_Framework ---> Verifying checksum(s) for MacPorts_Framework ---> Extracting MacPorts_Framework ---> Configuring MacPorts_Framework ---> Building MacPorts_Framework ---> Staging MacPorts_Framework into destroot ---> Installing MacPorts_Framework 0.0.1_0 ---> Activating MacPorts_Framework 0.0.1_0 ---> Cleaning MacPorts_Framework
that seems OK, but then
sudo port install pallet fails.
comment:4 Changed 17 years ago by jmroot (Joshua Root)
Cc: | grahamperrin@… removed |
---|---|
Owner: | changed from macports-tickets@… to rhwood@… |
Assigning to maintainer.
comment:5 Changed 17 years ago by rhwood@…
Status: | new → assigned |
---|
There are some Googe Summer of Code applications that will affect the MacPorts_Framework, so I'm holding off on fixing it until that process gets worked out.
comment:6 Changed 16 years ago by rhwood@…
Owner: | changed from rhwood@… to macports-tickets@… |
---|---|
Status: | assigned → new |
comment:7 Changed 16 years ago by blb@…
Port: | MacPorts_Framework added |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
The framework saw lots of work during 2008's GSoC (see MacPorts.Framework_Roadmap); speak up if this occurs with 0.1.0 of MacPorts_Framework.
db44/db.h isn't relevant, but it seems you have multiple installations of the MacPorts.framework ?
Remove the one you have installed yourself, or -f the activation of the port to move it aside...