Marcin Cieslak writes:
> Dag-Erling Smørgrav writes:
> > Marcin Cieslak writes:
> > > I think this (useful) change should go into the future release
> > > notes as a new feature.
> > Which change?
> https://reviews.freebsd.org/D32306 Import _FORTIFY_SOURCE
> implementation from NetBSD which intr
On Tue, 21 May 2024, Dag-Erling Smørgrav wrote:
Marcin Cieslak writes:
I think this (useful) change should go into the future release notes
as a new feature.
Which change?
https://reviews.freebsd.org/D32306 Import _FORTIFY_SOURCE implementation from
NetBSD
which introduced _memcpy_chk and
Marcin Cieslak writes:
> I think this (useful) change should go into the future release notes
> as a new feature.
Which change?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
On Tue, May 21, 2024 at 12:16 AM Dag-Erling Smørgrav
wrote:
The purpose of UPDATING is to document changes that break backward
compatibility, i.e. running old binaries on a newer world.
happened here is that you tried to run newer binaries on an older world,
On Tue, 21 May 2024, Warner Losh w
On Tue, May 21, 2024 at 12:16 AM Dag-Erling Smørgrav
wrote:
> Marcin Cieslak writes:
> > I have updated some binary packages using pkg(8) but neglected to
> > rebuild the world and my favourite web browsers no longer started
> > complaining about the undefined symbol __memcpy_chk@FBSD_1.8
> >
>
Marcin Cieslak writes:
> I have updated some binary packages using pkg(8) but neglected to
> rebuild the world and my favourite web browsers no longer started
> complaining about the undefined symbol __memcpy_chk@FBSD_1.8
>
> Would that be a good idea to add that information to the Handbook and
>
Hello,
I have updated some binary packages using pkg(8)
but neglected to rebuild the world and my favourite
web browsers no longer started complaining
about the undefined symbol __memcpy_chk@FBSD_1.8
Would that be a good idea to add that information
to the Handbook and possible bump FreeBSD_vers
