[Top][All Lists]

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

Re: Libtool Digest, Vol 207, Issue 1

From: Alex Ameen
Subject: Re: Libtool Digest, Vol 207, Issue 1
Date: Sun, 17 Oct 2021 12:07:13 -0500

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

Hopefully this helps. 

On Sun, Oct 17, 2021, 11:03 AM <> wrote:
Send Libtool mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libtool digest..."

Today's Topics:

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


Message: 1
Date: Sun, 17 Oct 2021 00:47:54 -0400 (EDT)
From: anonymous <>
Subject: [sr #110550] File expected to be at /usr/bin/file, isn't on
Message-ID: <" target="_blank" rel="noreferrer">>
Content-Type: text/plain;charset=UTF-8


                 Summary: File expected to be at /usr/bin/file, isn't on
                 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



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 `` and

Autoconf and libtool are both at latest versions (2.71 and 2.4.6

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


Subject: Digest Footer

Libtool mailing list


End of Libtool Digest, Vol 207, Issue 1

reply via email to

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