gcc5: Fix quickworld.

When copying the Makefile from gcc47, the writing of a comment line to
configargs.h about it being a generated file was removed, but the output
redirection was not adjusted to

gcc5: Fix quickworld.

When copying the Makefile from gcc47, the writing of a comment line to
configargs.h about it being a generated file was removed, but the output
redirection was not adjusted to create the file from scratch.

This led to quickworld just appending to the existing header in /usr/obj
and resultant build errors.

show more ...

Remove non-existant .PATH components from a number of Makefiles.

iconv sync 8/x: FreeBSD SVN 281550

Remove the const qualifier from iconv(3) to comply with POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/iconv.html
Adjust all code that calls icon

iconv sync 8/x: FreeBSD SVN 281550

Remove the const qualifier from iconv(3) to comply with POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/iconv.html
Adjust all code that calls iconv

Note: The libcpp Makefile cflag was added because the host iconv.h
header was getting pulled in. This always should have been the
src version of iconv.h, but the error wasn't exposed until now.

show more ...

Version number changes for 4.3-DEVELOPMENT.

gcc50: bump version date to 25 May 2015

The base compiler gains all the fixes over the last 5 weeks since
GCC 5.1 was released. This could fix a couple of issues in dports.

WORLD_CCVER: Fix buildworld with clangXX

The backtrace library requires unwind.h to build. This file was never
created, so the base GCC's would fall back to the version in /usr/libdata.
Clang compi

WORLD_CCVER: Fix buildworld with clangXX

The backtrace library requires unwind.h to build. This file was never
created, so the base GCC's would fall back to the version in /usr/libdata.
Clang compilers from ports don't have unwind.h so they were failing on the
world build (building gcc50). This modification makes unwind.h available
for backtrace.c and allows the build to complete with WORLD_CCVER=clang36

show more ...

cryptsetup(8): Remove -std=gcc89 and make getline()'s prototype visible.

Set gcc50 as the primary compiler, gcc47 as secondary

Per request, rather than define NO_GCC47 to prevent the building of the
secondary compiler, the new variable is called NO_ALTCOMPILER. This
wil

Set gcc50 as the primary compiler, gcc47 as secondary

Per request, rather than define NO_GCC47 to prevent the building of the
secondary compiler, the new variable is called NO_ALTCOMPILER. This
will avoid some disruption in the future where the actual version is not
important, only the desire to avoid the secondary compiler.

show more ...

gcc50: Update to release version 5.1.0 => 5.1.1

Immediately after the release was tagged, another commit was added that
changed the version to 5.1.1. Other than the version differing by 0.0.1,
this

gcc50: Update to release version 5.1.0 => 5.1.1

Immediately after the release was tagged, another commit was added that
changed the version to 5.1.1. Other than the version differing by 0.0.1,
this version is identical to what the GCC just released.

show more ...

gcc50: Upgrade to GCC 5.1 release candidate plus

while here:
* remove 4+ Mb of unused texi files from contrib
* update the 3 man pages from Release candidate
* Change makefiles to not take man

gcc50: Upgrade to GCC 5.1 release candidate plus

while here:
* remove 4+ Mb of unused texi files from contrib
* update the 3 man pages from Release candidate
* Change makefiles to not take man pages from contrib directory

After thinking about it, I've decided to continue to update GCC from
Subversion sources rather than limit updates to designated releases. This
is the reason the man pages are not taken from contrib; they are only
present in actual releases and not the SVN repository. The plan is to
only update the man pages when GCC minor version is released.

This is the first (and likely only) release candidate for GCC5. It will
be known as gcc 5.1.0, but CCVER will remain at "gcc50" regardless if the
version of gcc is 5.1.1 or 5.4.2. This includes changes up to SVN 222168
(April 17).

show more ...

Remove texinfo from base

At this point, the only info files left in DragonFly are from texinfo
itself. Due to a similar effort on FreeBSD 11, the ports are already
prepared for the lack of texinfo

Remove texinfo from base

At this point, the only info files left in DragonFly are from texinfo
itself. Due to a similar effort on FreeBSD 11, the ports are already
prepared for the lack of texinfo utilities in base.

show more ...

groff: Remove info page

Initially I converted the groff info page until groff.7, but then I
realized that groff.7 already existed and serves as an adequate
alternative to the groff info page. Thus,

groff: Remove info page

Initially I converted the groff info page until groff.7, but then I
realized that groff.7 already existed and serves as an adequate
alternative to the groff info page. Thus, this commit simply removes
the installation of the info page (one of the last in base)

show more ...

gdb: Remove 4 info pages (2 converted to man pages)

GDB had four info pages: gdb, gdbint, stabs, and annotate. They have been
removed.

* gdb.info : There has always been a man page gdb.1 wh

gdb: Remove 4 info pages (2 converted to man pages)

GDB had four info pages: gdb, gdbint, stabs, and annotate. They have been
removed.

