bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FTB if path to build dir contains a space


From: Alexander Batischev
Subject: FTB if path to build dir contains a space
Date: Sat, 27 Feb 2021 22:32:49 +0300

Hi!

I co-maintain Rust bindings for GNU gettext[1]. As conventional among Rust libraries (so-called "crates"), we also provide a crate that bundles GNU gettext and builds it if the user hasn't already installed it by some other means. A while ago, we got a bug report[2] which states that GNU gettext fails to build if the path to the build directory contains a space character.

1. https://crates.io/crates/gettext-rs
2. https://github.com/Koka/gettext-rs/issues/9 I just reproduced this on Debian testing with GNU gettext 0.21, outside of our crate and Rust. Arguments to ./configure were:

--without-emacs --disable-java --disable-csharp --disable-c++ --disable-shared --enable-static --enable-fast-install --with-included-gettext --with-included-glib --with-included-libcroco --with-included-libunistring

Is this indeed a limitation in autotools, like the bug report states? Can this be worked around somehow by you, or should I move the build to something like /tmp?

(Please CC me in replies, as I'm not subscribed to the list.)

--
Regards,
Alexander Batischev

PGP key 356961A20C8BFD03
Fingerprint: CE6C 4307 9348 58E3 FD94  A00F 3569 61A2 0C8B FD03

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]