ports/184008: gdb with the python option produces a package that uses bogus stagedir path
Jean-Paul Calderone
jean-paul at hybridcluster.com
Fri Nov 15 21:00:03 UTC 2013
>Number: 184008
>Category: ports
>Synopsis: gdb with the python option produces a package that uses bogus stagedir path
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Nov 15 21:00:02 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Jean-Paul Calderone
>Release: 9.1
>Organization:
HybridCluster
>Environment:
FreeBSD node011.hcdev1.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254707+5afe1ee: Mon Oct 21 17:59:04 UTC 2013 root at node003.testing.hybrid-cloud.com:/usr/obj/usr/src/sys/DTRACE amd64
>Description:
Building gdb 7.6.1 from ports with this option:
.if ${.CURDIR:N*/ports/devel/gdb} == ""
OPTIONS_SET+= PYTHON
.endif
appears to properly enable gdb's Python integration but does so with a bogus default path for some of the support files. When running the resulting gdb, this output is included in the startup blob:
Python Exception <type 'exceptions.ImportError'> No module named gdb:
warning:
Could not load the Python gdb module from `/wrkdirs/usr/ports/devel/gdb/work/stage/usr/local/share/gdb761/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.
The correct path which should be used instead is /usr/local/share/gdb761/python.
Launching gdb with --data-directory=/usr/local/share/gdb761/ suppresses this error and appears to make everything work fine.
>How-To-Repeat:
1) Build gdb 7.6.1 from ports with PYTHON enabled
2) Install the resulting package
3) Run gdb from the resulting package
4) See a warning from gdb
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list