22-Aug-2014 11:03:15 version:
22-Aug-2014 11:03:15 [echo] 1.0.0-MAIN-22328-23.${build.number}
22-Aug-2014 11:03:15
22-Aug-2014 11:03:15 revert:
22-Aug-2014 11:03:17 [p4edit] error: Invalid changelist number '${p4.change}'.
22-Aug-2014 11:03:17
22-Aug-2014 11:03:17 BUILD FAILED
22-Aug-2014 11:03:17 c:\Build\XXX\build.xml:189: error: Invalid changelist number '${p4.change}'.
22-Aug-2014 11:03:17
22-Aug-2014 11:03:17
22-Aug-2014 11:03:17 Total time: 2 seconds
Following is the error I am getting on my Bamboo build, initially 3 builds ago everything was working fine until this error started getting thrown
Nothing was changed in perforce or in Bamboo
Any tips as to what is going wrong???
Thanks in advance
--UK
Related
[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
I am trying to build a arm RPI4 crosscompiler and toolchain on cygwin on windows 10 with ctosstool-ng-1.24.0
The process works fine generating a arm RPI4 toolchain from ubuntu 20.4 host but fails on windows 10
The Prebuilt Windows Toolchain for Raspberry Pi have gold linker issue that fails to resolve gtk-3 and gdk-3 dependencies libs on windows. so I am trying to see if a newly generated one will resolve the problem.
ctosstool-ng build fails on cygwin for armv8-rpi3-linux-gnueabihf consistently with a flurry of
[ERROR] /usr/include/sys/features.h:322:5: error: "_FORTIFY_SOURCE" is not defined, evaluates to 0 [-Werror=undef]
followed by
[EXTRA] Installing C library start files
[ERROR] ../include/link.h:43:57: error: unknown type name 'Lmid_t'; did you mean 'pid_t'?
[ERROR] ../sysdeps/posix/dl-fileid.h:27:5: error: unknown type name 'ino64_t'
[ERROR] ../sysdeps/posix/dl-fileid.h:35:17: error: storage size of 'st' isn't known
[ERROR] ../sysdeps/posix/dl-fileid.h:37:37: error: '_STAT_VER' undeclared (first use in this function)
[ERROR] /usr/include/cygwin/core_dump.h:19:10: fatal error: windows.h: No such file or directory
[ERROR] /usr/include/cygwin/core_dump.h:19:10: fatal error: windows.h: No such file or directory
[ERROR] make[3]: *** [../Makerules:287: /cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tlsdesc.h] Error 1
[ERROR] make[3]: *** Waiting for unfinished jobs....
[ERROR] make[3]: *** [../Makerules:287: /cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tcb-offsets.h] Error 1
[ERROR] /usr/include/cygwin/core_dump.h:19:10: fatal error: windows.h: No such file or directory
[ERROR] make[3]: *** [../Makerules:287: /cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/rtld-global-offsets.h] Error 1
[ERROR] make[2]: *** [Makefile:258: csu/subdir_lib] Error 2
[ERROR] make[1]: *** [Makefile:9: csu/subdir_lib] Error 2
[ERROR] /
[ERROR] >>
[ERROR] >> Build failed in step 'Building for multilib 1/1: '''
[ERROR] >> called in step 'Installing C library headers & start files'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions#376]
[ERROR] >> called from: glibc_backend_once[scripts/build/libc/glibc.sh#374]
[ERROR] >> called from: CT_IterateMultilibs[scripts/functions#1586]
[ERROR] >> called from: glibc_backend[scripts/build/libc/glibc.sh#74]
[ERROR] >> called from: glibc_start_files[scripts/build/libc/glibc.sh#38]
[ERROR] >> called from: do_libc_start_files[scripts/build/libc.sh#28]
[ERROR] >> called from: main[scripts/crosstool-NG.sh#696]
[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] >> https://crosstool-ng.github.io/docs/known-issues/
[ERROR] >>
[ERROR] >> If you feel this is a bug in crosstool-NG, report it at:
[ERROR] >> https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR] >>
[ERROR] >> Make sure your report includes all the information pertinent to this issue.
[ERROR] >> Read the bug reporting guidelines here:
[ERROR] >> http://crosstool-ng.github.io/support/
[ERROR] /
[ERROR] (elapsed: 130:50.55)
[131:02] / make: *** [ct-ng:261: build] Error 2
I have tried cygwin gcc version 9.3 and 11.3 and also, under menuconfig, glib2.28 and glib2.24. All of them fail at the "libc_start_files" step after installing kernel_headers.
Steps followed from :
$ ../configure --prefix=<install-dir>
$ make
$ make install
$ ./ct-ng armv8-rpi3-linux-gnueabihf
$ ./ct-ng menuconfig (choose glib 2.28)
$ ./ct-ng build
Link to : build logs .config make and make-install logs
If anyone has else succeeded on building this on windows host please share your steps/configuration.
===[UPDATE 1] ===
It looks like c:/cygwin64//usr/include cygwin env is being included in the compiler options. I located ac_cv_env_CPPFLAGS_value=-Ic:/cygwin64//usr/include in build/build-libc-startfiles/multilib/config.cache. But not sure if thats the one causing linux files into cygwin64 includes.
gawk -f ../scripts/gen-as-const.awk ../sysdeps/arm/tlsdesc.sym |
arm-unknown-linux-gnueabihf-gcc -O2 -D_FORTIFY_SOURCE=0
-mlittle-endian -mcpu=cortex-a53 -mfpu=neon-vfpv4 -mhard-float
-S -o /cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tlsdesc.hT3
-std=gnu11 -fgnu89-inline -O2 -Wall -Wundef -Wwrite-strings
-fmerge-all-constants -fno-stack-protector -frounding-math -g
-Wstrict-prototypes -Wold-style-definition -fno-math-errno
-ftls-model=initial-exec
-U_FORTIFY_SOURCE -Ic:/cygwin64//usr/include
< rest pf of the includes are from under the .build dir >
... -I.. -I../libio -I. -nostdinc -isystem ....
-DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS -x c -
-MD -MP -MF /cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tlsdesc.h.dT
-MT '/cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tlsdesc.h.d
/cygdrive/c/repo/ctng124/bld/.build/arm-unknown-linux-gnueabihf/build/build-libc-startfiles/multilib/tlsdesc.h'
Also its not clear how these propagate from the root build directory into the component build/compiler options.
Any suggestion to track/debug the compiler options will be most helpful.
===
Has anyone encountered these errors?
What could be causing them?
Please share any experience you have on the above.
I cloned a fresh copy of the branch-2.0 branch of Spark from Github onto a Centos 7 system. When executing the suggested command to build from source,
./dev/make-distribution.sh --name custom-spark --tgz -Psparkr -Phadoop-2.4 -Phive -Phive-thriftserver -Pyarn
I get the following errors:
[INFO] Total time: 5.368 s (Wall Clock)
[INFO] Finished at: 2016-08-18T11:56:49-05:00
[error[INFO] Final Memory: 71M/1963M
] [INFO] ------------------------------------------------------------------------
/home/rprechelt/ada/spark/common/tags/src/main/scala/org/apache/spark/annotation/Since.scala:30: error writing class Since: /home/rprechelt/ada/spark/common/tags/target/scala-2.11/classes/org/apache/spark/annotation/Since.class: /home/rprechelt/ada/spark/common/tags/target/scala-2.11/classes/org is not a directory
[error] private[spark] class Since(version: String) extends StaticAnnotation
[error] ^
[error] /home/rprechelt/ada/spark/common/tags/src/main/scala/org/apache/spark/annotation/package.scala:25: error writing package object annotation: /home/rprechelt/ada/spark/common/tags/target/scala-2.11/classes/org/apache/spark/annotation/package.class: /home/rprechelt/ada/spark/common/tags/target/scala-2.11/classes/org is not a directory
[error] package object annotation
[error] ^
[error] two errors found
[error] Compile failed at Aug 18, 2016 11:56:49 AM [0.358s]
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile (scala-compile-first) on project spark-sketch_2.10: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile failed. CompileFailed -> [Help 1]
I'm at a loss for what could be occurring here - I've tried building it with different versions of Scala, but they all report the same error.
Does anyone have any suggestions about how I might go about fixing this?
I got the same problem, this is because zinc server is started by some other user. Trying killing zinc and then starting the build again.
Its basically an access error where zinc server started by another user is trying to write to a different directory.
sudo ps -ef | grep zinc
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.
Without Petsc, I can see which files, which functions, and which lines an error occurs and is propagated from. With Petsc, I always receive the same error message.
Is there any flag in Petsc that I'm missing?
Thanks.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: likely location of problem given in stack below
[0]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[0]PETSC ERROR: INSTEAD the line number of the start of the function
[0]PETSC ERROR: is given.
[0]PETSC ERROR: --------------------- Error Message ------------------------------------
[0]PETSC ERROR: Signal received!
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011
[0]PETSC ERROR: See docs/changes/index.html for recent updates.
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.
[0]PETSC ERROR: See docs/index.html for manual pages.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: ./solver on a linux named ion by khoa Sun Apr 10 23:29:33 2011
[0]PETSC ERROR: Libraries linked from /h1/khoa/libs/petsc-3.1/linux/lib
[0]PETSC ERROR: Configure run at Sun Apr 10 17:52:52 2011
[0]PETSC ERROR: Configure options --with-scalar-type=complex --with-clanguage=c++ --with-mpi=1 --with-mpi-dir=/usr/bin
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Your code has generated a SEGV, probably by illegally accessing memory. As the error message recommends, you should run using valgrind or gdb, which will allow you to see the stack.