I am getting the following error along with a lot of others when trying to compile jobs on DataStage 11.7:
Error when checking composite operator: Subprocess command failed with exit status 256
I did an internet search of all possible solutions. Could not look at dsxchange as the site is down. Looked at all compiler options and they look the same as other projects with successful compilation.
IBM has a solution but it did not work for me:
https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.ds.trouble.ref.doc/topics/transformstage01.html
Any ideas?
There are 165 hits on DSXchange (it is not down).
Can you please verify your operating system and the values of the four environment variables that control your compiler and linker (APT_COMPILER, APT_COMPILEOPT, APT_LINKER and APT_LINKEROPT)? Please also verify the exact version of DataStage that you are running and the exact version of the compiler.
As noted in the Knowledge Center article, this error usually relates to the compiler being incompatible, the incorrect version, or having incorrect options.
Related
Ugh....Microsoft have done something.
All our builds that have been kicked off in the last few hours (approx 10:00 GMT) are failing on our "Build Solution step" failing because of the following error (from the logs):
##[error]EXEC(0,0): Error : Error occurred during processing of input file 'XXX.XXX.dll' --> Method not found: 'System.ReadOnlySpan1 Microsoft.IO.Path.GetFileName(System.ReadOnlySpan1<Char>)'.
Does anyone have any ideas on this? Nothing in our codebase has changed.
If you need more information please let me know. Thanks
FYI, this seems to be caused by a recent update to MSBuild (https://github.com/dotnet/msbuild/pull/7680) that has updated the version of System.Memory.
It looks like the obfuscation tool you're using in your build pipeline is built against a previous version of System.Memory and now that the version provided by the MSBuild environment has changed, the obfuscation tool is broken. Most likely requires the obfuscation tool to be updated.
(PS. I'm just relaying the information that others have identified where other tools are having the same issue - see https://github.com/T4MVC/R4MVC/issues/172)
dart2js error with dash_chat
One of our existing applications makes use of dash_chat, which is working on a V2, however, v2 has a fraction of the APIs implemented. The project is somewhat dormant so today we just doing housekeeping and trying to keep the project up-to-date.
I am now getting this error, and sadly I went and updated all packages and we are using FLutter 3 and Dart 2.17 in all our other projects.
Target dart2js failed: Exception: Warning: The 'dart2js' entrypoint script is deprecated, please use 'dart compile js' instead.
So not sure which of the many things I changed is ultimately the cause of this issue, which crops up when trying to build for web.
No relevant issues on the DC repo and google is being very unhelpful on this one, was hoping someone had some insight that would allow me to take the correct steps forward (or back if need be) to get around this.
TIA
I followed the Flow installation guide for npm & babel and when I get to the second stage where you flow init I keep getting the error message zsh command not found: flow. I installed flow into my project (a branch of my Gatsby blog) for testing/debugging purposes. It is not installed globally, which is what the Flow docs state is the best practice:
Flow works best when installed per-project with explicit versioning rather than globally.
I have been having a similar issue with Lume that returns zsh command not found: lume
If I enter echo $PATH
The colon delimited list should have user/local/.deno/bin:$PATH but it is not there. If I add it by running:
export PATH="/Users/yourUserName/.deno/bin:$PATH"
Than I am able to run lume commands. However, when I try to run lume commands the next day I have to go through the whole process once more as the error crops up again...
My question here today is regarding the Flow error and getting it sorted. I only mention the Lume error because it makes me fairly certain something is messed up in $Path or my Zsh config. I am just not sure what. The only caveat to that hunch though is that Deno is a global install, whereas Flow is installed directly into my project...
So, maybe the two errors while the same syntax are totally separate?
Thank you in advance for any guidance/suggestions. Cheers!
I came across this video from 2017 no less and the host had issues with flow not working within the project and so he installed it globally. I gave it a shot and the flow error zsh command not found: flow has been resolved...
I have C/C++ application and I am trying to run cov-build and getting a warning “ NO FILES EMITTED”. Can you please help me as we doing the POC on Coverity for static code analysis.
C:\Users\Master\bamboo-agent-home\xml-data\build-dir\DEC-L11PROJ-JOB1>cov-build --dir cov-int IarBuild.exe MainApplication\EWARM\L11_P4_uC1.ewp -build *
Coverity Build Capture (64-bit) version 2019.03 on Windows 10 Enterprise, 64-bit (build 18362)
Internal version numbers: 2c0f9c8cf4 p-pacific1-push-35439.872
IAR Command Line Build Utility V8.4.8.6680
Copyright 2002-2020 IAR Systems AB.
Total number of errors: 0
Total number of warnings: 0
[WARNING] No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
For more details, please look at:
C:/Users/Master/bamboo-agent-home/xml-data/build-dir/DEC-L11PROJ-JOB1/cov-int/build-log.txt
First, if you are involved in a pre-sales Proof of Concept (POC), then there should be a Coverity Sales Engineer assigned to help with the POC. That person's role includes providing instructions and information similar to what I'll offer below, as well as answering technical questions such as yours. There may have been a miscommunication somewhere. Get in contact with the Sales Engineer, as they will be able to help more reliably and completely than I can.
Now, what's going on? The primary purpose of cov-build is to watch the build process for invocations of compilers, and when one is found, compile the same code using the Coverity compiler (called cov-emit). But in order to recognize a compiler, cov-build needs to know its command line name, what kind of compiler it is, where its include files are stored, etc. This is accomplished by a helper tool called cov-configure that must be run before cov-build. If cov-configure has not been run, then no compiler invocations will be recognized, which appears to be the case for you, as indicated by "No files were emitted".
Synopsys has a page called CLI Integration Cheat sheet that gives these commands for use with IAR:
cov-configure --comptype iar:arm --compiler iccarm --template
cov-build --dir <intermediate directory> "c:\Program Files (x86)\IAR Systems\Embedded Workbench 6.5\common\bin\IarBuild.exe" sample_project.ewp -build Debug -log all
I can't personally vouch for these commands (I don't have IAR, nor access to the Coverity tools anymore; I'm a former employee), but something like that will be needed. Again, your assigned Sales Engineer should be able to help.
Finally, for new Coverity users, I recommend using the cov-wizard tool. cov-wizard is a graphical front-end to the command line tools, and has help text explaining the concepts and procedures, along with a convenient interface for performing them. There are several steps even after cov-build, and cov-wizard will walk you through all of them. Its final screen shows exactly what command lines it used in case you want to script them.
I've just connected to a machine I never worked on, and tried to run Eclipse there. Unfortunately, I got the error:
Eclipse:
JVM terminated. Exit code=14
(my configuration details here)
I guess there's either a problem with my configuration or with that machine's setup, but Exit code=14 does not give me a lot of information to go on. What does that mean? Where should I start?
I intentionally omitted my configuration details because I'm looking for a general explanation of that exit code, not a specific fix for my configuration.
It could be related to bug 9027: Workbench should check JDK version on startup
You could have an incompatible (ie too old) JVM: the code 14 has been referenced in this comment as:
The main launcher detects the JVM terminates with exit code 14. Is the
following message sufficient?
Please use a newer VM. Eclipse requires at least 1.3.1.
It can also be related with an incompatibility between what is installed on the system and what Eclipse needs when launching: see for instance this example.
Just to add to #VonC's answer, the Eclipse source code has this to say:
// Check to see if we are running with a compatible VM.
// If not, then return exit code "14" which will be recognized
// by the executable and an appropriate message will be displayed
// to the user.
if (!isCompatible())
System.exit(14);
(Source: http://svn.netlabs.org/repos/swt/trunk/src/plugins/org.eclipse.platform/src/org/eclipse/core/launcher/Main.java)
So I suggest checking whether you have a compatible JVM.