NiLuJe / crosstool-ng

A versatile (cross-)toolchain generator.
Other
13 stars 7 forks source link

[Debian Trixie (wsl2)] Cannot install C Library #4

Closed Aryetis closed 1 month ago

Aryetis commented 7 months ago

The installation fails during the "Installing C library" step with

[ALL  ]      mv -f dir-add.texi.new dir-add.texi
[ALL  ]      LANGUAGE=C LC_ALL=C makeinfo libc.texinfo
[ALL  ]      texi2any (XS parser): bug: parent hv not already set
[ALL  ]      
[ALL  ]      /home/aramir/kobo-qt-setup-scripts/koxtoolchain/build/kobo/.build/arm-kobo-linux-gnueabihf/buildtools/bin/makeinfo: line 2: 28578 Aborted                 /usr/bin/makeinfo --force "${@}"
[ALL  ]      for file in libc.info*; do   /home/aramir/kobo-qt-setup-scripts/koxtoolchain/build/kobo/.build/tools/bin/install -c -m 644 $file /home/aramir/x-tools/arm-kobo-linux-gnueabihf/arm-kobo-linux-gnueabihf/sysroot/usr/share/info/$file; done
[ALL  ]      /usr/bin/install: cannot stat 'libc.info*': No such file or directory
[ERROR]      make[3]: *** [Makefile:200: /home/aramir/x-tools/arm-kobo-linux-gnueabihf/arm-kobo-linux-gnueabihf/sysroot/usr/share/info/libc.info] Error 1
[ALL  ]      make[3]: Leaving directory '/home/aramir/kobo-qt-setup-scripts/koxtoolchain/build/kobo/.build/src/glibc-2.15/manual'
[ERROR]      make[2]: *** [Makefile:221: manual/subdir_install] Error 2
[ALL  ]      make[2]: Leaving directory '/home/aramir/kobo-qt-setup-scripts/koxtoolchain/build/kobo/.build/src/glibc-2.15'
[ERROR]      make[1]: *** [Makefile:10: install] Error 2
[ALL  ]      make[1]: Leaving directory '/home/aramir/kobo-qt-setup-scripts/koxtoolchain/build/kobo/.build/arm-kobo-linux-gnueabihf/build/build-libc-final/multilib'

/home/aramir/x-tools/arm-kobo-linux-gnueabihf/arm-kobo-linux-gnueabihf/sysroot/usr/share/info/ is an empty folder

NiLuJe commented 1 month ago

Probably a WSL issue. Something like that sounds vaguely similar, specifically with a specific range of texinfo versions that horribly implode on some glibc docs.

Aryetis commented 1 month ago

Probably, could not reproduce the issue next time I installed my setup. Closing the issue.