Re: libtool problem
Hello Alice,
Alice Wonder wrote:
Hello,
[SNIP]
Software (audacity)
[SNIP]
libtool: link: unable to infer tagged configuration
libtool: link: specify a tag with `--tag'
[SNIP]
LIBTOOL=/opt/gnu/bin/libtool
libtool is generated script . Generated script has variable
available_tags= and then inside a number of sections.
audacity consists from many projects. Each project has own configuration
and some of them use libtool.
(1) If you audacity version is vary old try to update all audacity
{sub}projects and check that "autotool"-files are regenerated. Then
remove LIBTOOL variable from environment - project will use own script.
(2) About /opt/gnu/bin/libtool
It must be generated for this installation environment.
My own build version of libtool 2.4.6 supports:
available_tags='CXX F77 FC GO GCJ RC '
I guest that you lack CXX and result is missing 'tagged configuration'
If you prefer this approach you should rebuild libtool against compilers
installed in /opt/gnu/..., install and check content of "tagged" sections.
For instance search for 'TAG CONFIG: CXX'. Paths should correspond to
/opt/gnu/... installation.
With other words libtool script is compiler dependent. If installed it
must be refreshed (regenerated) after each update of compilers.
Regards,
Roumen
___
https://lists.gnu.org/mailman/listinfo/libtool
Re: libtool problem
On 2018-06-27 09:44, Roumen Petrov wrote:
Hello Alice,
Alice Wonder wrote:
Hello,
[SNIP]
Software (audacity)
[SNIP]
libtool: link: unable to infer tagged configuration
libtool: link: specify a tag with `--tag'
[SNIP]
LIBTOOL=/opt/gnu/bin/libtool
libtool is generated script . Generated script has variable
available_tags= and then inside a number of sections.
audacity consists from many projects. Each project has own
configuration and some of them use libtool.
(1) If you audacity version is vary old try to update all audacity
{sub}projects and check that "autotool"-files are regenerated. Then
remove LIBTOOL variable from environment - project will use own
script.
(2) About /opt/gnu/bin/libtool
It must be generated for this installation environment.
My own build version of libtool 2.4.6 supports:
available_tags='CXX F77 FC GO GCJ RC '
I guest that you lack CXX and result is missing 'tagged configuration'
If you prefer this approach you should rebuild libtool against
compilers installed in /opt/gnu/..., install and check content of
"tagged" sections.
For instance search for 'TAG CONFIG: CXX'. Paths should correspond to
/opt/gnu/... installation.
With other words libtool script is compiler dependent. If installed it
must be refreshed (regenerated) after each update of compilers.
Problem is now resolved.
I was trying to hard - setting environmental variables to let configure
know what was what. Seems *all* I needed to do was set /opt/gnu/bin
first in the $PATH and the existing configure script worked.
___
https://lists.gnu.org/mailman/listinfo/libtool
Does libtool need to escape plus signs in egrep expressions?
While looking though ltmain source code i've stumbled upon this egrep invocation: $EGREP ' (_head_[A-Za-z0-9_]+_[ad]l*|[A-Za-z0-9_]+_[ad]l*_iname)$' I've tried to see how it behaves on some import libraries that i have, and it turned out that i could never get it to detect the iname lines, unless i escape the plus sign. Are you sure this actually works? Note that the function that does this is only used in rather exotic corner-cases (old dlltool and/or ms dumpbin being in use), so it's plausible that it could have been broken since 2010, when it was added. signature.asc Description: OpenPGP digital signature ___ https://lists.gnu.org/mailman/listinfo/libtool
