Cannot build YugabyteDB with clang12 in Alma Linux 8.5 - yugabytedb

[Question posted by a user on YugabyteDB Community Slack]
Debug build does not seem to be working in the clang12 based build:
./yb_build.sh debug --sj
[100%] Linking CXX executable ../../../tests-integration-tests/cdc_service-int-test
[100%] Built target cdc_service-int-test
make: *** [Makefile:101: all] Error 2
real 0m28.279s
user 4m4.235s
sys 0m25.477s
[2022-02-26T15:52:32 yb_build.sh:466 run_cxx_build] C++ build finished with exit code 2 (build type: debug, compiler: clang12). Timing information is available above.
==========================================================================================
YUGABYTE BUILD SUMMARY
==========================================================================================
Build type : debug
C/C++ compiler : clang12
Build architecture : x86_64
Build directory : /yb-source/build/debug-clang12-dynamic
Third-party dir : /opt/yb-build/thirdparty/yugabyte-db-thirdparty-v20211222064150-dd4872fe56-almalinux8-x86_64-clang12
C++ compilation time : 28 seconds
Exit code : 2
------------------------------------------------------------------------------------------
doing
./yb_build.sh debug --clang12 --sj
also results in an error
...
[m-1] In YugabyteDB, setting LC_COLLATE to C and all other locale settings to en_US.UTF-8 by default. Locale support will be enhanced as part of addressing https://github.com/yugabyte/yugabyte-db/issues/1557
[m-1] initdb: invalid locale name "en_US.UTF-8"
[m-1] I0226 15:54:20.630203 15811 pg_wrapper.cc:521] initdb took 124 ms
[m-1] E0226 15:54:20.630272 15811 pg_wrapper.cc:525] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] E0226 15:54:20.630429 15811 catalog_manager.cc:7776] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
E0226 15:54:21.075644 15749 external_mini_cluster.cc:1247] master reported an initdb error: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: Failure
Failed
Bad status: Runtime error (yb/integration-tests/external_mini_cluster.cc:1248): Failed to start masters.: initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] W0226 15:54:21.096375 15815 catalog_manager.cc:2084] Tablespace refresh task failed with error Internal error (yb/master/catalog_manager.cc:1929): pg_tablespace table info not found
Test failure stack trace:
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: # 0x7f2962b044e9 yb::pgwrapper::PgWrapperTestBase::SetUp()
/yb-source/src/yb/yql/pgwrapper/create_initial_sys_catalog_snapshot.cc:29: # 0x404d94 yb::pgwrapper::CreateInitialSysCatalogSnapshotTest::SetUp()
I0226 15:54:21.706461 15749 external_mini_cluster.cc:2206] { daemon_id: m-1 bound_rpc: :0 } Starting Shutdown()
I0226 15:54:21.706606 15749 external_mini_cluster.cc:2249] Killing /yb-source/build/debug-clang12-dynamic/tests-pgwrapper/../bin/yb-master with pid 15756 with SIGKILL
I0226 15:54:21.719123 15749 test_util.cc:94] -----------------------------------------------
I0226 15:54:21.719149 15749 test_util.cc:95] Had fatal failures, leaving test files at /tmp/yb_test.tmp.32433.7631.5669.pid15685/create_initial_sys_catalog_snapshot.CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot.1645890856672495-15749
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot (5016 ms)
[----------] 1 test from CreateInitialSysCatalogSnapshotTest (5016 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (5016 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot
1 FAILED TEST
I0226 15:54:21.751582 15748 run-with-timeout.cc:198] subprocess.Wait finished, waitpid() returned 256
...
[postprocess_test_result.py:246] 2022-02-26 15:54:22,577 INFO: Wrote JSON test report file: /yb-source/build/debug-clang12-dynamic/yb-test-logs/tests-pgwrapper__create_initial_sys_catalog_snapshot/CreateInitialSysCatalogSnapshotTest_CreateInitialSysCatalogSnapshot_test_report.json
(end of standard error)
Traceback (most recent call last):
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 83, in <module>
main()
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 74, in main
raise RuntimeError("initdb failed in %.1f sec" % elapsed_time_sec)
RuntimeError: initdb failed in 6.4 sec
make[2]: *** [src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/build.make:70: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot] Error 1
make[1]: *** [CMakeFiles/Makefile2:51929: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/all] Error 2
make: *** [Makefile:101: all] Error 2
This happens in Alma Linux 8.5. Any hints?

You need some additional packages and it should work:
dnf install langpacks-en glibc-all-langpacks -y

Related

Ros2 Colcon build failed ,rclpy -error: 'PyErr_warnformat' was not decleared in the scope

Trying to install Ros2 humble in ubuntu 20.04,
while executing command --> Colcon build --symlink-install
I'm getting the following error
--- stderr: rclpy
In file included from /home/kalyan/ros2_humble/src/ros2/rclpy/rclpy/src/rclpy/node.hpp:24,
from /home/kalyan/ros2_humble/src/ros2/rclpy/rclpy/src/rclpy/action_client.hpp:26,
from /home/kalyan/ros2_humble/src/ros2/rclpy/rclpy/src/rclpy/_rclpy_pybind11.cpp:24:
/home/kalyan/ros2_humble/src/ros2/rclpy/rclpy/src/rclpy/context.hpp: In destructor ‘rclpy::InitOptions::~InitOptions()’:
/home/kalyan/ros2_humble/src/ros2/rclpy/rclpy/src/rclpy/context.hpp:49:7: error: ‘PyErr_WarnFormat’ was not declared in this scope; did you mean ‘PyErr_Format’?
49 | PyErr_WarnFormat(
| ^~~~~~
| PyErr_Format
make[2]: * [CMakeFiles/_rclpy_pybind11.dir/build.make:76: CMakeFiles/_rclpy_pybind11.dir/src/rclpy/_rclpy_pybind11.cpp.o] Error 1
make[1]: * [CMakeFiles/Makefile2:104: CMakeFiles/_rclpy_pybind11.dir/all] Error 2
make: * [Makefile:141: all] Error 2
---
Failed <<< rclpy [16.2s, exited with code 2]
Aborted <<< rclcpp [26.0s]
Aborted <<< ros2cli_test_interfaces [1min 29s]
Aborted <<< diagnostic_msgs [1min 32s]
Summary: 195 packages finished [4min 31s]
1 package failed: rclpy
3 packages aborted: diagnostic_msgs rclcpp ros2cli_test_interfaces
1 package had stderr output: rclpy
141 packages not processed
Help me to overcome this error.
pyhton3 version-->3.8.10
I have the python3.9 version too,
if python version < 3.2, it dose not have PyErr_WarnFormat().seehttps://docs.python.org/3/c-api/exceptions.html.
I delete /usr/include/python2.7/ and make the default python version is 3.8.10. It work for me.

Tty.c: loadable library and perl binaries are mismatched

I upgraded Ubuntu from zesty to bionic. In the process perl was upgraded from 5.24.1 to 5.26.1. Now I am getting this error when I try to install Expect.
Tty.c: loadable library and perl binaries are mismatched
I have re-installed IO::Tty and that says it has installed correctly. There are other modules that are reporting similar errors.
Here is the full output from the failed Expect install.
Fetching http://www.cpan.org/authors/id/J/JA/JACOBY/Expect-1.35.tar.gz
-> OK
Unpacking Expect-1.35.tar.gz
Entering Expect-1.35
Checking configure dependencies from META.json
Checking if you have ExtUtils::MakeMaker 6.64 ... Yes (7.24)
Configuring Expect-1.35
Running Makefile.PL
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Expect
Writing MYMETA.yml and MYMETA.json
-> OK
Checking dependencies from MYMETA.json ...
Checking if you have Fcntl 0 ... Yes (1.13)
Checking if you have IO::Handle 0 ... Yes (1.36)
Checking if you have IO::Pty 1.11 ... Yes (1.12)
Checking if you have Errno 0 ... Yes (1.28)
Checking if you have Test::More 1.00 ... Yes (1.302162)
Checking if you have Exporter 0 ... Yes (5.72)
Checking if you have IO::Tty 1.11 ... Yes (1.12)
Checking if you have File::Temp 0 ... Yes (0.2309)
Checking if you have POSIX 0 ... Yes (1.76)
Checking if you have Carp 0 ... Yes (1.42)
Building and testing Expect-1.35
cp lib/Expect.pm blib/lib/Expect.pm
Manifying 1 pod document
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/01-test.t .......
Dubious, test returned 1 (wstat 256, 0x100)
Failed 14/14 subtests
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/02-bc.t .........
Dubious, test returned 1 (wstat 256, 0x100)
No subtests run
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/03-log.t ........
Dubious, test returned 1 (wstat 256, 0x100)
Failed 11/11 subtests
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/04-multiline.t ..
Dubious, test returned 1 (wstat 256, 0x100)
Failed 33/33 subtests
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/10-internal.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 17/17 subtests
Tty.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)
t/11-calc.t .......
Dubious, test returned 1 (wstat 256, 0x100)
No subtests run
Test Summary Report
-------------------
t/01-test.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 14 tests but ran 0.
t/02-bc.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/03-log.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 11 tests but ran 0.
t/04-multiline.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 33 tests but ran 0.
t/10-internal.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 17 tests but ran 0.
t/11-calc.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
Files=6, Tests=0, 2 wallclock secs ( 0.08 usr 0.03 sys + 1.87 cusr 0.21 csys = 2.19 CPU)
Result: FAIL
Failed 6/6 test programs. 0/0 subtests failed.
Makefile:856: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 1
-> FAIL Installing Expect failed. See /home/chronos/.cpanm/work/1554249881.4055/build.log for details. Retry with --force to force install it.
chronos#BattleShip:~/app$ perl -v
This is perl 5, version 26, subversion 1 (v5.26.1) built for x86_64-linux-gnu-thread-multi
(with 67 registered patches, see perl -V for more detail)
Copyright 1987-2017, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
I deleted my ~/perl5 directory. Expect installed fine.

Copy Yocto Project to other PC by tar

Due to the Internet connect is poor on customer side, I copied the tar file of my Yocto Project to customer.
However, customer met an issue while untar the Yocto Project and run the bitbake command to build project on their PC.
Customer got the following build code error:
s32v#s32v-vm:~/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release$ bitbake fsl-image-s32v2xx
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:
Error, TMPDIR has changed location. You need to either move it back to /media/2T_HDD_for_SDK/Amingo/S32V/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp or rebuild
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
I edited /build_s32v234evb_release/tmp/saved_tmpdir file to re-position the tmp directory, this error has pass.
However, I got another error while building Kernel, it seems the directory parameter is still wrong... (There is no error while building U-Boot only.)
s32v#s32v-vm:~/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release$ bitbake fsl-image-s32v2xx
Loading cache: 100% |########################################################################################################################################################################| ETA: 00:00:00
Loaded 2462 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.26.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "aarch64-fsl-linux"
MACHINE = "s32v234evb"
DISTRO = "fsl-networking"
DISTRO_VERSION = "1.8"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "(nobranch):03b0fbcf6b3b5cd16ae16738fbaabd1c6bf98536"
meta-fsl-arm = "(nobranch):c9f259a4bf8472dfa3ff75f1c3fcbe5e0ded7aaf"
meta-fsl-networking = "(nobranch):b8ff02a8d508464a16c84e1d13c155f45aa98cbe"
meta-fsl-toolchain = "(nobranch):0a235c4bcd4057608ee60b8c898eec9509632b95"
meta-virtualization = "(nobranch):0277cbcb47db4239d0a4aa3b37c5c6a705070951"
meta-fsl-s32v = "<unknown>:<unknown>"
meta-oe
meta-networking
meta-python
meta-webserver
meta-filesystems = "(nobranch):c841231b9f327d2d06d19d2ba1324dd86b83617c"
meta-linaro
meta-aarch64
meta-linaro-toolchain = "(nobranch):5075a82bd510d19617803fb16da2375605225cbb"
NOTE: Preparing RunQueue
WARNING: /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/meta-fsl-s32v/recipes-kernel/linux/linux-s32v2xx_4.1.26.bb.do_compile is tainted from a forced run
WARNING: /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/meta-fsl-s32v/recipes-bsp/u-boot/u-boot-s32v2xx_2016.01.bb.do_compile is tainted from a forced run
WARNING: /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/meta-fsl-s32v/recipes-bsp/u-boot/u-boot-s32v2xx_2016.01.bb.do_deploy is tainted from a forced run
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (log file is located at /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/s32v234evb-fsl-linux/linux-s32v2xx/4.1.26-r0/temp/log.do_compile.17853)
ERROR: Logfile of failure stored in: /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/s32v234evb-fsl-linux/linux-s32v2xx/4.1.26-r0/temp/log.do_compile.17853
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 Image CC=aarch64-fsl-linux-gcc --sysroot=/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/sysroots/s32v234evb LD=aarch64-fsl-linux-ld.bfd --sysroot=/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/sysroots/s32v234evb
| make: *** /media/2T_HDD_for_SDK/Amingo/S32V/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work-shared/s32v234evb/kernel-source: No such file or directory. Stop.
| make: *** [__sub-make] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/s32v234evb-fsl-linux/linux-s32v2xx/4.1.26-r0/temp/log.do_compile.17853)
ERROR: Task 76 (/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/meta-fsl-s32v/recipes-kernel/linux/linux-s32v2xx_4.1.26.bb, do_compile) failed with exit code '1'
ERROR: Function failed: do_compile (log file is located at /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_compile.17854)
ERROR: Logfile of failure stored in: /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_compile.17854
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| LINK tests/qemu-iotests/socket_scm_helper
| GEN qemu-doc.html
| GEN qemu.1
| CC qga/commands.o
| cc1: warning: /media/2T_HDD_for_SDK/Amingo/S32V/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/sysroots/x86_64-linux/usr/include/pixman-1: No such file or directory [enabled by default]
| cc1: warning: /media/2T_HDD_for_SDK/Amingo/S32V/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/sysroots/x86_64-linux/usr/include/glib-2.0: No such file or directory [enabled by default]
| cc1: warning: /media/2T_HDD_for_SDK/Amingo/S32V/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/sysroots/x86_64-linux/usr/lib/glib-2.0/include: No such file or directory [enabled by default]
| /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/qemu-2.2.0/qga/commands.c:13:18: fatal error: glib.h: No such file or directory
| #include <glib.h>
| ^
| compilation terminated.
| make: *** [qga/commands.o] Error 1
| make: *** Waiting for unfinished jobs....
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/build_s32v234evb_release/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_compile.17854)
ERROR: Task 2849 (virtual:native:/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/poky/meta/recipes-devtools/qemu/qemu_2.2.0.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1504 tasks of which 1502 didn't need to be rerun and 2 failed.
Waiting for 0 running tasks to finish:
Summary: 2 tasks failed:
/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/meta-fsl-s32v/recipes-kernel/linux/linux-s32v2xx_4.1.26.bb, do_compile
virtual:native:/home/s32v/s32v_15.0/yocto_auto_linux_bsp15.0/poky/meta/recipes-devtools/qemu/qemu_2.2.0.bb, do_compile
Summary: There were 3 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
My question is:
Is it possible to copy the Yocot Project to another PC by tar file?
What configuration / initial files I need to edit except saved_tmpdir file?
Which file does Yocto Project define the "kernel-source" directory?
Best Regards,
Wayne Kuo
when you copy tar project to another PC, two files will be modified:
build/conf/bblayers.conf
build/tmp/saved_tmpdir
If it's only a matter of internet connection, I suggest you create a download folder mirror.
On your side, you add BB_GENERATE_MIRROR_TARBALLS and build.
Then copy entire DL_DIR folder at customer side, and use BB_NO_NETWORK there.
You can look here and here for usage example.
You can then make a new build at customer side without internet connection. to speed up process, you can also copy your sstate-cache folder to customer side and add a sstate mirror with SSTATE_MIRRORS.
No, you will need a fresh build folder
You need to create a new Yocto environment at customer side
It's bitbake variable STAGING_KERNEL_DIR
Error, TMPDIR has changed location. You need to either move it back to...
I built all yocto stuff with the user jamie. Due to disk space running out, I copied the whole $HOME directory of jamie to another disk /dev/sdb1, which had a larger storage.
When I tried to run bitbake command to make a test, I got the same error. Here is a simple solution which worked for me:
mount /dev/sdb1 /mnt/sdb1/
mount --bind /mnt/sdb1/home_jamie/ /home/jamie/
What I want was to restore the exact original filesystem layout which the bitbake commands were once run with.
To make the above changes permanent, write above mounting as entries of /etc/fstab.

linux, error building AM33 Yocto image, bitbake

I am following the steps here:http://variwiki.com/index.php?title=VAR-SOM-AM33_Yocto_FIDO_GS
I get the following error:
ERROR: Function failed: do_compile (log file is located at /home/philip/yocto_varsomam33/tisdk/build/arago-tmp-external-linaro-toolchain/work/cortexa8hf-vfp-neon-linux-gnueabi/input-utils/1.0-r0/temp/log.do_compile.3467)
ERROR: Logfile of failure stored in: /home/philip/yocto_varsomam33/tisdk/build/arago-tmp-external-linaro-toolchain/work/cortexa8hf-vfp-neon-linux-gnueabi/input-utils/1.0-r0/temp/log.do_compile.3467
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 6 DESTDIR=/home/philip/yocto_varsomam33/tisdk/build/arago-tmp-external-linaro-toolchain/work/cortexa8hf-vfp-neon-linux-gnueabi/input-utils/1.0-r0/image STRIP=
| Make.config:1: *** empty variable name. Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/philip/yocto_varsomam33/tisdk/build/arago-tmp-external-linaro-toolchain/work/cortexa8hf-vfp-neon-linux-gnueabi/input-utils/1.0-r0/temp/log.do_compile.3467)
ERROR: Task 1815 (/home/philip/yocto_varsomam33/tisdk/sources/meta-arago/meta-arago-extras/recipes-devtools/input-utils/input-utils_1.0.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3217 tasks of which 3211 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
Waiting for 0 running tasks to finish:
Summary: 1 task failed:
/home/philip/yocto_varsomam33/tisdk/sources/meta-arago/meta-arago-extras/recipes-devtools/input-utils/input-utils_1.0.bb, do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
If I look at the inputs-utils_1.0.bb file:
# set the DESTDIR and the STRIP variables used by the GNUmakefile.
# The STRIP variable is set to blank or else the variable setting from OE
# is picked up as <TC>-strip and the install step sees that as another
# file to install.
EXTRA_OEMAKE = "DESTDIR=${D} STRIP=''"
do_install () {
oe_runmake install
}
What to I do with the STRIP variable?
Thanks!
I rebuilt the VM with ubuntu 14.04 and now it works

Cross Compiling on OSX to Raspberry Pi

I am trying to configure an environment on my osx machine that will allow me to cross compile arm6 applications for the Raspberry Pi. I seem to be runnning into a wall when it comes to setting up the toolchain. I am using crosstool-ng and am following multiple guides on setup but my issue comes down to when running the ct-ng build command.
Once I run this command everything seems to be running fine until I get to trying to build the binutils. Once it reaches this depenency it will eventually fail no mater what I do.
This is the ouput that I am seeing:
[INFO ] Installing binutils for host
[EXTRA] Configuring binutils
[EXTRA] Building binutils
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:51:72: error: use of undeclared identifier 'do_not_use_isalnum_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:59:72: error: use of undeclared identifier 'do_not_use_isalpha_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:75:72: error: use of undeclared identifier 'do_not_use_iscntrl_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:83:72: error: use of undeclared identifier 'do_not_use_isdigit_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:91:72: error: use of undeclared identifier 'do_not_use_isgraph_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:99:72: error: use of undeclared identifier 'do_not_use_islower_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:107:72: error: use of undeclared identifier 'do_not_use_isprint_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:115:72: error: use of undeclared identifier 'do_not_use_ispunct_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:123:72: error: use of undeclared identifier 'do_not_use_isspace_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:131:72: error: use of undeclared identifier 'do_not_use_isupper_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:139:73: error: use of undeclared identifier 'do_not_use_isxdigit_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:147:72: error: use of undeclared identifier 'do_not_use_tolower_with_safe_ctype'
[ERROR] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cctype:155:72: error: use of undeclared identifier 'do_not_use_toupper_with_safe_ctype'
[ERROR] make[5]: *** [binary.o] Error 1
[ERROR] make[4]: *** [all-recursive] Error 1
[ERROR] make[3]: *** [all] Error 2
[ERROR] make[2]: *** [all-gold] Error 2
[ERROR] make[1]: *** [all] Error 2
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing binutils for host'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions#216]
[ERROR] >> called from: do_binutils_backend[scripts/build/binutils/binutils.sh#236]
[ERROR] >> called from: do_binutils_for_host[scripts/build/binutils/binutils.sh#101]
[ERROR] >> called from: main[scripts/crosstool-NG.sh#638]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> '/usr/local/Cellar/crosstool-ng/1.21.0/share/doc/crosstool-ng/ct-ng.1.21.0/B - Known issues.txt'
[ERROR]
[ERROR] (elapsed: 5:11.00)
[05:12] / make: *** [build] Error 1
If anyone has ran into this issue and knows how to fix it. It would be much appreciated. Trying to build from source on the Pi (Model A+ has proven pretty tough as it will eventually crash)
Thank you.
Gold linker cannot be compiled on Clang 6-7 for now. You should be able to proceed if the linker is disabled via ct-ng menuconfig in Binary Utilities - Linkers to enable.

Resources