[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] build: Fix undefined 'LIBTOOL' error.
From: |
Collin Funk |
Subject: |
[PATCH] build: Fix undefined 'LIBTOOL' error. |
Date: |
Sat, 01 Jun 2024 05:03:20 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
When building from the main branch I see the following error:
guile-readline/Makefile.am:47: error: Libtool library used but 'LIBTOOL' is
undefined
guile-readline/Makefile.am:47: The usual way to define 'LIBTOOL' is to add
'LT_INIT'
guile-readline/Makefile.am:47: to 'configure.ac' and run 'aclocal' and
'autoconf' again.
guile-readline/Makefile.am:47: If 'LT_INIT' is in 'configure.ac', make sure
guile-readline/Makefile.am:47: its definition is in aclocal's search path.
Then autogen.sh fails. This is because libtoolize is not called. The
version is announced so I assume the intent was to actually call it.
I've attached a patch doing so.
Then I see the following warning:
automake: warning: possible forward-incompatibility.
automake: At least one source file is in a subdirectory, but the
'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding
output
automake: object file(s) will be placed in the top-level directory. However,
this
automake: behavior may change in a future Automake major version, with object
automake: files being placed in the same subdirectory as the corresponding
sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
This option has been around for a long time. I have just added it to
AM_INIT_AUTOMAKE to silence the warning.
Collin
0001-build-Fix-undefined-LIBTOOL-error.patch
Description: Text Data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] build: Fix undefined 'LIBTOOL' error.,
Collin Funk <=