Opened 7 years ago

Closed 7 years ago

#54334 closed defect (invalid)

MacPorts 2.4.1 claims Xcode command line tools are not installed, but they are

Reported by: chrisscooke Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.4.1
Keywords: Cc:
Port: dsniff

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

Trying to install "dsniff" claims that Xcode command line tools are not installed.

Christopher-Cookes-MacBook-Air:~ chriscooke$ sudo port install dsniff
Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build.
Warning: Install them by running `xcode-select --install'.
--->  Computing dependencies for dsniff
--->  Configuring dsniff
Error: Failed to configure dsniff, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_dsniff/dsniff/work/dsniff-2.4/config.log
Error: Failed to configure dsniff: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_dsniff/dsniff/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port dsniff failed

But the command line tools are installed:

Christopher-Cookes-MacBook-Air:~ chriscooke$ xcode-select -p
/Applications/Xcode.app/Contents/Developer

I have Xcode 8.3.2.

Also, I cannot fill in the maintainer in the CC because the port info command claims this port doesn't exist, even though trying to install the port seems to try to install the port (as seen above):

Christopher-Cookes-MacBook-Air:~ chriscooke$ port info --maintainer dnsiff
Error: Port dnsiff not found

Change History (9)

comment:1 Changed 7 years ago by Schamschula (Marius Schamschula)

Two things:

1) what does which gcc tell you?

2) dsniff is nomaintainer, i.e. has no maintainer

comment:2 Changed 7 years ago by chrisscooke

1) which gcc returns: Christopher-Cookes-MacBook-Air:~ chriscooke$ which gcc /usr/bin/gcc

2) if dsniff has nomaintainer, then the maintainer command should say that instead of "dsniff not found". So that is yet another bug in macports.

comment:3 Changed 7 years ago by ctreleaven (Craig Treleaven)

2)

CT-MBP11:libass craigtreleaven$ port info --maintainer dnsiff
Error: Port dnsiff not found
CT-MBP11:libass craigtreleaven$ port info --maintainer dsniff
maintainer: 

comment:4 in reply to:  3 Changed 7 years ago by Schamschula (Marius Schamschula)

Replying to ctreleaven:

2)

CT-MBP11:libass craigtreleaven$ port info --maintainer dnsiff
Error: Port dnsiff not found
CT-MBP11:libass craigtreleaven$ port info --maintainer dsniff
maintainer: 

Interesting:

I tend to be too lazy to type in port info --maintainer dnsiff, so I just type port info dnsiff, and as part of the full output it correctly gives me

Maintainers: none

comment:5 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: port xcode command line tools removed

Running xcode-select -p does not prove that the command line tools are installed. Please (re)install the command line tools.

The port name is "dsniff" not "dnsiff".

Once you've installed the command line tools, clean dsniff and try again. If it fails, attach the main.log file.

comment:6 in reply to:  2 Changed 7 years ago by Schamschula (Marius Schamschula)

Replying to chrisscooke:

1) which gcc returns: Christopher-Cookes-MacBook-Air:~ chriscooke$ which gcc /usr/bin/gcc

Sorry, I misread your first entry, i.e. I thought you meant to use xcode-select -p to set the path, rather than to retrieve the path.

Are you sure you are using the correct version of Xcode for your OS? i.e. the right Toolchain?

2) if dsniff has nomaintainer, then the maintainer command should say that instead of "dsniff not found". So that is yet another bug in macports.

comment:7 Changed 7 years ago by chrisscooke

Yes, I was using -p to print, not -s to set. If xcode-select -p tells you the path of the tools, but that doesn't prove that you have them, then what does prove it?

When I do:

sudo xcode-select --install

A popup comes up saying "The xcode-select command requires the command line developer tools. Would you like to install them now?" That sounds like I don't have the tools. So I click the "Install" button, and accept the license that comes up. Then a progress popup appears, which says "Finding software". The progress bar never moves. I left it there for an hour when I first tried (after the port command said I didn't have Xcode tools). Eventually I hit the stop button. A search on the internet implied that this often happens when you already have the command line tools. In any event, I don't know how to uninstall them without uninstalling all of Xcode, in order to try again. I have Sierra, and a very recently installed Xcode, so I'm not sure what good a reinstall of Xcode would do anyway (it's already a pretty new install). What I have is:

OSX: macOS Sierra 10.12.5 Xcode: version 8.3.2 (8E2002) command line tools: from Xcode, Xcode menu : Preferences : Locations tab, setting Command Line Tools: Xcode 8.3.2 (8E2002) The Command Line Tools is a select list, but only this one item is in it. It matches the Xcode version.

I think I'm just about done trying to get Macports to work. I was using it because I expected it to be an easier way to install a package, but it is turning out to more trouble than it's worth.

comment:8 Changed 7 years ago by chrisscooke

OK, I have it figured out. The xcode-select --install command does not work. I don't know why. In order to install the command line tools I had to get it from the developer's site. From the Xcode menu in Xcode, I chose "Open Developer Tool" and then "More Developer Tools...". This took me to a downloads page on the developer site, where I needed to login, and then I was able to find command line tools for Xcode 8.3.2. (the url was: https://developer.apple.com/download/more/?=for%20Xcode). After running this installer, Macports ran fine.

comment:9 Changed 7 years ago by ctreleaven (Craig Treleaven)

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