Opened 10 years ago
Closed 10 years ago
#47095 closed defect (fixed)
GQRX mdmg build fails
Reported by: | macports@… | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: | gqrx |
Description
I'm trying to build an mdmg package of GQRX to install on a different OSX box.
Everything seems to build ok, but the issue is in constructing the final package. It seems a file is missing.
The command I give is :
sudo port mdmg gqrx +xquartz
It fails after a while with this in the error log:
:info:pkg cp: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_gqrx/gqrx/work/gqrx-20150307-component.pkg: No such file or directory :info:pkg Command failed: cp -PR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_gqrx/gqrx/work/gqrx-20150307-component.pkg /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_gqrx/gqrx/work/mpkg_packages :info:pkg Exit code: 1 :error:pkg org.macports.mpkg for port gqrx returned: command execution failed :debug:pkg Error code: CHILDSTATUS 66797 1 :debug:pkg Backtrace: command execution failed while executing "system "cp -PR ${pkgpath} ${packages_path}"" (procedure "package_mpkg" line 55) invoked from within "package_mpkg $subport $epoch $version $revision" (procedure "portmpkg::mpkg_main" line 9) invoked from within "portmpkg::mpkg_main org.macports.mpkg" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:pkg Warning: targets not executed for gqrx: org.macports.mdmg org.macports.mpkg :notice:pkg Please see the log file for port gqrx for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_gqrx/gqrx/main.log
The file gqrx-20150307-component.pkg isn't created anywhere. Copying gqrx-20150307.pkg to gqrx-20150307-component.pkg fails with an error relating to bundles, so I'm guessing it's not the right answer.
I've cleaned GQRX prior to building, I've gone in and wiped out the build directory too, but I still eventually get the same error.
Any ideas?
David
Attachments (2)
Change History (14)
comment:1 follow-up: 2 Changed 10 years ago by mf2k (Frank Schima)
Keywords: | gqrx mdmg removed |
---|---|
Owner: | changed from macports-tickets@… to michaelld@… |
comment:2 Changed 10 years ago by macports@…
Replying to mf2k@…:
In the future, please use Cc the port maintainers (
port info --maintainers gqrx
), if any.
My apologies.
David
comment:3 follow-up: 4 Changed 10 years ago by michaelld (Michael Dickens)
Can you attach the fail log? That might help.
comment:4 Changed 10 years ago by macports@…
Replying to michaelld@…:
Can you attach the fail log? That might help.
Is the attached log the one you wanted?
David
comment:5 follow-up: 6 Changed 10 years ago by michaelld (Michael Dickens)
Yes, that's the log. I haven't had time to try out this command yet. Have you tried creating an mdmg of any other port(s)? Do they work, or do they fail similarly?
comment:6 Changed 10 years ago by macports@…
Replying to michaelld@…:
Yes, that's the log. I haven't had time to try out this command yet. Have you tried creating an mdmg of any other port(s)? Do they work, or do they fail similarly?
I've been able to build disk images for gpredict and for rtl-sdr with no problems - just tested that. I did manage to find a copy of packaagemanager.app which has stopped the warnings in the log, but the error still persists.
comment:7 Changed 10 years ago by michaelld (Michael Dickens)
Hmm .. yes, I see what you mean. I get the same error when trying even "sudo port mdmg rtl-sdr". I'm guessing this is a MacPorts bug. I'll ping some MP devs to look further into this.
comment:8 follow-up: 9 Changed 10 years ago by michaelld (Michael Dickens)
OK; a little more progress. You have to have PackageMaker.app installed either into a place where MacPorts expects it, or you need to set "packagemaker_path" to be the full path to and including "PackageMaker.app", e.g., "/Applications/Utilities/PackageMaker.app" (but without the """s). According to "/opt/local/etc/macports/macports.conf",
# Path to PackageMaker.app # It may be necessary to set this with Xcode >= 4.3, as that version # requires PackageMaker to be installed manually from the Auxiliary Tools for # Xcode disk image. The default is /Applications/PackageMaker.app with Xcode # 4.3 and ${developer_dir}/Applications/Utilities/PackageMaker.app with older # versions.
So, what I did was comment in the line starting with "packagemaker_path", and set it to the correct path. This did the trick for me; hopefully it will for you too.
comment:9 Changed 10 years ago by macports@…
Replying to michaelld@…:
OK; a little more progress. You have to have PackageMaker.app installed either into a place where MacPorts expects it, or you need to set "packagemaker_path" to be the full path to and including "PackageMaker.app", e.g., "/Applications/Utilities/PackageMaker.app" (but without the """s). According to "/opt/local/etc/macports/macports.conf",
# Path to PackageMaker.app # It may be necessary to set this with Xcode >= 4.3, as that version # requires PackageMaker to be installed manually from the Auxiliary Tools for # Xcode disk image. The default is /Applications/PackageMaker.app with Xcode # 4.3 and ${developer_dir}/Applications/Utilities/PackageMaker.app with older # versions.So, what I did was comment in the line starting with "packagemaker_path", and set it to the correct path. This did the trick for me; hopefully it will for you too.
Installing packagemaker.app does get rid of the warning s about not being able to find it, but still doesn;t let the gqrx mdmg be built. The failure is still :
:info:pkg cp: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_gqrx/gqrx/work/gqrx-20150307-component.pkg: No such file or directory :info:pkg Command failed: cp -PR /opt/local/var/macports/build
I've had a look, but I can't see where gqrx-20150307-component.pkg is suposed to be built, just looks like it's trying to copy a file that is never made.
I've attached the full build log again, now that the packagemaker warnings/errors are gone.
Changed 10 years ago by macports@…
Attachment: | main.2.log added |
---|
With the packagemaker warnings gone.
comment:10 follow-up: 11 Changed 10 years ago by michaelld (Michael Dickens)
There should be calls to PackageMaker.app interspersed throughout the log. So, I don't think the "packagemaker_path" setting is correct. Where is PackageMaker.app located on your install? Have you edited "/opt/local/etc/macports/macports.conf" to reflect this location in the "packagemaker_path" variable? If not, please do the edit, then "clean gqrx" and try again.
comment:11 Changed 10 years ago by macports@…
Replying to michaelld@…:
There should be calls to PackageMaker.app interspersed throughout the log. So, I don't think the "packagemaker_path" setting is correct. Where is PackageMaker.app located on your install? Have you edited "/opt/local/etc/macports/macports.conf" to reflect this location in the "packagemaker_path" variable? If not, please do the edit, then "clean gqrx" and try again.
That got it!
Looks like it built correctly, I'll test the resulting image this eve on the target computer.
Many thanks. David
comment:12 Changed 10 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Excellent! YW.
In the future, please use Cc the port maintainers (
port info --maintainers gqrx
), if any.