necessarily compatible (E.g. binutils-2.25 does not define PARAMS). Adjust
the include path priority so the internal ansidecl.h gets precedence, allowing
cp-demangle.c to use libiberty.h without compilation errors.
The removed hunk is definitely wrong, but I can't figure out what it was
trying to do. I think the patch hunk was accidentally reintroduced in r1.4
after being correctly removed in r1.3.
The reason it is wrong is because it breaks later tests by introducing code
into confdefs.h. The following tests always break, because they have
duplicate main() definitions.
Build test on NetBSD works because the java support isn't in the suggested
options anyway.
* Fixes regressions, revive parts removed at "Fix build under OpenBSD/amd64 5.5"
* Drop default behaviour changes and local features from OpenBSD ports,
it break other platforms, at least, NetBSD-6.0/i386.
* Remove needless patches after "Restore monolithic gcc48 and gcc48-libs".
* Convert gcc48 to simple meta-pkg
* Potentially fix non-NetBSD packaging
* Fix gcc48-libs/gcc48-cc++ build under OpenBSD/amd64 5.5
* Enable graphite option, from wip/gcc48snapshot via Xiyue Deng
* Tweak nls option
Changelog:
GCC 4.8.3
This is the [35]list of problem reports (PRs) from GCC's bug tracking
system that are known to be fixed in the 4.8.3 release. This list might
not be complete (that is, it is possible that some PRs that have been
fixed are not listed here).
Support for the new powerpc64le-linux platform has been added. It
defaults to generating code that conforms to the ELFV2
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
handler). Make precompiled headers work on NetBSD hosts (by choosing a
hopefully stable virtual address for precompiled header symbol tables).
Both reported upstream.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
