gdb @7.6 Staging into destroot failed

[nimrodomer@…]

If I configure MacPorts with --prefix=$HOME/.local, gdb installs just fine. However, if I configure MacPorts with --prefix=$HOME/.local and with --with-no-root-privileges, it will not. The relevant part from the logfile:

:debug:destroot Executing proc-post-org.macports.destroot-destroot-0
:info:destroot chgrp: you are not a member of group procmod
:info:destroot Command failed: chgrp procmod /Users/deaddork/.local/var/macports/build/_Users_deaddork_.local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gdb/gdb/work/destroot/Users/deaddork/.local/bin/ggdb*
:info:destroot Exit code: 1
:error:destroot org.macports.destroot for port gdb returned: command execution failed
:debug:destroot Error code: NONE
:debug:destroot Backtrace: command execution failed
    while executing
"$post $targetname"
:info:destroot Warning: targets not executed for gdb: org.macports.activate org.macports.destroot org.macports.install

I am using a mid-2012 MacBook Air with Maverick. The install command I used: port install gdb.

I gather from the log file that I need to be part of group ProcMod in order to install gdb in Maverick. This is unfortunate, as I would rather not install code as root. FYI I did not have any problems installing gdb in Mountain Lion with --with-no-root-privileges.

Thank you in advance!

[cooljeanius (Eric Gallager)]

Cc Me!

[frozencemetery (Robbie Harwood)]

Cc Me!

[mf2k (Frank Schima)]

dweber has retired. See #43834.

Is this a base issue?

[posita (Matt Bogosian)]

Cc Me!

[posita (Matt Bogosian)]

See also #48648 (possible dup: similar issue, but with complete main.log from @7.9.1).

[posita (Matt Bogosian)]

Here's a possible work-around (for systems with dseditgroup):

% # add current user to procmod
% sudo dseditgroup -o edit -a "$( whoami )" -t user procmod
% port install gdb
...
% # remove user from procmod
% sudo dseditgroup -o edit -d "$( whoami )" -t user procmod

Adapted from ​this source. You'll still get this warning after installation:

You will need to make sure /System/Library/LaunchDaemons/com.apple.taskgated.plist has the '-p' option, e.g.
            <key>ProgramArguments</key>
            <array>
                    <string>/usr/libexec/taskgated</string>
                    <string>-sp</string>
            </array>

Due to kernel caching, you usually need to restart Mac OS X for this option to effect.

But at least it installs.

If you're curious about the motivation of the warning, see ​this explanation. See also these, which explain an alternate approach based on creating and trusting your own self-signed certificate and using it to codesign gdb:

• ​http://stackoverflow.com/questions/13913818/how-to-get-a-codesigned-gdb-on-osx
• ​http://ntraft.com/installing-gdb-on-os-x-mavericks/

[mf2k (Frank Schima)]

#53744

[mf2k (Frank Schima)]

has duplicate #48648.

[raimue (Rainer Müller)]

gdb notes hint at codesigning as of [380ef99dde4cec0516cba66797d478ff0d97239d/macports-ports] (#54217) and no longer needs chgrp to procmod.