Opened 16 years ago
Closed 14 years ago
#16500 closed defect (fixed)
Error building MacPorts_Framework
Reported by: | dstwo@… | Owned by: | armahg@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | juanger@…, rhwood@…, febeling@…, birdflyin@… | |
Port: | MacPorts_Framework |
Description
---> Fetching MacPorts_Framework ---> Verifying checksum(s) for MacPorts_Framework ---> Extracting MacPorts_Framework ---> Configuring MacPorts_Framework ---> Building MacPorts_Framework Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release" && xcodebuild -target "MacPorts" -configuration Release build OBJROOT=build/ SYMROOT=build/ " returned error 1 Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release: No such file or directory Error: Unable to upgrade port: 1
Change History (10)
comment:1 Changed 16 years ago by blb@…
Cc: | rhwood@… added |
---|---|
Owner: | changed from macports-tickets@… to armahg@… |
Port: | MacPorts_Framework added |
comment:2 Changed 16 years ago by armahg@…
comment:3 Changed 16 years ago by dstwo@…
I tried that, and it still failed:
~ $ sudo port uninstall MacPorts_Framework Password: ---> Deactivating MacPorts_Framework 0.0.1_0 ---> Uninstalling MacPorts_Framework 0.0.1_0 ~ $ sudo port upgrade outdated Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/dsn"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. (you might also see this message if a pseudo-port such as outdated or installed expands to no ports). Error: No port found. ~ $ sudo port install MacPorts_Framework ---> Building MacPorts_Framework Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release" && xcodebuild -target "MacPorts" -configuration Release build OBJROOT=build/ SYMROOT=build/ " returned error 1 Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release: No such file or directory Error: Status 1 encountered during processing. ~ $ sudo port selfupdate MacPorts base version 1.600 installed Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! ~ $ sudo port install MacPorts_Framework ---> Building MacPorts_Framework Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release" && xcodebuild -target "MacPorts" -configuration Release build OBJROOT=build/ SYMROOT=build/ " returned error 1 Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/work/MacPorts_Framework_Release: No such file or directory Error: Status 1 encountered during processing. ~ $
comment:4 Changed 16 years ago by blb@…
Since you updated the Portfile to point to contrib in svn instead of the GSoC branch, and contrib just calls it MacPorts_Framework, the worksrcdir in the Portfile needs updating,
-worksrcdir MacPorts_Framework_Release +worksrcdir MacPorts_Framework
comment:5 Changed 16 years ago by armahg@…
blb thanks for catching that. I made the correction accordingly.
dstwo ... please let me know if it now builds successfully. Also, out of curiousity, what will you be using the Framework for?
comment:6 Changed 16 years ago by dstwo@…
Yep, it worked. I'm actually not sure why the framework was installed on my machine - perhaps it was a dependency of something?
~ $ sudo port selfupdate Password: MacPorts base version 1.600 installed Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! ~ $ sudo port upgrade outdated Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/dsn/Research/PrimShell/trunk"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. (you might also see this message if a pseudo-port such as outdated or installed expands to no ports). Error: No port found. ~ $ sudo port install MacPorts_Framework Password: Portfile changed since last build; discarding previous state. ---> 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.1.0_0 ---> Activating MacPorts_Framework 0.1.0_0 ---> Cleaning MacPorts_Framework
comment:10 Changed 14 years ago by jmroot (Joshua Root)
Cc: | juanger@… added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Replying to dstwo@…:
So I migrated to 10.6 and Xcode 3.2 :P. I guess I now know that something Apple plans to do in the future might break this port. I have moved back to 10.5.4 and Xcode 3.1 and I made some changes to the project and committed them. The port builds fine on my machie. Please attempt a clean install and let me know if that works. Thanks,
George.