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

[Alex Ameen]

Update of sr #110550 (project libtool):

  Status:  Ready For Test => Done   
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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

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

[Alex Ameen]

Update of sr #110550 (project libtool):

  Status:None => Ready For Test 
 Assigned to:None => growpotkin 


___

Reply to this item at:

  

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

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

[Alex Ameen]

Follow-up Comment #1, sr #110550 (project libtool):

I actually just submitted a PR for this issue that you can probably use. 

savannah.gnu.org/patch/?10113

Hopefully this helps. 


___

Reply to this item at:

  

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

[sr #110550] 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: 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
 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:

  

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