From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#33848: Store references in SBCL-compiled code are "invisible" Date: Thu, 27 Dec 2018 23:59:12 +0100 Message-ID: <87r2e28tkv.fsf@gnu.org> References: <87r2e8jpfx.fsf@gnu.org> <877eg0i43j.fsf@netris.org> <87d0psi1xo.fsf@gnu.org> <874lb3kin6.fsf@ambrevar.xyz> <87sgynezha.fsf@gnu.org> <87tvj2yesd.fsf@netris.org> <877efwe04u.fsf@gnu.org> <8736qji7c1.fsf@ambrevar.xyz> <87tvizvzgk.fsf@netris.org> <87o9979gfn.fsf@gnu.org> <87tvizgghs.fsf@ambrevar.xyz> <87k1juaomo.fsf@gnu.org> <87muoqhk62.fsf@ambrevar.xyz> <87zhsq8wkj.fsf@gnu.org> <87d0pmhbgn.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38002) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcehI-0002ri-1A for bug-guix@gnu.org; Thu, 27 Dec 2018 18:04:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcedG-0007wK-9F for bug-guix@gnu.org; Thu, 27 Dec 2018 18:00:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:41383) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gcedG-0007vc-3Z for bug-guix@gnu.org; Thu, 27 Dec 2018 18:00:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gcedF-0007xg-Rn for bug-guix@gnu.org; Thu, 27 Dec 2018 18:00:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d0pmhbgn.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 27 Dec 2018 23:05:44 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Pierre Neidhardt Cc: 33848@debbugs.gnu.org Pierre Neidhardt skribis: >> The reference scanner, currently written in C++, traverses whole >> directory trees. Being C++ it treats file names as byte arrays so it >> doesn=E2=80=99t matter what the file name encoding is. > > But what matters then is that the filename encodings on the filesystem an= d in the > binary match, right? I=E2=80=99m not sure what you call =E2=80=9Cthe binary=E2=80=9D. Do you me= an the nar? Ludo=E2=80=99.