Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building libspiro with slibtool (https://dev.midipix.org/cross/slibtool) it fails in two places.
This reveals four issues:
--mode=link
unless its also calling$(LIBTOOL)
manually which its not. GNU libtool silently consumes and ignores invalid command-line arguments hiding the issue.LIBADD
for libraries orLDADD
for programs whileLDFLAGS
is for other linker arguments. GNU libtool is far more permissive about these things than slibtool and hides incorrect usage.SOURCES
and the build should not define object files rules manually..libs
directory should not be manually added to the linker paths, that is for internal$(LIBTOOL)
usage.Also please see this related PR fontforge/libuninameslist#24.