to GCC 4.8.3.

Part II, Bump PORTREVISIONs.

PR:		192025
Tested by:	antoine (-exp runs)
Approved by:	portmgr (implicit)

- Bump portrevision as most docs was unreadable

to GCC 4.8.3.

This entails updating the lang/gcc port as well as changing the default
in Mk/bsd.default-versions.mk, and it replaces the CONFLICT between the
lang/gcc and lang/gcc47 ports by lang/gcc48.

GCC now uses C++ as its implementation language and performs more
aggressive loop analysis which can be disabled via the
-fno-aggressive-loop-optimizations command-line option.

Compilation of extremely large functions has been signficantly improved,
as have interprocedural optimizations.

A new optimization level -Og has been introduced.  It addresses the need
for fast compilation and a superior debugging experience while providing
a reasonable level of run-time performance.  This should be better
suitable for development than the default -O0.

A new local register allocator (LRA) has been implemented, which replaces
the 26 year old reload pass and improves generated code quality. For now
it is active on the x86 and x86-64 targets.

AddressSanitizer, a fast memory error detector, has been added and can be
enabled via -fsanitize=address.

Each diagnostic emitted now includes the original source line and a caret
indicating the column.

The new option -Wpedantic is an alias for -pedantic, which is now deprecated.

The C++ frontend and associated run-time library libstdc++ have gained
support for many additional C++11 features.  As with previous releases
the Fortrand frontend has seen many improvements as well.

Support for the AArch64 has been added, and there are many improvements
to the x86/x86-64 backend and others.

See http://gcc.gnu.org/gcc-4.8/changes.html for an extense list of changes;
http://gcc.gnu.org/gcc-4.8/porting_to.html for information on how to port
to that new version.

PR:		192025
Tested by:	antoine (-exp runs)

PR:		191132
Submitted by:	andrew.hotlab@hotmail.com, jcm@visi.com (maintainer) [1]

PR:		193484
Submitted by:	ohartman (zedat.fu-berlin.de)
Too much TLC:	marino

ChangeLog:
- xml: br.weather.com: location fixed
- xml: de.weather.com: location fixed
- xml: fr.weather.com: location fixed
- xml: in.weather.com: links fixed
- xml: pogodynka.pl: fixes
- xml: weather.com.cn: fixed

dependencies.

- Remove DOCS conditions

- Switch from gnomehack to pathfix

can be deleted entirely due to the Mate Desktop 1.8 import, but I'm leaving
that for someone who was involved in that import.

Announcement with ChangeLog:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2014q3/008793.html

Submitted by:	portscout

  Release notes: http://sourceforge.net/p/tcllib/mailman/message/32817224/
- Update LICENSE information

- Do not overwrite config.php with and empty file on install

New ports: textproc/rubygem-elasticsearch, textproc/rubygem-elasticsearch-api, textproc/rubygem-elasticsearch-transport:

Ruby integrations for Elasticsearch that feature:

* a client for connecting to an Elasticsearch cluster
* a Ruby API for the Elasticsearch's REST API
* various extensions and utilities

WWW: https://rubygems.org/gems/elasticsearch

- Drop .la files, no dependees require them

Approved by:	portmgr blanket

- USES=kmod and simplify

- Clarify License
- Use shebangfix rather than manual post-patch

- Add LICENSE_FILE
- Bump dependent ports as .so version has changed

Approved by:	portmgr blanket

FATAL: /usr/ports/MOVED: malformed line at 7077.
 =>
WARN: /usr/ports/MOVED: seems to have unnecessary blank lines at the last part.

- Shebangfix

Changes:
- New @dir keyword
- @dirrm/@dirrmtry will now expose a warning in DEVELOPER_MODE
- directories outside of PREFIX are now automatically handled
- Determine the running OS version from /bin/sh not uname so that
pkg doesn't think a jail running on a newer host is an OS upgrade
- Remove libyaml
- The plist now entirely default on owner root, group wheel
- Add more regressions tests

- Fix in CegoQueryHelper::evalAttrCond. In some table ordering cases,
  the attributes had been switched and the evaluation was wrong
  ( LESS_THAN, MORE_THAN, LESS_EQUAL_THAN, MORE_EQUAL_THAN ).

Submitted by:	Björn Lemke <lemke@lemke-it.com>