ports clang for ports that explicitly use clang to compile.
So put COMPILER_LINKS for those, so that we get the requested compiler, along
with -B support.
Noticed some oddities in WANTLIB for a few ports (libc++ and libc++abi which
had no business being there), this fixes the issue.
ok benoit@
The Algol 68 Genie project preserves and promotes Algol 68 out of
educational as well as scientific-historical interest, by making
available a recent checkout compiler-interpreter written from scratch
together with extensive documentation for both the language and this new
implementation. Algol 68 Genie is a fast compiler-interpreter which
ranks among the most complete implementations of the language.
ok juanfra@
Gravity is a powerful, dynamically typed, lightweight, embeddable
programming language written in C without any external dependencies
(except for stdlib). It is a class-based concurrent scripting language
with modern Swift-like syntax.
Gravity supports procedural programming, object-oriented programming,
functional programming and data-driven programming. Thanks to special
built-in methods, it can also be used as a prototype-based programming
language.
This mirrors a change made to base gcc4.2 by martynas@ in 2014.
https://marc.info/?l=openbsd-ports&m=149656580518245&w=2
Includes an independent fix from upstream for gcc6, currently unlinked
from builds
Also, stop installing libssp as it broken on OpenBSD as it tries to use gets()
pirofti@ ok'd an earlier version, suggestions from sthen@
"doesn't look dangerous" espie@
"pretty astounding" deraadt@
search path to ${WRKDIR}/bin. Ensures that the ld wrapper script needed
for USE_WXNEEDED gets used (clang was ignoring it otherwise).
Rework ccache support and gcc4/clang MODULES to use the same wrapper
generator as above, setting up a list of command names (cc, c++, etc) and
destinations (egcc, eg++, etc) as the port is processed, and writing the
wrappers in one place in bsd.port.mk, with an optional wrapper (e.g.
ccache), and with an echo to make it clear on screen/in log which
compiler binaries were chosen (easier than inspecting the wrapper
scripts) and whether ccache is used.
Initial wrapper using -B from espie, ccache bits from me, discussed
with/ok espie. Been through a bulk on i386.
Otherwise, the PostScript versions of the man pages may
be created or not during build, depending on wether groff
is installed or not, which may lead to consusion when
updating this port.
Suggested by Ingo a few days ago.
This requires three changes:
- OpenBSD clang produces __guard_local symbols that are marked as hidden,
which causes problems with the go linker. Workaround this by explicitly
making __guard_local symbols visible when reading in an ELF object.
- OpenBSD clang currently fails to correctly report the compiler runtime
via --print-libgcc-file-name. Workaround this issue by hardcoding it
for the time being.
- The TestCgoConsistentResults test passes successfully outside of ports,
however fails under a ports build. This requires further investigation
but we can just skip the test for now.
However, this is not enough, because if groff is installed,
the .ps files will be generated. I'll have a look on how to
completely disable the use of groff here, as suggested by
Ingo.
