DDD is the Data Display Debugger, a common graphical front-end for
GDB, DBX, and XDB debuggers.
DDD is an Motif application that besides the "usual" features such as viewing
source texts and breakpoints, DDD provides a _graphical_data_display_, where
data structures are displayed as graphs. A simple mouse click dereferences
pointers or reveals structure contents. Complex data structures can be
explored incrementally and interactively, using automatic layout if
preferred. Each time the program stops, the data display reflects the
current variable values.
Data Display Debugger requires pty(4) functionality to talk to GDB, so
make sure to either load appropriate kernel module or use custom kernel
with pty(4) compiled in.
WWW: http://www.gnu.org/software/ddd/
===> The following configuration options are available for ddd-3.3.12_2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove expired ports:
2019-07-31 security/rubygem-googleauth06: Use security/rubygem-googleauth
instead
2019-07-31 devel/ddd: does not work with modern gdb
2019-07-31 devel/py-pip-tools2: Use devel/py-pip-tools instead
2019-07-31 lang/cint: Abandonware; superseded by lang/cling
Deprecate devel/ddd
It does not work with modern gdb.
While here reset MAINTAINER.
PR: 238984, 226827
Approved by: maintainer timeout (~1.5 years based on PR 226827)
Reported by: jhb
Fix devel/ddd after fallout from libXt update.
Stricter type rules mean that you can't pass a non-noreturn function
as a parameter to a function expecting a noreturn-function. Error
reported by Antoine was
exit.C:815:12: error: no matching function for call to 'XtAppSetErrorHandler'
(void) XtAppSetErrorHandler(app_context, ddd_xt_error);
because ddd_xt_error had the wrong attribute (non-noreturn). So add
that in, and add it to goto_main_loop() as well, where it makes sense
because that uses longjmp() and doesn't return.
Reported by: antoine
Reviewed by: zeising
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
MASTER_SITES cleanup.
- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.
While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.
Also, replace some EXTRACT_SUFX occurences with USES=tar:*.
Checked by: make fetch-urlall-list
With hat: portmgr
Sponsored by: Absolight
Add OPTIONS_DEFINE=DOCS for ports with %%PORTDOCS%% in the plist.
Where possible, correct a few instances where PORTDOCS was being used
to flag stuff in EXAMPLESDIR. For some ports, mostly those owned by
ruby@, PORTDOCS is applied to pretty much everything whether it's
documentation or example.
Fix build at 10.x.
While here:
. use stage phase;
. use MKDIR macro instead of INSTALL -d one to create a directory;
. unmute install command.
PR: ports/182315
Submitted by: Sergio Mangialardi <sergio@softshark.org> (maintainer)
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Update to 3.3.12 and silence a long standing bug in how
DDD handles controlling terminals for child processes.
No response from maintainer since: Sat, 22 Aug 2009
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Chase freelibiberty header files location move which removed CONFLICTS
with libgnugetopt. This resolves port build under most FreeBSD port
installations where libgnugetopt is already installed.
Approved by: marcus (portmgr)
Ding-dong, this is your friendly happy face talking. Please to be
reading the 20040314 entry in /usr/ports/CHANGES regarding importing
of ports into the tree that require the use of GNU autotools.
Thanks awfully
UPDATE: ddd-3.3.1 to 3.3.8
The port was marked broken, but compiled anyway when BROKEN=
was commnted out. I took it upon myself to fix it so the
lates version builds.
For whatever reason the libiberty configure script bombs.
Instead of patching/and fixing it I added a dependency on
devel/freelibiberty. That solves that problem.
Cleaned up the installation of PORTDOCS in the Makefile and
pkg-plist.
Regenerated all the patch files since many of the original
ones had no contextual lines and would apply without error
where the patch should have bombed. So the following patch
files are to be removed:
PR: ports/63473
Submitted by: Yarema <yds@CoolRat.org>
Approved by: Maintainer timeout
Fix build in 5.x branch: configure is not detecting streampos
correctly, circumvent that. Provide a proper auto* tools related
solution later
PR: 52983
Submitted by: David Yeske <dyeske@yahoo.com>
Fix build in 5.x branch: configure is not detecting streampos
correctly, circumvent that. Provide a proper auto* tools related
solution later
PR: 52983
Submitted by: David Yeske <dyeske@yahoo.com>
Move inclusion of bsd.port.pre.mk later in the file for conditional BROKEN
tag. Early inclusion caused problems for some ports, so to be safe I'm
updating all of them.
Pointy hat to: kris
Use ${ECHO_CMD} instead of ${ECHO} where you mean the echo command; the ECHO
macro is set to "echo" by default, but it is set to "true" if make(1) is
invoked with the -s option while ECHO_CMD is always set to the echo command.
Change motif to a normal dependency. REQUIRES_MOTIF is now called USE_MOTIF
and generates a LIB_DEPENDS to x11-toolkits/open-motif. As before, it implies
USE_XPM (and therefore USE_XLIB). Motif-dummy is removed from
PKG_IGNORE_DEPENDS, whose sole resident is now XFree86-3.
Fix an annoying (but apparently benign) error dialog that seems to be a result
of some changes Luoqi Chen made to src/sys/kern/tty_pty.c at revs 1.58 and
1.59, apparently to resolve some sort of race condition. (Search for EAGAIN in
that file if you'd like to see).
(1) Add new variable, XFREE86_VERSION, to specify which version of XFree86
(3 or 4) to depend to when USE_XLIB is set. XFREE86_VERSION defaults to 3
for now, but adventurous users can override it in /etc/make.conf. When
XFREE86_VERSION=3, USE_XLIB will add a dependency to x11/XFree86; when it
is set to 4, the dependency will be to x11/XFree86-4-libraries. When
XFREE86_VERSION=4, the PKG_IGNORE_DEPENDS and ALWAYS_BUILD_DEPENDS hacks
to avoid messing with XFree86 are turned off.
