[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TexInfo] Compatibility to glibc 2.34
|
From: |
Gavin Smith |
|
Subject: |
Re: [TexInfo] Compatibility to glibc 2.34 |
|
Date: |
Fri, 14 Jan 2022 19:32:26 +0000 |
|
User-agent: |
Mutt/1.9.4 (2018-02-28) |
On Fri, Jan 14, 2022 at 06:22:38PM +0100, Hilmar Preuße wrote:
> Yes, I noticed that gnulib in Debian builds fine w/ glibc 2.34. However I
> didn't notice that the issue is solved in texinfo repo already. I just
> noticed that the files modified by my patch still look the same in texinfo
> repository. It is
> https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=c9ade3f83d4fba7a0fbdca87c21f860cffd5f8a4
> right?
>
> Many thanks!
>
> Hilmar
I am not sure what you mean. Are you saying that the issue isn't fixed
in Texinfo yet?
I don't regularly import new gnulib versions, but do it before a new release.
As it might be useful for testing, I am trying to import recent gnulib
changes. I have been unable to do it so far, though, getting an error
message
checking whether we can build Perl extension (XS) modules... yes
checking for eslint... no
checking for tsc... no
checking for uglifyjs... no
checking for modernizr... no
checking for prove... prove
checking parser tests requirements... yes
checking Perl Texinfo API texinfo documentation build requirements... yes
checking Pod::Simple::Texinfo tests requirements... yes
checking that generated files are newer than configure... done
configure: error: conditional "LIBUNISTRING_COMPILE_UNIWIDTH_WIDTH" was never
defined.
Usually this means the macro was only invoked conditionally.
I am trying to investigate.