Opened 8 years ago

Closed 8 years ago

#51588 closed defect (invalid)

gnupg: make: /Volumes/Macintosh: No such file or directory

Reported by: gurlinthewurld@… Owned by: Ionic (Mihai Moldovan)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: gnupg

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I have been trying to install keybase on my OSX external dev drive. It fails to install gnupg. I ran

sudo port clean gnupg

and

sudo port -v install gnupg

and then to get the details

cat /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/main.log

Is this an issue with my drive's paths? My other ports seem to be fine, and I selfupdate regularly. Thanks in advance.

:info:configure config.status: executing po-directories commands
:info:configure config.status: creating po/POTFILES
:info:configure config.status: creating po/Makefile
:info:configure 
:info:configure                 Version info:   gnupg 1.4.20
:info:configure                 Configured for: Darwin (x86_64-apple-darwin15.5.0)
:info:configure 
:debug:configure Privilege de-escalation not attempted as not running as root.
:debug:build build phase started at Thu Jun  9 13:11:22 EDT 2016
:notice:build --->  Building gnupg
:debug:build Executing org.macports.build (gnupg)
:debug:build Environment: 
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/.CC_PRINT_OPTIONS'
CPATH='/opt/local/include'
LIBRARY_PATH='/opt/local/lib'
MACOSX_DEPLOYMENT_TARGET='10.11'
:debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all'
:debug:build Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all 
:info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20'
:info:build /Volumes/Macintosh HD/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-recursive
:info:build make: /Volumes/Macintosh: No such file or directory
:info:build make: *** [all] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all 
:info:build Exit code: 2
:error:build org.macports.build for port gnupg returned: command execution failed
:debug:build Error code: CHILDSTATUS 12774 2
:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"portbuild::build_main org.macports.build"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"
:info:build Warning: targets not executed for gnupg: org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Please see the log file for port gnupg for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/main.log

Change History (6)

comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Yes, the problem is that you have placed Xcode on a disk that is not your startup disk and whose name contains a space. Most UNIX software, including gnupg and other software that is in MacPorts, does not work with paths that contain spaces.

If Macintosh HD is in fact your startup disk, then you should use xcode-select to select its location as /Applications/Xcode.app/Contents/Developer rather than /Volumes/Macintosh HD/Applications/Xcode.app/Contents/Developer.

comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: keybase gnupg removed
Owner: changed from macports-tickets@… to ionic@…
Summary: Macports port install keybase dependency gnupg failsgnupg: make: /Volumes/Macintosh: No such file or directory

comment:3 Changed 8 years ago by gurlinthewurld@…

Thanks for the reply @ryandesign.

I do in fact use my external dev drive to boot up - won't changing the path disrupt all my other ports, and possibly other installations? I'm researching this now, but please share any info: I am trying to find the Macports documentation re commands to check which Dev Tools and XCode path my ports are referenced to. Please forward any resources. Thanks again!

Last edited 8 years ago by gurlinthewurld@… (previous) (diff)

comment:4 Changed 8 years ago by Ionic (Mihai Moldovan)

In this case, is / located on your external drive and "Macintosh HD" only mounted in /Volumes/? That sounds weird (especially since you must have a full installation of OS X on the external drive - and then another one on the Macintosh HD-labeled partition of the other drive?!)

comment:5 Changed 8 years ago by gurlinthewurld@…

Yes, the / is the dev drive ... from root I can cd to Volumes which has both Macintosh HD and my External Dev drive. Each has its own OS X and its own macports installation. I temporarily took the space out of "Macintosh HD" to perform the port install. After searching around, I eventually (updated XCode on dev and) changed the XCode path.

comment:6 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.