Hi,
I'm not sure if this is the correct place to report this, but the configure
scripts produced by autoconf/automake assume "file" is located at
/usr/bin/file and report it missing otherwise.
I have file at /usr/local/bin/file - shouldn't the configure script search
$PATH to find "file"?
Regard
On 09/02/2015 02:06 AM, John Frankish wrote:
> Hi,
>
> I'm not sure if this is the correct place to report this, but the configure
> scripts produced by autoconf/automake assume "file" is located at
> /usr/bin/file and report it missing otherwise.
Running this command in both autoconf.git and aut
John Frankish wrote:
the configure
scripts produced by autoconf/automake assume "file" is located at
/usr/bin/file and report it missing otherwise.
Can you show us how to reproduce the bug, by supplying a configure.ac and a way
to invoke autoconf and configure? I'm not seeing it in my configu
> > Hi,
> >
> > I'm not sure if this is the correct place to report this, but the
> > configure scripts produced by autoconf/automake assume "file" is
> > located at /usr/bin/file and report it missing otherwise.
>
> Running this command in both autoconf.git and automake.git produces no hits:
>
John Frankish wrote:
I see it in almost every package I compile, in this case I took the first one I
found,
NetworkManager-1.0.4, which gives:
That use of /usr/bin/file comes from NetworkManager-1.0.4/m4/libtool.m4, which
is not part of Autoconf or Automake per se. I suggest reporting the bu
> > I see it in almost every package I compile, in this case I took the
> > first one I found, NetworkManager-1.0.4, which gives:
>
> That use of /usr/bin/file comes from NetworkManager-1.0.4/m4/libtool.m4,
> which is not part of Autoconf or Automake per se.
> I suggest reporting the bug to the L
