I have pushed fixes for this. Let me know if there are still issues. Thanks,
Arnold arn...@skeeve.com wrote: > "Dmitry V. Levin" <l...@altlinux.org> wrote: > > > On Sat, Apr 17, 2021 at 01:43:58PM -0600, arn...@skeeve.com wrote: > > > "Dmitry V. Levin" <l...@altlinux.org> wrote: > > > > > > > I've just tried to build the latest commit gawk-5.1.0-260-gde598391 from > > > > gawk-5.1-stable branch. Unfortunately, the result executable uses a > > > > private glibc interface: > > > > $ nm gawk |grep GLIBC_PRIVATE > > > > U __libc_dynarray_resize@GLIBC_PRIVATE > > > > This makes it unusable at least in GNU/Linux distributions. > > > > > > Can you explain how this makes it unusable? I see this on Ubuntu > > > but the gawk executables run just fine. > > > > > > What, really, is the problem here? I don't understand. > > > > Well, GLIBC_PRIVATE is a private glibc interface intended for use by > > various parts of glibc itself, it can change (and does change from time > > to time) without providing backwards compatibility, any symbol in > > GLIBC_PRIVATE can disappear or change its semantics during glibc update. > > Consequently, packages are not allowed to have dependencies on > > GLIBC_PRIVATE. > > So, the problem is that __libc_dynarray_resize is actually not linked > into gawk, but the executable runs because the local libc happens to > supply the symbol. But since it's "private" to GLIBC, that symbol > being there can't be relied upon. > > OK --- I will work on this. > > Thanks, > > Arnold
