[sr #110549] File expected to be at /usr/bin/file, isn't on ChromeOS

[Daniel Macks]

Follow-up Comment #1, sr #110549 (project autoconf):

That use of /usr/bin/file seems to come from the libtool.m4 and/or ltmain.sh
files that get imported when 'configure' is generated. Those files are part of
the libtool package. So the bug needs to be fixed there, and then that fix
will propagate whenever autoconf is run.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110549] File expected to be at /usr/bin/file, isn't on ChromeOS

[anonymous]

URL:
  

 Summary: File expected to be at /usr/bin/file, isn't on
ChromeOS
 Project: Autoconf
Submitted by: None
Submitted on: Sat 16 Oct 2021 06:59:02 PM 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`

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:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/