distcc is a program to distribute compilation of C code across
several machines on a network. distcc should always generate the
same results as a local compile, is simple to install and use, and
is often significantly faster than a local compile.
Unlike other distributed build systems, distcc does not require all
machines to share a filesystem, have synchronized clocks, or to
have the same libraries or header files installed. Machines can be
running different operating systems, as long as they have compatible
binary formats or cross-compilers.
distcc sends the complete preprocessed source code across the network
for each job, so all it requires of the volunteer machines is that
they be running the distccd daemon, and that they have an appropriate
compiler installed.
This package comes with a text-based monitor to inspect the load on
the cluster, and how it is distributed among the various distcc nodes.
===> The following configuration options are available for distcc-3.4_3:
AVAHI=off: Zeroconf support via Avahi
CLANGLINK=on: Create clang compiler links if clang is installed
DOCS=on: Build and/or install documentation
IPV6=on: IPv6 protocol support
LLVMLINK=off: Create llvm compiler links if llvm is installed
PUMP=on: Distribute compilation as well as preprocessing to distcc servers
===> Use 'make config' to modify these settings
*/*: De-orbit alias.mk
Mk/Uses/alias.mk was an attempt for compat with DPorts, but has rotted.
This feature was never documented in the PHB, so there is no work to
be done by the docs@ team.
Nothing against DragonFly, but if DPorts still needs FreeBSD 9
support, they really should work that out with upstream projects.
Ultimately, we don't need to keep carrying this outdated feature that
doesn't affect us.
python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
(Only the first 15 lines of the commit message are shown above )
devel/distcc: Patch small bugs
- Fix GUI option not working and made it a flavor
- Fix service not starting
- Improve default options
- Update available compilers masquerade
- Create proper pkg-plist
- Use pyXY- pkg prefix when pump mode is compiled with non-default python
version
- Take maintainership
PR: 281706
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
cleanup: remove '$MCom' tag
gnome@ no longer uses Marcusom as their staging ground.
Approved by: gnome (nc)
Differential Revision: https://reviews.freebsd.org/D35866
devel/distcc: update to 3.3.3
Update to 3.3.2 in r475448 was wrong because GH_TAGNAME was not updated
accordingly.
This was spotted by ngie@ who provided the first version to move to 3.3.3
See https://github.com/distcc/distcc/releases for changes from 3.1 to 3.3.3
Submitted by: ngie@
Reported by: ngie@
Reviewed by: 0mp, fernape@, mat@
Approved by: 0mp
Differential Revision: https://reviews.freebsd.org/D21259
GOOGLE_CODE has gone away.
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
- Reset maintainership per skreuzer.
- Install desktop and icon files when GNOME or GTK option is set. [1]
- Fix pidfile when 'distccd_flags' variable is not set by the user.
- Replace COMPILER_LINKS option with CLANGLINK and LLVMLINK options. Note
these are turned off by default unlike COMPILER_LINKS. Actually, these are
equivalent to options for devel/ccache as they are often jointly used.
- Modernize and clean up the port.
PR: 185426 [1]
Add USES=alias to several ports
Alias is a new USES tool that allows DragonFly to masquerade as FreeBSD
by setting CFLAGS+= -D__FreeBSD__. For some ports, this fixes the build
without the need for additional patches.
Approved by: portmgr (bapt, blanket)
devel/distcc: Fix mistake made during optionsNG conversion
Not only is it not necessary to include both bsd.port.pre.mk and
bsd.port.options.mk, it actually causes problems like double inclusion
when other ".include" keywords are encountered. While here, convert
USE_GMAKE too, both under the "Just fix it" blanket.
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Remove more tags from pkg-descr files fo the form:
- Name
em@i.l
or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.
- 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
- Provide symlinks for clang and llvm-gcc compilers as well
- Provede links for latest gcc versions
- While here, use GOOGLE_CODE abbreviation for eye candy
Modify the rc script to run after ldconfig has been run due to a dependency
on libpopt.0.so
PR: ports/149068
Submitted by: Carsten Bäcker <carbaecker@gmx.de>
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 )
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
Presenting GNOME 2.20.1 and all related works for FreeBSD. The official
GNOME 2.20 release notes can be found at
http://www.gnome.org/start/2.20/notes/en/ . Beyond that, this update
includes the new GIMP 2.4 (courtesy of ahze).
The GNOME 2.20 update also includes a huge change in the FreeBSD GNOME
hierarchy. We are now using the more standard DATADIR of ${PREFIX}/share
rather than ${PREFIX}/share/gnome. The result is that fewer patches and
hacks are needed to port GNOME components to FreeBSD. This will mean some
user changes may be required, so be sure to read /usr/ports/UPDATING for
more details.
This release and the things we accomplished in it would not have been
possible without mezz's crazy idea to collapse DATADIR, and his persistence
to make it happen successfully. Ahze and pav also deserve thanks for
(Only the first 15 lines of the commit message are shown above )
Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
Maintainer Update: devel/distcc
devel/distcc 2.16 -> 2.18.3
http://distcc.samba.org/ftp/distcc/distcc-2.18.3.NEWS
Consists mostly of bug fixes. Only one change in the way distcc
works. You must specify a network on which connections are
allowed, connections from all networks will still be admitted
but connections outside the specified network will be logged
and dropped.
The 127.0.0.0/8 network is the default for the port. All
existing users and all new users will need to update/add a
distccd_flags variable in /etc/rc.conf, a template for which
can be found in the rc.d script.
Perhaps a new variable, which simply contained the trusted
network address would be better, like
distccd_network="192.168.10.2/24"
PR: ports/75718
Submitted by: Dominic Marks <dom@helenmarks.co.uk>
In same cases (e.g. gnome 1.4 installed), if you don't want to have
the gnome monitor, the install failed due to remaining auto detection
stuff.
Reported by: Andrew Heybey <ath@niksun.com>
Submitted by: Clement Laforet <sheepkiller@cultdeadsheep.org>
