ffmpeg --devel 2.1
libmpd: move URL from SourceForge.

Tarballs have been removed from SourceForge and are now hosted directly by musicpd.org.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
mpdscribble: move URL from SourceForge.

Tarballs have been removed from SourceForge and are now hosted directly by musicpd.org.

Closes #23915.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
ledger: remove unneeded HEAD patch.

The patch has been pushed upstream, so it is not needed any longer.

Closes #23903.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
Android SDK 22.3

Closes #23920.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Elixir 0.11.0

Closes #23918.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Postgres-XC: add compatibility with OS X 10.9.

Closes #23919.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Undocument --use-gcc and friends

These options are deprecated in favor of --cc=<compiler>, so there is no
need to continue advertising their existence.
Remove --use-gcc and friends from completion scripts
wine: update older clang warning
Move gtkglextmm to the boneyard

This software no longer builds against recent changes in glibmm. Its
git repository hasn't had a commit in over two years and a release in
over four.

Closes #21333.
sysbench: fix audit warning
Move superenv make_fuss output back to stderr

In 6e3a585607116d06f47aac2ff5a649f2898216f0 ("Improve superenv
add/remove message."), more debugging information was added to the
"make_fuss" output generated by the superenv compiler
wrapper.

This resulted in some breakage in configure scripts that inspect stderr,
so in e1bd9b9e980c433878e60833f09964b8ca996657 ("Don't use stderr for
make_fuss output."), the output was moved to stdout. This only appeared
to solve the problem, since stdout is buffered but stderr is not.

Later, in fb749e47509b77b5bd89e7b14f0a1097d4af7f40, Homebrew started
generating logs even in verbose mode. This had the side effect of moving
stdout/stderr from a TTY to a pipe, and thus stdout was no longer
line-buffered.

Since it was not line-buffered, and Ruby's internal buffers were not
flushed, the debug output was being lost. This was addressed in
2d5724af8613c820b8c14f4171fe1de6a17f10c3 ("cc: ensure wrapper output is
always flushed").

This caused stdout to be flushed during configure, which resurfaced the
original bug that prompted e1bd9b9e980c433878e60833f09964b8ca996657.
This was fixed by disabling the debug output during configure, in
f1779837a46a58520560fba3850a0e2992284d0a.

Since the original bug has been addressed in a more robust way, we can
move the debug output back to stderr.

Fixes #23923.
Doctor: fix check_access_logs

Fixes #23936.
Plowshare git20131102

Closes #23921.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>