Pierre Neidhardt skribis: > If we are going for a SBCL-specific solution, I believe that all > references are stored in plain text files at some points (the .asd files > and the .lisp files) which are often encoded in ASCII / UTF-8, so > searching these files without having to deal with their encoding might > be enough. But of course this is less general and more brittle. A store reference to a C library in a standalone Lisp binary can come either from the current package or from some dependencies (cl+ssl, cl-cffi-gtk, etc.). So we would need to scan the source code of all the Lisp dependencies recursively to get the full list of store refrences. And as Mark wrote below, with the current grafting code, this list of store references will not solve grafting for paths that are in UTF-32 or both in ASCII and UTF-32 in the binary file. Ludovic Courtès skribis: > Mark H Weaver skribis: > >> Pierre Neidhardt writes: >>> - The main recommendation for an easy fix without updating the scanner >>> is that we tweaked our build system to dump the store reference to a >>> separate ASCII file. >> >> Sounds good. I made a similar proposal in Dec 2018, earlier in this >> thread . I wrote: >> >> If you don't want to change the daemon, it could be worked around in our >> build-side code as follows: we could add a new phase to certain build >> systems (or possibly gnu-build-system) that scans each output for >> UTF-16/32 encoded store references that are never referenced in UTF-8. >> If such references exist, a file with an unobtrusive name would be added >> to that output containing those references encoded in UTF-8. This would >> enable our daemon's existing reference scanner to find all of the >> references. >> >> Our grafting code would then need to be extended to recognize and >> transform store references encoded in UTF-16/32 as well as UTF-8. > > Oh thanks for the reminder. > > The separate ASCII file doesn’t solve it all because, as you write, we’d > need to change the grafting code as well. > > Then it might be simpler to use a “byte vector” data type for those > strings. We’ll have to wait for Pierre’s patches to get a better idea. > :-) I'm not sure what you mean with the "byte vector" data type here. Could you explain what you're thinking about with a few more details?