**DISPUTED**A failure in the -fstack-protector feature in GCC-based toolchains
that target AArch64 allows an attacker to exploit an existing buffer
overflow in dynamically-sized local variables in your application
without this being detected. This stack-protector failure only applies
to C99-style dynamically-sized local variables or those created using …
VuXML only (0) · listed, port not fixed yet
None. pkg audit reports nothing for this version.
Fixed (0)
No VuXML entries for this package.
Commits (40)
Tijl Coosemans (tijl) · 11.3.0_3
*/*: Use C.UTF-8 locale
Ports 02f27a83b44d fixed the ports tree to the C locale so it would work
correctly in environments where users use a locale that isn't compatible
with the C locale, e.g. xx_YY.UTF-8 where [A-Z] includes more than just
upper case letters. USE_LOCALE was introduced to let ports use another
locale if they needed it. The C.UTF-8 locale was created later on to be
mostly compatible with the C locale.
Switch the ports tree locale to C.UTF-8 and remove USE_LOCALE. The
world has moved to Unicode so all ports either require it or know how to
build correctly in a Unicode environment.
PR: 295945
Exp-run by: antoine
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
devel/aarch64-none-elf-gcc: fix build with libc++ 17
When building relatively recent gcc ports (with C++ in them) against
libc++ 17, you get errors similar to:
In file included from /wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/cp/module.cc:208:
In file included from /wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/system.h:239:
In file included from /usr/include/c++/v1/vector:321:
In file included from /usr/include/c++/v1/__format/formatter_bool.h:20:
In file included from /usr/include/c++/v1/__format/formatter_integral.h:32:
In file included from /usr/include/c++/v1/locale:202:
/usr/include/c++/v1/__locale:546:5: error: '__abi_tag__' attribute only applies to structs, variables, functions, and namespaces
546 | _LIBCPP_INLINE_VISIBILITY
| ^
/usr/include/c++/v1/__config:813:37: note: expanded from macro '_LIBCPP_INLINE_VISIBILITY'
813 | # define _LIBCPP_INLINE_VISIBILITY _LIBCPP_HIDE_FROM_ABI
| ^
/usr/include/c++/v1/__config:792:26: note: expanded from macro '_LIBCPP_HIDE_FROM_ABI'
792 | __attribute__((__abi_tag__(_LIBCPP_TOSTRING(_LIBCPP_VERSIONED_IDENTIFIER))))
| ^
In file included from /wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/cp/module.cc:208:
In file included from /wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/system.h:239:
In file included from /usr/include/c++/v1/vector:321:
In file included from /usr/include/c++/v1/__format/formatter_bool.h:20:
In file included from /usr/include/c++/v1/__format/formatter_integral.h:32:
In file included from /usr/include/c++/v1/locale:202:
/usr/include/c++/v1/__locale:547:37: error: expected ';' at end of declaration list
547 | char_type toupper(char_type __c) const
| ^
/usr/include/c++/v1/__locale:553:48: error: too many arguments provided to function-like macro invocation
553 | const char_type* toupper(char_type* __low, const char_type* __high) const
| ^
/wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/../include/safe-ctype.h:146:9: note: macro 'toupper' defined here
146 | #define toupper(c) do_not_use_toupper_with_safe_ctype
| ^
This is because gcc/system.h includes safe-ctype.h which redefines ctype
macros such as toupper, tolower, etc to "poison" them.
However, it should only include the safe-ctype.h header *after* any C++
headers, such as <list>, <map>, <string>, etc, otherwise these might
transitively include internal ctype headers (such as with libc++ 17),
causing the above conflicts.
This commit moves the safe-ctype.h inclusion to later in gcc/system.h,
which solves this issue, and makes it possible to build against libc++
17.
PR: 274040
Approved by: manu (maintainer)
MFH: 2023Q3
devel/aarch64-none-elf-gcc: Work around aarch64 extraction bug
Extraction fails with poudriere on aarch64 with the following error:
=> SHA256 Checksum OK for gcc-11.3.0.tar.xz.
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Error exit delayed from previous errors.
Enforcing the use of bsdtar works around the issue.
The issue is specific to lang/gcc11 and lang/gcc12: no other GCC port is affected.
Apply the same fix used to fix bug #271052.
PR: 273194
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
devel/arm-none-eabi-gcc: More flexible multilib options
This patch introduces port build options to control GCC's multilib
layout. It defaults to "disable multilib" as the port used to be set
before.
In order to build a compiler suitable for Cortex-M devices, select the
"Optimized for Cortex-M/R" option instead.
A subsequent patch to devel/arm-none-eabi-newlib will automatically
create their pkg-plist which now depends on the multilib option
chosen.
Reviewed by: manu
Differential Revision: <https://reviews.freebsd.org/D32638>
Update to MPC version 1.2.0 with the following changes: - New functions: . mpc_sum . mpc_dot - Several functions are more robust with a reduced exponent range (for example corresponding to IEEE 754 binary formats). - New mpcheck tool for comparison with the native C library (which is not installed by default).
Bump all directly dependent ports. Do not bump those indirectly
dependent via the lang/gcc* family since their run-time dependencies
and code generated should not be affected.
PR: 249950
Submitted by: wen
aarch64-none-elf-gcc: Remove the include-fixed directory
Those includes are, afaict, useless and cause problems if one build from a
custom FreeBSD without IPFILTER.
Do what the other gcc packages do and simply remove them.
PR: 230199 239210
devel/aarch64-none-elf-gcc: Add binutils dependency
Building the plugins require a native objdump, all arches have one except for
aarch64 so add a dependency on devel/binutils@native in case the arch doesn't
have objdump installed.
devel/aarch64-none-elf-gcc: Fix building plugins
For building plugins gcc needs objdump, whcih exists in amd64 world but
not on aarch64. We already have a dependancy on devel/binutils but this
port install binaries in ${LOCALBASE}/${GCC_TARGET}/bin so add that to
the PATH.
Reported by: Mark Millard
devel/aarch64-none-elf-gcc: Enable the plugins
The plugins now build fine on a native build for aarch64 so enable
and install them unconditionally for all arches.
Reported by: Mark Millard
Update aarch64-none-elf-gcc and slave ports to 8.4.0
This updates :
devel/aarch64-none-elf-gcc
devel/arm-none-eabi-gcc
devel/riscv32-unknown-elf-gcc
devel/riscv64-none-elf-gcc
For now keep a distinfo file for each ports, when we know taht
we can updated them all together we will remove it and use only
the master port distinfo file.
devel/aarch64-none-elf-gcc: parameterise PORTVERSION
Needed by devel/riscv64-none-elf-gcc to build a different version of GCC for
RISC-V.
Submitted by: kp
Sponsored by: Axiado
Reviewed by: bapt
Update binutils to 2.33.1
While here, convert binutils into flavors, that ease a lot maintenance
and helps cleaning out the code.
This is inspired by the same work on going on the xtoolchained gcc by jhb@
PR: 241756
Exp-run: antoine (portmgr)
Discussed with: jhb
Differential Revision: https://reviews.freebsd.org/D22258
Divorce the ARM bare-metal GCC ports from the FreeBSD GCC xtoolchain ports.
In the past, changes to the FreeBSD GCC xtoolchain ports have broken
the ARM bare-metal GCC ports by accident. In addition, we'd like to
move to having multiple FreeBSD GCC xtoolchain ports for different GCC
versions. It seems best if we make the two groups of ports
independent so that changes to one do not affect the other.
Reviewed by: manu
Differential Revision: https://reviews.freebsd.org/D22064
devel/aarch64-none-elf-gcc: Unbreak on arm64
The plugins ae not built on arm64.
While we might want them in the future, we also need gcc on this platform
as it's the compiler used for u-boot.
Reviewed by: jhb, kan
Approved by: kan (maintainer)
Upgrade ext-toolchain GCC ports to GCC 6.4.0
This is the latest supported release in GCC 6.x series.
Drop aarch64 support patch - it has been committed upstream.
Enable ifunc suppport by default.
PR: 228161
Reviewed by: bapt (update part)
Differential Revision: https://reviews.freebsd.org/D13602
Fix arm-none-eabi-gcc/aarch64-none-elf-gcc plist after r466699
jhb fixed these ports in r466699, but include-fixed headers has changed
since the last update, perhaps due to --sysroot and these ports being built
differently since then.
Add the extra headers to the plist and bump PORTREVISION due to package
differences. This fixes some sanity checking in the plist, since these files
are installed to the stage dir.
Reported by: Phillip R. Jaenke <prj@rootwyrm.com>
Approved by: ler (ports)
MFH: 2018Q2
Fix two more issues with r465416.
- Force build of a cross-compiler by defining CROSS_DIRECTORY_STRUCTURE
in CFLAGS even if the build host matches the build target. This
fixes such a cross compiler to not include /usr/local/lib in its default
library path (e.g. amd64-gcc when built on amd64).
- Don't remove the include-fixed headers for the aarch64-none-elf-gcc
and arm-none-eabi-gcc packages.
- Bump PORTREVISION.
Reported by: kevans (2)
Reviewed by: bdrewery, kevans
Differential Revision: https://reviews.freebsd.org/D14925
Mark the gcc crosscompiler ports as broken on various tier-2 archs.
Unfortunately neither the maintainer or I have time at the moment
to chase down all of these failures. The "fails to package" ones
ought to be fairly easy to fix.
Discussed with: maintainer
Add the aarch64-none-elf-binutils and aarch64-none-elf-gcc ports. These are useful for bare-metal development, for example to build U-Boot.
Approved by: imp
Differential Revision: https://reviews.freebsd.org/D4137