URL: <https://savannah.gnu.org/support/?110550>
Summary: File expected to be at /usr/bin/file, isn't on ChromeOS Project: GNU Libtool Submitted by: None Submitted on: Sun 17 Oct 2021 04:47:52 AM UTC Category: None Priority: 5 - Normal Severity: 3 - Normal Status: None Privacy: Public Assigned to: None Originator Email: Open/Closed: Open Discussion Lock: Any Operating System: GNU/Linux _______________________________________________________ Details: I'm a developer for Chromebrew, a package manager for ChromeOS. We've had a problem with most all configure scripts: `file` is expected at `/usr/bin/file`, but ChromeOS doesn't ship with `file`, so we have to provide it at `/usr/local/bin/file`. `./configure` scripts generated with `autoconf` are unaware of this and, instead of looking for the location of `file`, raise an error: ./configure: line 6712: /usr/bin/file: No such file or directory This particular error is an example from the latest version of `libsigsegv` I thought this was an `autoconf` bug, hence the bug report filed here <https://savannah.gnu.org/support/index.php?110549> but as it turns out, this is trickling down from `libtool`, specifically the files `ltmain.sh` and `libtool.m4` Autoconf and libtool are both at latest versions (2.71 and 2.4.6 respectively) As I've never reported a bug of this type, I don't know what other information would be helpful (logs, etc.), so please don't hesitate to let me know. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/support/?110550> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/