I am trying to build Rails from source for the latest stable (4.2) version from the branch 4-2-stable; however I am getting a segmentation fault at 'activesupport' for rake tests.
The details of error log are as below:
Platform I am trying on: Ubuntu 14.10 Rails Version: 4.2.3 Ruby
Version: 2.2.2 & 2.1.6 (on both versions getting same trace)
Log:
** Invoke test (first_time)
** Execute test
/home/test/.rvm/rubies/ruby-2.1.6/bin/ruby -w -I"lib:test"
-I"/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib" "/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/rake_test_loader.rb"
"test/**/*_test.rb"
Run options: --seed 36135
Running:
................................................................................................................................................................................ Segmentation fault
rake aborted!
Command failed with status (139): [ruby -w -I"lib:test"
-I"/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib" "/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/rake_test_loader.rb"
"test/**/*_test.rb" ]
/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/testtask.rb:108:in
`block (3 levels) in define'
Can anyone provide any pointers so as to fix this?
Related
Title says it all - I am attempting to run a very basic Rust program using hyper_wasi, and everything compiles seemingly ok using cargo wasi run. Unfortunately when it actually executes, I get:
Error: failed to run main module `target/wasm32-wasi/debug/<my project name here>.wasm`
Caused by:
0: failed to instantiate "target/wasm32-wasi/debug/<my project name here>.wasm"
1: unknown import: `wasi_snapshot_preview1::sock_setsockopt` has not been defined
Execution environment is a rather older Mac (2013 MBP with Big Sur), clang version:
Homebrew clang version 15.0.3
Target: x86_64-apple-darwin20.6.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin
If anyone can point me at what I might be missing I'd appreciate it.
I'm trying to run Node.js app (12.x or 14.x) that uses IBMMQ 0.9.17 library in Docker container and getting this error:
Error: Dynamic Linking Error: Error loading shared library /opt/mqm/lib/libmqm_r.so: Exec format error
C client has been installed and env variables set properly:
LD_LIBRARY_PATH = /opt/mqm/lib64:/opt/mqm/java/lib64:
DYLD_LIBRARY_PATH = /opt/mqm/lib64:/opt/mqm/java/lib64:
Docker Image:
Darwin Kernel Version 20.5.0
what does "Exec format error" mean?
I've followed all the steps in the official guide. Except I built it using:
$ bazel build -c opt --copt=-mavx --copt=-mavx2 --copt=-mfma --copt=- msse4.1 --copt=-msse4.2 --config=opt -k //tensorflow/tools/pip_package:build_pip_package
And during ./config I've set the right paths and disabled Google Cloud Platform, Hadoop, XLA, VERBS, OpenCL, CUDA, MPI support.
Hardware:
Macbook Pro 13 inch (mid 2014)
CPU: Intel Core i5 (4278U)
RAM: 8GB
Software:
High Sierra (10.13.2)
Clang Version: clang-900.0.39.2
Bazel Version: 0.9.0
Conda Version: 4.4.3
Python: 3.6.3
All the packages are upto date. This worked perfectly fine 2 months ago on this machine. For some strange reasons it doesn't build anymore now. I'm just posting a part of the error list here:
WARNING: Config values are not defined in any .rc file: opt
ERROR: Skipping 'msse4.1': no such target '//:msse4.1': target 'msse4.1' not declared in package '' defined by /Users/rakshithgb/Documents/Tensorflow/tensorflow/BUILD
WARNING: Target pattern parsing failed.
ERROR: /private/var/tmp/_bazel_rakshithgb/fde7bc60972656b0c2db4fd0b79e24fb/external/com_googlesource_code_re2/BUILD:96:1: First argument of 'load' must be a label and start with either '//', ':', or '#'. Use --incompatible_load_argument_is_label=false to temporarily disable this check.
ERROR: /private/var/tmp/_bazel_rakshithgb/fde7bc60972656b0c2db4fd0b79e24fb/external/com_googlesource_code_re2/BUILD:98:1: name 're2_test' is not defined (did you mean 'ios_test'?)
ERROR: /private/var/tmp/_bazel_rakshithgb/fde7bc60972656b0c2db4fd0b79e24fb/external/com_googlesource_code_re2/BUILD:100:1: name 're2_test' is not defined (did you mean 'ios_test'?)
And it ends like this:
ERROR: /Users/rakshithgb/Documents/Tensorflow/tensorflow/tensorflow/core/kernels/BUILD:550:1: Target '#local_config_sycl//sycl:using_sycl' contains an error and its package is in error and referenced by '//tensorflow/core/kernels:debug_ops'
WARNING: errors encountered while analyzing target '//tensorflow/tools/pip_package:build_pip_package': it will not be built
INFO: Analysed target //tensorflow/tools/pip_package:build_pip_package (203 packages loaded).
INFO: Found 0 targets...
ERROR: command succeeded, but there were errors parsing the target pattern
INFO: Elapsed time: 12.763s, Critical Path: 0.02s
FAILED: Build did NOT complete successfully
Has anyone else had this issue? How do I fix it? I've uploaded the entire error log on GitHub Tensorflow issue page. #15622
Ok it looks like the new bazel version isn't compatible with the current Tensorflow release. It looks like the fix will be issued in the next release. According to this thread on GitHub - #15492
The temporary fix that worked for me was to build it using --incompatible_load_argument_is_label=false in the bazel command. So my build command now looks like this:
$ bazel build --config=opt --incompatible_load_argument_is_label=false //tensorflow/tools/pip_package:build_pip_package
I am using Groovy/Gradle with Cucumber framework. following are the versions
Groovy Version: 2.4.4
------------------------------------------------------------
Gradle 2.5
------------------------------------------------------------
Build time: 2015-07-08 07:38:37 UTC
Build number: none
Revision: 093765bccd3ee722ed5310583e5ed140688a8c2b
Groovy: 2.3.10
Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013
JVM: 1.7.0_17 (Oracle Corporation 23.7-b01)
OS: Windows 8 6.2 amd64
I am getting this error when I try to run following
$ gradle clean idea
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\Documents and Settings\Sudheerah\Documents\Sudheera\KBase\APDM\APIAutomation\build.gradle' line: 76
* What went wrong:
A problem occurred evaluating root project 'APIAutomation'.
> Could not find method groovy() for arguments [org.codehaus.groovy:groovy-all:2.4.4] on root project 'APIAutomation'.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 35.237 secs
Below is the build.gradle file error line.
Stacktrace
Caused by: org.gradle.api.internal.MissingMethodException: Could not find method groovy() for arguments [org.codehaus.groovy:groovy-all:2.4.4] on root project 'APIAutomation'.
at org.gradle.api.internal.AbstractDynamicObject.methodMissingException(AbstractDynamicObject.java:68)
Assuming you've applied the groovy plugin, you need to change your groovy dependency to a compile dependency.
The groovy dependency is the old way of setting up the groovy plugin
In the last few days we've had a previously working AWS Cloud Formation and associated Chef script start failing. At this point there does not seem to be any identifiable reason for this. If anyone has any insights as to the potential cause and/or solution to this we'd love to hear it. Below is the error log from chef-client.log:
[2015-03-26T23:20:31+00:00] INFO: Processing execute[resize2fs /dev/xvda1 2>/dev/null] action run (base::default line 26) [2015-03-26T23:20:31+00:00] INFO: execute[resize2fs /dev/xvda1 2>/dev/null] ran successfully [2015-03-26T23:20:31+00:00] INFO: Processing yum_package[git] action install (base::default line 29) [2015-03-26T23:20:34+00:00] INFO: Processing yum_package[htop] action install (base::default line 30) [2015-03-26T23:20:34+00:00] INFO: yum_package[htop] installing htop-1.0.1-2.3.amzn1 from amzn-main repository [2015-03-26T23:20:38+00:00] INFO: Processing directory[/var/builds/dependencies/] action create (base::common_dependencies line 9) [2015-03-26T23:20:38+00:00] INFO: directory[/var/builds/dependencies/] created directory /var/builds/dependencies/ [2015-03-26T23:20:38+00:00] INFO: Processing s3_file[/var/builds/dependencies/deploy_key] action create (base::common_dependencies line 14) [2015-03-26T23:20:38+00:00] INFO: Processing chef_gem[rest-client] action install (dynamically defined)
================================================================================ Error executing action `install` on resource 'chef_gem[rest-client]'
================================================================================
Mixlib::ShellOut::ShellCommandFailed
------------------------------------ Expected process to exit with [0], but received '1'
---- Begin output of /opt/chefdk/embedded/bin/gem install rest-client -q --no-rdoc --no-ri -v "1.8.0" ---- STDOUT: Successfully installed netrc-0.10.3 Building native extensions. This could take a while... STDERR: WARNING: You don't have /.chefdk/gem/ruby/2.1.0/bin in your PATH,
gem executables will not run. ERROR: Error installing rest-client:
ERROR: Failed to build gem native extension.
/opt/chefdk/embedded/bin/ruby -r ./siteconf20150326-4306-ptf6fb.rb extconf.rb checking for main() in -lstdc++... *** extconf.rb failed
*** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/opt/chefdk/embedded/bin/ruby
--with-stdc++lib
--without-stdc++lib /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:467:in `try_do': The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first.
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:552:in `try_link0'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:567:in `try_link'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:753:in `try_func'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:984:in `block in have_library'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:929:in `block in checking_for'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:351:in `block (2 levels) in postpone'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:321:in `open'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:351:in `block in postpone'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:321:in `open'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:347:in `postpone'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:928:in `checking_for'
from /opt/chefdk/embedded/lib/ruby/2.1.0/mkmf.rb:979:in `have_library'
from extconf.rb:2:in `<main>'
extconf failed, exit code 1
Gem files will remain installed in /.chefdk/gem/ruby/2.1.0/gems/unf_ext-0.0.6 for inspection. Results logged to /.chefdk/gem/ruby/2.1.0/extensions/x86_64-linux/2.1.0/unf_ext-0.0.6/gem_make.out
---- End output of /opt/chefdk/embedded/bin/gem install rest-client -q --no-rdoc --no-ri -v "1.8.0" ---- Ran /opt/chefdk/embedded/bin/gem install rest-client -q --no-rdoc --no-ri -v "1.8.0" returned 1
Cookbook Trace:
--------------- /etc/chef/local-mode-cache/cache/cookbooks/s3_file/providers/default.rb:8:in `block in class_from_file'
Compiled Resource:
------------------
# Declared in
chef_gem("rest-client") do action :install retries 0 retry_delay 2 default_guard_interpreter :default package_name "rest-client" version "1.8.0" timeout 900 gem_binary "/opt/chefdk/embedded/bin/gem" end
The rubygem rest-client was updated recently:
1.8.0 - March 24, 2015 (122 KB)
This adds a dependency to http-cookie gem, which resolves in dependencies to domain_name, unf and unf_ext which needs a C++ compiler and libstdc++ (https://github.com/knu/ruby-unf_ext, Requirement)
For CentOS this means: yum install gcc-c++ libstdc++-devel
I created an issue on their bug tracker (https://github.com/rest-client/rest-client/issues/371)