On 10/31/19 10:53 AM, Jared Stevens via blfs-support wrote:
Hey guys,
Here I am with yet another problem I am having on an entirely new build
of LFS.
For some reason, I am now getting the following error (which never
happened on any of my other builds) whenever a package calls for
'*autogen.sh*' before the configure process:
*+ libtoolize --copy*
*+ 'aclocal -I /usr/share/aclocal' -I m4*
*autogen.sh: line 44: aclocal -I /usr/share/aclocal: No such file or
directory*
This has happened on multiple packages in BLFS now such as
'*libuv-v1.31.0*.'
Thinking that the issue was due to an error in my LFS build, I
completely started over again and made CERTAIN that the check for
*Automake* passed flawlessly, which it did.
However, the issue persisted even with this new build. I tried using the
updated versions of some packages in development such as *'libuv-133.1*'
as well, but no luck.
Both the *aclocal* and *aclocal-1.16* are clearly installed in the
*//usr/share/* directory, and both contain*.m4* files as expected that
very nearly match the contents of my host PC's identical directories.
I am perplexed as to what the issue is, where it started, and how to fix
it. As of now I am having no issues elsewhere. I just cannot install any
package requiring a call to *aclocal* because it can't be found for some
reason.
Hmm. Do you have the ACLOCAL environment variable set? What I see
above is 'aclocal -I /usr/share/aclocal' -I m4*. The quotes should not
be present. It is treating the entire quoted string, 'aclocal -I
/usr/share/aclocal' as the file name.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
