clang does not define _CALL_SYSV, breaking an #ifdef. Remove G_VA_COPY
#ifdef hell taken from an old glib version and define G_VA_COPY as
va_copy(3) instead.
Also remove a trailing whitespace in Makefile.
Improved fix and OK jca@
(which is not) throughout the ports Makefiles.
* Replace find|xargs with find -exec {} +
* Replace -exec {} \; with -exec {} + if applicable.
* Use the -delete operator to remove files and empty directories.
* Combine and tweak some find(1) invocations while here.
ok kn@ rsadowski@ espie@
there may be some missing as my unpacked ports source is a little out of date
but this should catch the main things people might run into
the struct was reordered a second time in sysctl.h r1.192 to improve
compatibility but amd64 snapshot packages made it out before that happened
so the bumps are still needed
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
changes (CPUSTATES/etc). Last part.
- some of these might be in code that's not actually built or rarely
used but it's not worth the hassle evaluating that, i'm just bumping &
moving on.
- as mentioned before, there might still be runtime problems relating
to the addition or renumbering.
and hasn't kept up with ports infrastructure changes so doesn't build as-is.
ok jca@ "kiiilllll" landry@ "I will always vote yes to killing ports" bcallah@
This way we now have only one mono-icon-theme package, and bulk builds
should become happy. We probably got lucky before due to
x11/kde/accessibility3 being always built before x11/kde4/artwork.
