All,
I need help, or a link, to find out why libtool isn't working. I have also posted to the arch list in case this is libtool itself. libtool is attempting to use an undeclared variable as a command. The libtool file generated includes (beginning at line 2071):
# func_to_tool_file ARG LAZY # converts the file name ARG from $build format to toolchain format. Return # result in func_to_tool_file_result. If the conversion in use is listed # in (the comma separated) LAZY, no conversion takes place. func_to_tool_file () { $opt_debug case ,$2, in *,"$to_tool_file_cmd",*) func_to_tool_file_result=$1 ;; *) $to_tool_file_cmd "$1" func_to_tool_file_result=$func_to_host_file_result ;; esac } # end func_to_tool_file
The tdeutils build fails at make on the very first file. The line that fails is line 2083:
2083| $to_tool_file_cmd "$1"
The problem is '$to_tool_file_cmd' is never declared in 'libtool' resulting in the error:
../libtool: line 2083: ark_part.cpp: command not found
Basically, libtool is trying to execute 'ark_part.cpp' as the command since '$to_tool_file_cmd' is never declared or initialized and is just blank in the command '$to_tool_file_cmd "$1"'.
What I need to learn is whether this is a libtool problem or whether it is a tdeutils problem. tdeutils from the same source builds fine on slack, debian, etc.., so I wonder if this is a libtool version problem or something similar.
I am building in an arch chroot and he PKGBUILD file used does:
cd ${srcdir}/${pkgname#*-}
cp /usr/share/aclocal/libtool.m4 ./admin cp /usr/share/libtool/config/ltmain.sh ./admin
make -f admin/Makefile.common
./configure \ --prefix=${TDEDIR} \ --with-qt-dir=${QTDIR} \ --sysconfdir=/etc \ --localstatedir=/var \ --enable-debug=full \ --enable-closure
make
The complete error, which I don't fully understand is:
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE64_SOURCE -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT ark_part.lo -MD -MP -MF .deps/ark_part.Tpo -c -o ark_part.lo ark_part.cpp ../libtool: line 2083: ark_part.cpp: command not found
I have also tried 'make SHELL=/bin/bash' after googling that the environment could cause shell extension issues if part was done with bash and make was using sh, but that made no difference.
Anybody familiar with libtool know if this is a libtool problem or if this is a problem with the tdeutil code? If it is libtool, any work-arounds?
On Monday 19 March 2012 17:43:11 David C. Rankin wrote:
All,
I need help, or a link, to find out why libtool isn't working. I have also posted to the arch list in case this is libtool itself. libtool is attempting to use an undeclared variable as a command. The libtool file generated includes (beginning at line 2071):
# func_to_tool_file ARG LAZY # converts the file name ARG from $build format to toolchain format. Return # result in func_to_tool_file_result. If the conversion in use is listed # in (the comma separated) LAZY, no conversion takes place. func_to_tool_file () { $opt_debug case ,$2, in *,"$to_tool_file_cmd",*) func_to_tool_file_result=$1 ;; *) $to_tool_file_cmd "$1" func_to_tool_file_result=$func_to_host_file_result ;; esac } # end func_to_tool_file
The tdeutils build fails at make on the very first file. The line that fails is line 2083:
2083| $to_tool_file_cmd "$1"
The problem is '$to_tool_file_cmd' is never declared in 'libtool' resulting in the error:
../libtool: line 2083: ark_part.cpp: command not found
Basically, libtool is trying to execute 'ark_part.cpp' as the command since '$to_tool_file_cmd' is never declared or initialized and is just blank in the command '$to_tool_file_cmd "$1"'.
What I need to learn is whether this is a libtool problem or whether it is a tdeutils problem. tdeutils from the same source builds fine on slack, debian, etc.., so I wonder if this is a libtool version problem or something similar.
I am building in an arch chroot and he PKGBUILD file used does:
cd ${srcdir}/${pkgname#*-}
cp /usr/share/aclocal/libtool.m4 ./admin cp /usr/share/libtool/config/ltmain.sh ./admin
make -f admin/Makefile.common
./configure \ --prefix=${TDEDIR} \ --with-qt-dir=${QTDIR} \ --sysconfdir=/etc \ --localstatedir=/var \ --enable-debug=full \ --enable-closure
make
The complete error, which I don't fully understand is:
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE64_SOURCE -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT ark_part.lo -MD -MP -MF .deps/ark_part.Tpo -c -o ark_part.lo ark_part.cpp ../libtool: line 2083: ark_part.cpp: command not found
I have also tried 'make SHELL=/bin/bash' after googling that the environment could cause shell extension issues if part was done with bash and make was using sh, but that made no difference.
Anybody familiar with libtool know if this is a libtool problem or if this is a problem with the tdeutil code? If it is libtool, any work-arounds?
On Monday 19 March 2012 17:43:11 David C. Rankin wrote: [...]
The complete error, which I don't fully understand is:
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE64_SOURCE -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT ark_part.lo -MD -MP -MF .deps/ark_part.Tpo -c -o ark_part.lo ark_part.cpp ../libtool: line 2083: ark_part.cpp: command not found
I have also tried 'make SHELL=/bin/bash' after googling that the environment could cause shell extension issues if part was done with bash and make was using sh, but that made no difference.
Anybody familiar with libtool know if this is a libtool problem or if this is a problem with the tdeutil code? If it is libtool, any work-arounds?
It seems like libtool can't execute g++
On 03/19/2012 10:50 AM, Serghei Amelian wrote:
Anybody familiar with libtool know if this is a libtool problem or if this is a problem with the tdeutil code? If it is libtool, any work-arounds?
It seems like libtool can't execute g++
Hmm,
I wonder if the libtool.m4.in file may not be the problem? There is no reference in libtool.m4.in at all concerning to_tool_file_cmd. Could this be the problem?
10:51 nirvana:/mnt/nv1/home/chroot/david/build/src/tdeutils/admin> grep to_tool_file_cmd * libtool.m4:AC_CACHE_VAL(lt_cv_to_tool_file_cmd, libtool.m4:lt_cv_to_tool_file_cmd=func_convert_file_noop libtool.m4: lt_cv_to_tool_file_cmd=func_convert_file_msys_to_w32 libtool.m4:to_tool_file_cmd=$lt_cv_to_tool_file_cmd libtool.m4:AC_MSG_RESULT([$lt_cv_to_tool_file_cmd]) libtool.m4:_LT_DECL([to_tool_file_cmd], [lt_cv_to_tool_file_cmd],
ltmain.sh: *,"$to_tool_file_cmd",*) ltmain.sh: $to_tool_file_cmd "$1" ltmain.sh: case $nm_file_list_spec~$to_tool_file_cmd in
Nothing in libtool.m4.in. I don't know if libtool.m4.in is even used since the libtool.m4 is present, but this caught my eye looking around.
I'll report back on the kpowersave linker issue in the other thread :)
I wonder if the libtool.m4.in file may not be the problem? There is no reference in libtool.m4.in at all concerning to_tool_file_cmd. Could this be the problem?
10:51 nirvana:/mnt/nv1/home/chroot/david/build/src/tdeutils/admin> grep to_tool_file_cmd * libtool.m4:AC_CACHE_VAL(lt_cv_to_tool_file_cmd, libtool.m4:lt_cv_to_tool_file_cmd=func_convert_file_noop libtool.m4: lt_cv_to_tool_file_cmd=func_convert_file_msys_to_w32 libtool.m4:to_tool_file_cmd=$lt_cv_to_tool_file_cmd libtool.m4:AC_MSG_RESULT([$lt_cv_to_tool_file_cmd]) libtool.m4:_LT_DECL([to_tool_file_cmd], [lt_cv_to_tool_file_cmd],
ltmain.sh: *,"$to_tool_file_cmd",*) ltmain.sh: $to_tool_file_cmd "$1" ltmain.sh: case $nm_file_list_spec~$to_tool_file_cmd in
Nothing in libtool.m4.in. I don't know if libtool.m4.in is even used since the libtool.m4 is present, but this caught my eye looking around.
tdeutils built without error here last night (Slackware 13.1).
Darrell
tdeutils built without error here last night (Slackware 13.1).
Darrell
What version of libtool? I have 2.4.2-4. There is no question what the problem is. In the version of libtool created in tdeutils, the variable 'to_tool_file_cmd' is undefined and the call at line 2083 to:
$to_tool_file_cmd "$1"
fails...
If you grep your libtool or libtool.m4, do you even have a reference to it?
What version of libtool? I have 2.4.2-4. There is no question what the problem is. In the version of libtool created in tdeutils, the variable 'to_tool_file_cmd' is undefined and the call at line 2083 to:
$to_tool_file_cmd "$1"
fails...
If you grep your libtool or libtool.m4, do you even have a reference to it?
I have libtool 2.2.6b. No reference to to_tool_file_cmd.
Darrell
On 03/19/2012 02:17 PM, Darrell Anderson wrote:
I have libtool 2.2.6b. No reference to to_tool_file_cmd.
Darrell
Grrr... Archlinux! That's the whole problem. Now the question is how do I fix it? I have no idea how to control the code generated by libtool or autofoo....
I would like to just bypass the whole to_tool_file_cmd parsing. It is the last 15 or so lines of code in my libtool.m4 file. Wonder if I can just nix it?