Pushing the envelope of build performance
Yuri Shtil's Discussions
SparkBuild error not present in regular build
37 Replies
I get a number of errors introduced by SparkBuild:--- Start Quote ---Step 'compilation' - 3 Errors, 291 Warningserror Error #1 of 3 in step 'compilation'log referencecompilation.353053.log:61579 (src)Continue
Started this discussion. Last reply by Eric Melski Oct 30, 2009.
Using SparkBuild with Visual Studio (via devenv)
4 Replies
We run Windows builds via Electric Commander using command line devenv.How do I use SparkBuild in this environment? Do I need to generate an nmake file from the solution file?How do I do it from the…Continue
Started this discussion. Last reply by Yuri Shtil Oct 16, 2009.
Does SparkBuild require Accelerator
7 Replies
I have installed SparkBuild and ran a build but could not find the annotation file.emake help sais that it only created when running under Accelerator.Am I missing something?Continue
Started this discussion. Last reply by Scott Castle Oct 14, 2009.
Yuri Shtil's Page
Latest Activity
Eric Melski replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Yuri, that's an interesting discovery! Hopefully in a future release we'll be able to make SparkBuild emake write annotation to a file the same way that ElectricAccelerator emake does.
Best Regards,
Eric Melski
Architect
Electric Cloud,…
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
I guess the problem is that the build calls make and tries to use its output, emake annotates the output which look like garbage to the code reading it.
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
The compilation aborts with the following error message:
checking whether make sets $(MAKE)... ./configure: eval: line 20417: syntax error near unexpected token `<'
./configure: eval: line 20417: `
Eric Melski replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Yuri, it looks like there are two types of problems with the annotation file. First, you are using the 'clear' command in the middle of your build for some reason. This emits control characters that are normally interpreted by the terminal…
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Hi Duc,
Did you have a chance to look into this?
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Thank you
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
I attached one of the annotation files. Try to open it with sbinsight.
Duc Nguyen replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
I am not sure what you mean by this. Is postp still picking up WARNING/ERROR strings from the annotation file?
Duc Nguyen replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
If the problem has went away, then you can just turn off logging entirely by removing the --emake-logfile and --emake-debug flags.
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
However, the annotation files are full with things like
I cannot put here.
I guess makefiles echo special characters and the file would not load.
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Duc,
It was all my fault. We run more on more than one resource but I specified the same paths for both
steps, I separated the xml and db paths and everything is better now.
I don't want the huge log files, how do I lower the verbosity?
Duc Nguyen replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
since the script is so simple, could you try logging directly onto the commander resource that was used to run it originally, and run the script directly from there? I'm trying to figure out if it's something in the commander environment…
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
There you go. The full script attached, it is very short.
Duc Nguyen replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
Are the emake commands in the commander step body? If so, can you show me the contents of the command block for the step where the two emake commands were invoked?
Yuri Shtil replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
There is no reply option on the message below.
The two make invokations are in the same step.
They obviously run on the same resource one after another.
What other information can I provide to help you?
Duc Nguyen replied to Yuri Shtil's discussion 'SparkBuild error not present in regular build'
EC1155 refers to emake not being able to access the subbuild database file (invalid path, bad permissions etc.) or a child emake not being able to connect to the parent emake for subbuild information.
Are you running the phase1 and phase2 builds…
Comment Wall
- No comments yet!
© 2012 Created by Electric Cloud Administrator.
