Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 May 2024 08:15:52 +0200
From:      =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>
To:        Marcin Cieslak <saper@saper.info>
Cc:        current@FreeBSD.org
Subject:   Re: __memcpy_chk family of functions
Message-ID:  <86msojvgfb.fsf@ltc.des.dev>
In-Reply-To: <20qspnq2-8qp0-pq49-rq65-986n0q4r6rqq@fncre.vasb> (Marcin Cieslak's message of "Mon, 20 May 2024 21:26:41 %2B0000")
References:  <20qspnq2-8qp0-pq49-rq65-986n0q4r6rqq@fncre.vasb>

next in thread | previous in thread | raw e-mail | index | archive | help
Marcin Cieslak <saper@saper.info> 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
> possible bump FreeBSD_version and add this info to UPDATING?

The purpose of UPDATING is to document changes that break backward
compatibility, i.e. running old binaries on a newer world.  What
happened here is that you tried to run newer binaries on an older world,
an issue of _forward_ compatibility, which we've never promised.
Besides, an entry in UPDATING wouldn't have helped you since your source
tree predated the change that would have added it.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86msojvgfb.fsf>