[MacPorts] #39938: Macport 2.2.0 and Valgrind 3.8.1 on OS X 10.8.3 (x64): fatal: "<no name yet>"

[MacPorts]

#39938: Macport 2.2.0 and Valgrind 3.8.1 on OS X 10.8.3 (x64): fatal: "<no name
yet>"
-------------------------+--------------------------------
  Reporter:  noloader@…  |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.2.0
Resolution:  invalid     |   Keywords:
      Port:              |
-------------------------+--------------------------------

Comment (by larryv@…):

 Replying to [comment:2 noloader@…]:
 > Macport was provided su to install the software. Shouldn't it drop
 > privileges during steps like building?

 It does drop privileges, as you can see from your log output.
 {{{
 :debug:main Executing org.macports.main (valgrind)
 :debug:main changing euid/egid - current euid: 0 - current egid: 0
 :debug:main egid changed to: 502
 :debug:main euid changed to: 502
 }}}

 I am not personally familiar with how MacPorts deals with Xcode license
 acceptance. As noted in the wiki page I linked to, it is sometimes
 necessary to accept the license at the system level, but I don’t know why
 this is the case. You could ask on [[MailingLists|macports-users]] if
 you’re curious; maybe someone there can explain.

-- 
Ticket URL: <https://trac.macports.org/ticket/39938#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X