* gdb.info : There has always been a man page gdb.1 which is an
adequate replacement for gdb.info
* stabs.info : This has been converted to stabs.7 with info2man
* gdbint.info : This has been converted to gdbint.7 with info2man
* annotate.info : This was always obsolete[1], so it was not replaced

[1] From annotate info page: This document describes the obsolete level
two annotation interface implemented in older GDB versions.

show more ...

diffutils: Remove redundant info page

The three diff binaries all have their own man pages, so the
diffutils.info file is redundant. For now a copy of it remains in
contrib/diffutils/doc, but it is

diffutils: Remove redundant info page

The three diff binaries all have their own man pages, so the
diffutils.info file is redundant. For now a copy of it remains in
contrib/diffutils/doc, but it is being removed from the base system.

show more ...

grep: remove "redundant" info page

Grep already has an adequate man page, so we can remove info page without
losing much.

gcc47: Remove info pages

The info pages from gcc50 are not installed due to limited use and the
fact all the information is readily available on the web. Removing info
pages from gcc47 matches gcc5

gcc47: Remove info pages

The info pages from gcc50 are not installed due to limited use and the
fact all the information is readily available on the web. Removing info
pages from gcc47 matches gcc50 and moves us closer to removing texinfo.

show more ...

binutils 2.24: Remove info pages

The info pages from binutils 2.25 are not installed (if they were, they
would overwrite 2.24 versions anyway). Both "as" and "ld" have sufficient
man pages. There

binutils 2.24: Remove info pages

The info pages from binutils 2.25 are not installed (if they were, they
would overwrite 2.24 versions anyway). Both "as" and "ld" have sufficient
man pages. There is not equivalent "binutils" man page, but this
information is readily available on the internet, which is the same
justification used for not importing gcc50 info pages.

show more ...

cvs: Remove info pages (one converted to man page)

As the start of an effort to remove info pages and texinfo from the
system, the cvsclient info page has been converted to a man page.
The cvs info

cvs: Remove info pages (one converted to man page)

As the start of an effort to remove info pages and texinfo from the
system, the cvsclient info page has been converted to a man page.
The cvs info page was not converted since it appears to be equivalent
to the already existing man page.

Entries were added to Makefile_upgrade.inc, but when all the info pages
are gone, those entries will be replaced by a single directory line -
to remove /usr/share/info

show more ...

gcc50: Update to 02 APR 2015 snapshot (SVN 221845)

Fix gold linker 2.25

The trick of dumping target files to libgold did not work. The gold
linker was missing all of it's targets and emulations. This new approach
uses a custom build target to avoid

Fix gold linker 2.25

The trick of dumping target files to libgold did not work. The gold
linker was missing all of it's targets and emulations. This new approach
uses a custom build target to avoid building common c++ object files
twice.

show more ...

cross-tools stage: Don't build unused linker (i.e. gold)

Only one linker is used to build the world, but each version of binutils
normally installs two linkers. Update the build infrastructure to s

cross-tools stage: Don't build unused linker (i.e. gold)

Only one linker is used to build the world, but each version of binutils
normally installs two linkers. Update the build infrastructure to skip
building one linker for the cross-tools version of binutils. This is
normally the gold linker, which builds very slowly due to being written
in c++.

This change could be backported to binutils 2.24, but right now it only
applies to binutils 2.25, the version normally used to build world.

show more ...

Set binutils 2.25 as primary version

Binutils 2.24 is now the backup version.

ld-225: fix ldscripts (allows binutils 2.25 to build world)

Replace binutils 2.22 with latest binutils 2.25

There are several active Common Vulnerabilities and Exposures (CVE) on
binutils version 2.24 and earlier. As far as I can tell, there are no
known vu

Replace binutils 2.22 with latest binutils 2.25

There are several active Common Vulnerabilities and Exposures (CVE) on
binutils version 2.24 and earlier. As far as I can tell, there are no
known vulnerabilities with Binutils 2.25 (released late Dec 2014).

While here, maximumize parallelism by splitting binutils into three
serial blocks. Previously binutils built serially with the build on the
gold linker (c++) particularly obvious.

The commit only replaces the ALTBINUTILS (version 2.22). Once it is
confirmed that world builds without issue using version 2.25, it will
become prime and binutils 2.24 will become ALTBINUTILS.

The active vulnerability list:
* CVE-2012-3509 possible DOS (crash) (2.22 only)
* CVE-2014-8484 possible DOS (out of bounds read)
* CVE-2014-8485 possible DOS (crash) and code execution
* CVE-2014-8501 possible DOS (out of bounds write) and unspecified impacts
* CVE-2014-8502 possible DOS (crash) and unspecified impacts
* CVE-2014-8503 possible DOS (crash) and unspecified impacts
* CVE-2014-8404 possible DOS (crash) and unspecified impacts
* CVE-2014-8737 allows local users to arbitrarily delete files
* CVE-2014-8738 possible DOS (crash, invalid write)

show more ...

gdb(1), kgdb(1): Rework makefile to prevent repeated rebuilding

The beforedepends target was done in such a way that caused gdb and
kgdb to rebuild with every quickworld. This commit rearranges thi