* libtool error when running adt_installer
@ 2014-07-16 9:26 Joseph Andrew de la Peña
0 siblings, 0 replies; 4+ messages in thread
From: Joseph Andrew de la Peña @ 2014-07-16 9:26 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]
Good day,
I have an error in libtool when running adt_installer script.
make[1]: Entering directory
`/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32
-march=i586
--sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
-DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall -DHOST_CPU_STR=\"x86_64\"
-DBUILD_CPU=x86_64 -O -fno-omit-frame-pointer -g
-feliminate-unused-debug-types -pipe -MT libbb_la-gz_open.lo -MD -MP -MF
.deps/libbb_la-gz_open.Tpo -c -o libbb_la-gz_open.lo `test -f 'gz_open.c'
|| echo './'`gz_open.c
*/bin/sh: ../-libtool: No such file or directory*
make[1]: *** [libbb_la-gz_open.lo] Error 127
make[1]: Leaving directory
`/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
make: *** [all-recursive] Error 1
Seems to be $LIBTOOL was not having the correct value. I've searched all
occurrence of $LIBTOOL but all of them had -libtool value.
Where does $LIBTOOL originate when creating my own adt_installer script via
bitbake adt-installer?
What variables in any conf file do I need to change to run adt_installer
successfully?
Attached is the full log during running of adt_installer.
Thanks,
Joseph
[-- Attachment #1.2: Type: text/html, Size: 1529 bytes --]
[-- Attachment #2: adt_installer.log --]
[-- Type: application/octet-stream, Size: 13329 bytes --]
#########################################################################
# Welcome to Yocto Application Developement Tools (ADT) Installer
#
# Host Machine: x86_64
# OS info: 3.9.10-100.fc17.x86_64
# Yocto ADT version to be installed:
# supported target architectures: x86 x86_64 arm ppc mips
# supported target root_fs images: minimal minimal-dev sato sato-dev sato-sdk lsb lsb-dev lsb-sdk
#########################################################################
Systemwide installation. Installation will occur under /bonus/scratch/jdelapena/temp
############################################################################
# Your system installation configurations from adt_installer.conf
############################################################################
# Cross toolchains: arm x86
# Install Qemu: Y
# Install NFS utilities: Y
##############################################################################
# Your rootfs image(s) and target sysroot selections from adt_installer.conf
##############################################################################
# Target architecture: x86
# Target machine: qemux86
# Root_fs images: sato-sdk
# Target sysroot image: sato-sdk
# Target sysroot loc: /users/jdelapena/test-yocto/qemux86
# Target architecture: arm
# Target machine: qemuarm
# Root_fs images: minimal sato-sdk
# Target sysroot image: sato-sdk
# Target sysroot loc: /users/jdelapena/test-yocto/qemuarm
############################################################################
There're two ways you can do installation: silent mode or interactive mode. To choose silent mode, which means you opt for the system to override the existing data under the specified installation directories without prompting for your confirmation. Please be cautious with this selection which may trigger your losing data. With the interactive mode, you have to closely monitor the installation process, since it will prompt you each step it needs to override some existing data. To choose silent mode, please enter [S], for interactive mode, please enter [I] or [X] to exit the installation.
[ADT_INST] Please enter your selections here:
--2014-07-16 15:53:29-- http://adtrepo.yoctoproject.org/1.5.1
Resolving adtrepo.yoctoproject.org... 140.211.169.59
Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... failed: Connection refused.
OPKG is not setup, setting up opkg in local, which is required for installing yocto ADT...
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `conf'.
libtoolize: copying file `conf/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `shave'.
libtoolize: copying file `shave/libtool.m4'
libtoolize: copying file `shave/ltoptions.m4'
libtoolize: copying file `shave/ltsugar.m4'
libtoolize: copying file `shave/ltversion.m4'
libtoolize: copying file `shave/lt~obsolete.m4'
Creating po/ subdirectory
Copying file po/Makefile.in.in
Please add the files
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
progtest.m4
from the /bonus/scratch/jdelapena/build-bundle/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.
configure: loading site script /bonus/scratch/jdelapena/sdk/site-config-i586-poky-linux
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for style of include used by make... GNU
checking for gcc... i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux accepts -g... yes
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to accept ISO C89... none needed
checking dependency style of i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... gcc3
checking how to run the C preprocessor... i586-poky-linux-gcc -E -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for gawk... (cached) gawk
checking for gcc... (cached) i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking whether we are using the GNU C compiler... (cached) yes
checking whether i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux accepts -g... (cached) yes
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to accept ISO C89... (cached) none needed
checking dependency style of i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... (cached) gcc3
checking whether ln -s works... yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking if the linker (i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... i586-poky-linux-nm
checking the name lister (i586-poky-linux-nm) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to reload object files... -r
checking for objdump... i586-poky-linux-objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... i586-poky-linux-strip
checking for ranlib... i586-poky-linux-ranlib
checking command to parse i586-poky-linux-nm output from i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux object... ok
checking for sysroot... /bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking for mt... no
checking if : is a manifest tool... no
checking for dlfcn.h... (cached) yes
checking for objdir... .libs
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -fno-rtti -fno-exceptions... no
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to produce PIC... -fPIC -DPIC
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux PIC flag -fPIC -DPIC works... yes
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux static flag -static works... no
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -c -o file.o... yes
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -c -o file.o... (cached) yes
checking whether the i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux linker (i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux -m elf_i386) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for pkg-config... /bonus/scratch/jdelapena/sdk/sysroots/i686-pokysdk-linux/usr/bin/pkg-config
checking pkg-config is at least version 0.20... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for errno.h... (cached) yes
checking for fcntl.h... (cached) yes
checking for memory.h... (cached) yes
checking for regex.h... (cached) yes
checking for stddef.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for unistd.h... (cached) yes
checking for utime.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for uid_t in sys/types.h... (cached) {ac_cv_type_uid_t=yes}
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for struct stat.st_rdev... yes
checking whether byte ordering is bigendian... (cached) no
checking for unistd.h... (cached) yes
checking for working chown... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... (cached) yes
checking for vfork... (cached) yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking return type of signal handlers... void
checking for utime.h... (cached) yes
checking whether utime accepts a null argument... yes
checking for vprintf... (cached) yes
checking for _doprnt... no
checking for memmove... (cached) yes
checking for memset... (cached) yes
checking for mkdir... (cached) yes
checking for regcomp... (cached) yes
checking for strchr... (cached) yes
checking for strcspn... (cached) yes
checking for strdup... (cached) yes
checking for strerror... (cached) yes
checking for strndup... (cached) yes
checking for strrchr... (cached) yes
checking for strstr... (cached) yes
checking for strtol... (cached) yes
checking for strtoul... (cached) yes
checking for sysinfo... (cached) yes
checking for utime... (cached) yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libopkg/Makefile
config.status: creating tests/Makefile
config.status: creating src/Makefile
config.status: creating libbb/Makefile
config.status: creating utils/Makefile
config.status: creating utils/update-alternatives
config.status: creating libopkg.pc
config.status: creating shave/shave
config.status: creating shave/shave-libtool
config.status: creating man/Makefile
config.status: creating man/opkg-cl.1
config.status: creating man/opkg-key.1
config.status: creating libopkg/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in libbb
make[1]: Entering directory `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux -DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall -DHOST_CPU_STR=\"x86_64\" -DBUILD_CPU=x86_64 -O -fno-omit-frame-pointer -g -feliminate-unused-debug-types -pipe -MT libbb_la-gz_open.lo -MD -MP -MF .deps/libbb_la-gz_open.Tpo -c -o libbb_la-gz_open.lo `test -f 'gz_open.c' || echo './'`gz_open.c
/bin/sh: ../-libtool: No such file or directory
make[1]: *** [libbb_la-gz_open.lo] Error 127
make[1]: Leaving directory `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
make: *** [all-recursive] Error 1
^ permalink raw reply [flat|nested] 4+ messages in thread
* libtool error when running adt_installer
@ 2014-07-17 1:18 Joseph Andrew de la Peña
2014-07-17 8:57 ` Chong Lu
0 siblings, 1 reply; 4+ messages in thread
From: Joseph Andrew de la Peña @ 2014-07-17 1:18 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]
Good day,
I have an error in libtool when running adt_installer script.
make[1]: Entering directory
`/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32
-march=i586
--sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
-DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall -DHOST_CPU_STR=\"x86_64\"
-DBUILD_CPU=x86_64 -O -fno-omit-frame-pointer -g
-feliminate-unused-debug-types -pipe -MT libbb_la-gz_open.lo -MD -MP -MF
.deps/libbb_la-gz_open.Tpo -c -o libbb_la-gz_open.lo `test -f 'gz_open.c'
|| echo './'`gz_open.c
*/bin/sh: ../-libtool: No such file or directory*
make[1]: *** [libbb_la-gz_open.lo] Error 127
make[1]: Leaving directory
`/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
make: *** [all-recursive] Error 1
Seems to be $LIBTOOL was not having the correct value. I've searched all
occurrence of $LIBTOOL but all of them had -libtool value.
Where does $LIBTOOL originate when creating my own adt_installer script via
bitbake adt-installer?
What variables in any conf file do I need to change to run adt_installer
successfully?
Attached is the full log during running of adt_installer.
Thanks,
Joseph
[-- Attachment #1.2: Type: text/html, Size: 1565 bytes --]
[-- Attachment #2: adt_installer.log --]
[-- Type: application/octet-stream, Size: 13329 bytes --]
#########################################################################
# Welcome to Yocto Application Developement Tools (ADT) Installer
#
# Host Machine: x86_64
# OS info: 3.9.10-100.fc17.x86_64
# Yocto ADT version to be installed:
# supported target architectures: x86 x86_64 arm ppc mips
# supported target root_fs images: minimal minimal-dev sato sato-dev sato-sdk lsb lsb-dev lsb-sdk
#########################################################################
Systemwide installation. Installation will occur under /bonus/scratch/jdelapena/temp
############################################################################
# Your system installation configurations from adt_installer.conf
############################################################################
# Cross toolchains: arm x86
# Install Qemu: Y
# Install NFS utilities: Y
##############################################################################
# Your rootfs image(s) and target sysroot selections from adt_installer.conf
##############################################################################
# Target architecture: x86
# Target machine: qemux86
# Root_fs images: sato-sdk
# Target sysroot image: sato-sdk
# Target sysroot loc: /users/jdelapena/test-yocto/qemux86
# Target architecture: arm
# Target machine: qemuarm
# Root_fs images: minimal sato-sdk
# Target sysroot image: sato-sdk
# Target sysroot loc: /users/jdelapena/test-yocto/qemuarm
############################################################################
There're two ways you can do installation: silent mode or interactive mode. To choose silent mode, which means you opt for the system to override the existing data under the specified installation directories without prompting for your confirmation. Please be cautious with this selection which may trigger your losing data. With the interactive mode, you have to closely monitor the installation process, since it will prompt you each step it needs to override some existing data. To choose silent mode, please enter [S], for interactive mode, please enter [I] or [X] to exit the installation.
[ADT_INST] Please enter your selections here:
--2014-07-16 15:53:29-- http://adtrepo.yoctoproject.org/1.5.1
Resolving adtrepo.yoctoproject.org... 140.211.169.59
Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... failed: Connection refused.
OPKG is not setup, setting up opkg in local, which is required for installing yocto ADT...
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `conf'.
libtoolize: copying file `conf/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `shave'.
libtoolize: copying file `shave/libtool.m4'
libtoolize: copying file `shave/ltoptions.m4'
libtoolize: copying file `shave/ltsugar.m4'
libtoolize: copying file `shave/ltversion.m4'
libtoolize: copying file `shave/lt~obsolete.m4'
Creating po/ subdirectory
Copying file po/Makefile.in.in
Please add the files
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
progtest.m4
from the /bonus/scratch/jdelapena/build-bundle/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.
configure: loading site script /bonus/scratch/jdelapena/sdk/site-config-i586-poky-linux
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for style of include used by make... GNU
checking for gcc... i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux accepts -g... yes
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to accept ISO C89... none needed
checking dependency style of i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... gcc3
checking how to run the C preprocessor... i586-poky-linux-gcc -E -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for gawk... (cached) gawk
checking for gcc... (cached) i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking whether we are using the GNU C compiler... (cached) yes
checking whether i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux accepts -g... (cached) yes
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to accept ISO C89... (cached) none needed
checking dependency style of i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... (cached) gcc3
checking whether ln -s works... yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux... i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking if the linker (i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... i586-poky-linux-nm
checking the name lister (i586-poky-linux-nm) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to reload object files... -r
checking for objdump... i586-poky-linux-objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... i586-poky-linux-strip
checking for ranlib... i586-poky-linux-ranlib
checking command to parse i586-poky-linux-nm output from i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux object... ok
checking for sysroot... /bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
checking for mt... no
checking if : is a manifest tool... no
checking for dlfcn.h... (cached) yes
checking for objdir... .libs
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -fno-rtti -fno-exceptions... no
checking for i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux option to produce PIC... -fPIC -DPIC
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux PIC flag -fPIC -DPIC works... yes
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux static flag -static works... no
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -c -o file.o... yes
checking if i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux supports -c -o file.o... (cached) yes
checking whether the i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux linker (i586-poky-linux-ld --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux -m elf_i386) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for pkg-config... /bonus/scratch/jdelapena/sdk/sysroots/i686-pokysdk-linux/usr/bin/pkg-config
checking pkg-config is at least version 0.20... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for errno.h... (cached) yes
checking for fcntl.h... (cached) yes
checking for memory.h... (cached) yes
checking for regex.h... (cached) yes
checking for stddef.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for unistd.h... (cached) yes
checking for utime.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for uid_t in sys/types.h... (cached) {ac_cv_type_uid_t=yes}
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for struct stat.st_rdev... yes
checking whether byte ordering is bigendian... (cached) no
checking for unistd.h... (cached) yes
checking for working chown... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... (cached) yes
checking for vfork... (cached) yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking return type of signal handlers... void
checking for utime.h... (cached) yes
checking whether utime accepts a null argument... yes
checking for vprintf... (cached) yes
checking for _doprnt... no
checking for memmove... (cached) yes
checking for memset... (cached) yes
checking for mkdir... (cached) yes
checking for regcomp... (cached) yes
checking for strchr... (cached) yes
checking for strcspn... (cached) yes
checking for strdup... (cached) yes
checking for strerror... (cached) yes
checking for strndup... (cached) yes
checking for strrchr... (cached) yes
checking for strstr... (cached) yes
checking for strtol... (cached) yes
checking for strtoul... (cached) yes
checking for sysinfo... (cached) yes
checking for utime... (cached) yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libopkg/Makefile
config.status: creating tests/Makefile
config.status: creating src/Makefile
config.status: creating libbb/Makefile
config.status: creating utils/Makefile
config.status: creating utils/update-alternatives
config.status: creating libopkg.pc
config.status: creating shave/shave
config.status: creating shave/shave-libtool
config.status: creating man/Makefile
config.status: creating man/opkg-cl.1
config.status: creating man/opkg-key.1
config.status: creating libopkg/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in libbb
make[1]: Entering directory `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32 -march=i586 --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux -DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall -DHOST_CPU_STR=\"x86_64\" -DBUILD_CPU=x86_64 -O -fno-omit-frame-pointer -g -feliminate-unused-debug-types -pipe -MT libbb_la-gz_open.lo -MD -MP -MF .deps/libbb_la-gz_open.Tpo -c -o libbb_la-gz_open.lo `test -f 'gz_open.c' || echo './'`gz_open.c
/bin/sh: ../-libtool: No such file or directory
make[1]: *** [libbb_la-gz_open.lo] Error 127
make[1]: Leaving directory `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
make: *** [all-recursive] Error 1
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libtool error when running adt_installer
2014-07-17 1:18 libtool error when running adt_installer Joseph Andrew de la Peña
@ 2014-07-17 8:57 ` Chong Lu
2014-07-17 9:14 ` Joseph Andrew de la Peña
0 siblings, 1 reply; 4+ messages in thread
From: Chong Lu @ 2014-07-17 8:57 UTC (permalink / raw)
To: Joseph Andrew de la Peña, yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
Hi Joseph,
In adt-installer/opkg/build/opkg-svn/configure file, we have
8917 # Always use our own libtool.
8918 LIBTOOL='$(SHELL) $(top_builddir)/libtool'
So, we should libtool rather than -libtool.
Do you have any env variable to set LIBTOOL?
In addition, I found your log:
--2014-07-16 15:53:29--http://adtrepo.yoctoproject.org/1.5.1
Resolving adtrepo.yoctoproject.org... 140.211.169.59
Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... failed: Connection refused.
You fail to connect repo. Please check.
BR
Chong
On 07/17/2014 09:18 AM, Joseph Andrew de la Peña wrote:
> Good day,
>
> I have an error in libtool when running adt_installer script.
>
> make[1]: Entering directory
> `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
> ../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32
> -march=i586
> --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
> -DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall
> -DHOST_CPU_STR=\"x86_64\" -DBUILD_CPU=x86_64 -O
> -fno-omit-frame-pointer -g -feliminate-unused-debug-types -pipe -MT
> libbb_la-gz_open.lo -MD -MP -MF .deps/libbb_la-gz_open.Tpo -c -o
> libbb_la-gz_open.lo `test -f 'gz_open.c' || echo './'`gz_open.c
>
> */bin/sh: ../-libtool: No such file or directory*
> make[1]: *** [libbb_la-gz_open.lo] Error 127
> make[1]: Leaving directory
> `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
> make: *** [all-recursive] Error 1
>
> Seems to be $LIBTOOL was not having the correct value. I've searched
> all occurrence of $LIBTOOL but all of them had -libtool value.
>
> Where does $LIBTOOL originate when creating my own adt_installer
> script via bitbake adt-installer?
> What variables in any conf file do I need to change to run
> adt_installer successfully?
>
> Attached is the full log during running of adt_installer.
>
> Thanks,
> Joseph
>
>
>
[-- Attachment #2: Type: text/html, Size: 3586 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libtool error when running adt_installer
2014-07-17 8:57 ` Chong Lu
@ 2014-07-17 9:14 ` Joseph Andrew de la Peña
0 siblings, 0 replies; 4+ messages in thread
From: Joseph Andrew de la Peña @ 2014-07-17 9:14 UTC (permalink / raw)
To: Chong Lu; +Cc: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]
Good day Chong,
Thank you again for looking into my issue. Apparently, in the generated
configure script:
# Always use our own libtool.
LIBTOOL='$(top_builddir)'
LIBTOOL="$LIBTOOL/${host_alias}-libtool"
Looked into the changes for this and there was a patch submitted to
differentiate host aliases.
http://cgit.openembedded.org/openembedded/plain/recipes/binutils/binutils-2.20.1/libtool-update.patch
Found out that host_alias was "" which resulted to -libtool. When I set
manually host_alias to a certain host value, it went pass the error. So
maybe the question now is where is host_alias assigned to a value?
YES. There was a connection error since I've disabled HTTP_PROXY.
Thanks,
Joseph
On Thu, Jul 17, 2014 at 4:57 PM, Chong Lu <Chong.Lu@windriver.com> wrote:
> Hi Joseph,
>
> In adt-installer/opkg/build/opkg-svn/configure file, we have
> 8917 # Always use our own libtool.
> 8918 LIBTOOL='$(SHELL) $(top_builddir)/libtool'
>
> So, we should libtool rather than -libtool.
> Do you have any env variable to set LIBTOOL?
>
> In addition, I found your log:
>
> --2014-07-16 15:53:29-- http://adtrepo.yoctoproject.org/1.5.1
> Resolving adtrepo.yoctoproject.org... 140.211.169.59
> Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... failed: Connection refused.
>
> You fail to connect repo. Please check.
>
> BR
> Chong
>
>
> On 07/17/2014 09:18 AM, Joseph Andrew de la Peña wrote:
>
> Good day,
>
> I have an error in libtool when running adt_installer script.
>
> make[1]: Entering directory
> `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
> ../-libtool --tag=CC --mode=compile i586-poky-linux-gcc -m32
> -march=i586
> --sysroot=/bonus/scratch/jdelapena/sdk/sysroots/i586-poky-linux
> -DHAVE_CONFIG_H -I. -I../libopkg -g -O -Wall -DHOST_CPU_STR=\"x86_64\"
> -DBUILD_CPU=x86_64 -O -fno-omit-frame-pointer -g
> -feliminate-unused-debug-types -pipe -MT libbb_la-gz_open.lo -MD -MP -MF
> .deps/libbb_la-gz_open.Tpo -c -o libbb_la-gz_open.lo `test -f 'gz_open.c'
> || echo './'`gz_open.c
>
> */bin/sh: ../-libtool: No such file or directory*
> make[1]: *** [libbb_la-gz_open.lo] Error 127
> make[1]: Leaving directory
> `/users/jdelapena/adt-installer/opkg/build/opkg-svn/libbb'
> make: *** [all-recursive] Error 1
>
> Seems to be $LIBTOOL was not having the correct value. I've searched all
> occurrence of $LIBTOOL but all of them had -libtool value.
>
> Where does $LIBTOOL originate when creating my own adt_installer script
> via bitbake adt-installer?
> What variables in any conf file do I need to change to run adt_installer
> successfully?
>
> Attached is the full log during running of adt_installer.
>
> Thanks,
> Joseph
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4821 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-07-17 9:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-17 1:18 libtool error when running adt_installer Joseph Andrew de la Peña
2014-07-17 8:57 ` Chong Lu
2014-07-17 9:14 ` Joseph Andrew de la Peña
-- strict thread matches above, loose matches on Subject: below --
2014-07-16 9:26 Joseph Andrew de la Peña
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.