mainAutoconf - Support: sr #110549, File expected to be at...


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

Submitter:  None
Submitted:  Sat 16 Oct 2021 06:59:02 PM UTC
Priority:  * 5 - Unprioritized Severity:  3 - Normal
Status:  Not Autoconf Privacy:  Public
Assigned to:  None Originator Email:  -email is unavailable-
Open/Closed:  Closed Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup

Fri 08 Dec 2023 01:35:10 AM UTC, comment #2: 

Closing; this needs to be addressed in Libtool.

Zack Weinberg <zackw>
Group administrator
Sat 16 Oct 2021 07:40:09 PM UTC, comment #1: 

That use of /usr/bin/file seems to come from the libtool.m4 and/or 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.

Daniel Macks <dmacks>
Sat 16 Oct 2021 06:59:02 PM UTC, original submission:  

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.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by zackw (Posted a comment)
  • -email is unavailable- added by dmacks (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-12-08 zackw StatusNone Not Autoconf
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code