Can't build MonoDevelop on an embedded Linux - linux

Good day!
I'm trying to build MonoDevelop on/for an embedded/minimal Linux, and can't build msbuild from source which is why I'm using the binary from this DEB package.
This basically works as it seems, but now make ends with an error:
configure output
make output
Can someone please help me to get MonoDevelop built?

I see two errors in your build log:
/update/download/monodevelop-7.8/src/addins/VersionControl/MonoDevelop.VersionControl.Git/MonoDevelop.VersionControl.Git.csproj(146,5):
error MSB3073: The command "bash build_libgit2.sh" exited with code
-1.
"/update/download/monodevelop-7.8/Main.sln" (default target) (1) ->
"/update/download/monodevelop-7.8/external/fsharpbinding/MonoDevelop.FSharpBinding/MonoDevelop.FSharp.fsproj"
(default target) (81) ->
/update/download/monodevelop-7.8/external/fsharpbinding/MonoDevelop.FSharpBinding/MonoDevelop.FSharp.fsproj(33,3):
error MSB4019: The imported project
"/update/swroot/lib/mono/xbuild/Microsoft/VisualStudio/v15.0/FSharp/Microsoft.FSharp.Targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
For the latter, did you install F#? (Just apt-get install fsharp should suffice.) And for the second, try running bash build_libgit2.sh separately to see the error message.

Related

How to resolve error in debugging a program in totalview?

I installed TotalView on Ubuntu. For the begining I just tried to debug a very simple Hello Word program in but I got the following error:
"Fatal Error: Can't set up library cache directory -- cannot debug this target. Do you want to run the TotalView Diagnostic Tool?"
I don't know what is the library cache directory. Any idea about the library cache directory in ubuntu can be helpful.

MiXiM building no such file or directory error

I failed to build the MiXiM on Ubuntu 14.04.3 and OMNet 4.6, the error message is: ”fatal error: Mac80211Pkt_m.h: No such file or directory”. From the manual of OMNet it can be found that the file Mac80211Pkt_m.h should be generated automatically by the compiler during the building process, but it was shown by the error message that the file was not generated automatically. I am confused about the problem, how can I solve this? Can anyone help me? Thanks!
I faced the same error message. Here is how I bypassed the problem:
Extract "mixim-2.3.tar.gz" (tar xvzf mixim-2.3.tar.gz)
Change into the directory just extracted (cd mixim-2.3)
Execute "make makefiles"
Start the build by "make"
Import the just built project using the omnet++ IDE

ERROR: executing command 'ant' - After installation and setting ANT_HOME

After wrestling with my environment variables to get the proper directory set, I can now get the version with:
C:\Projects\TestProj>ant -version
Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ant appears to be working:
C:\Projects\TestProj>ant
Buildfile: build.xml does not exist!
Build failed
I still get the error when I try:
C:\Projects\TestProj>cordova -d platform add android
cordova library for "android" already exists. No need to download. Continuing.
Checking if platform "android" passes minimum requirements...
Creating android project...
Running command: C:\Users\Administrator\.cordova\lib\android\cordova\3.4.0\bin\c
reate.bat --cli C:\Projects\TestProj\platforms\android com.company.testproj
TestProj
C:\Users\Administrator\.cordova\lib\android\cordova\3.4.0\bin\node_modules\q\q.j
s:126
throw e;
^
Error: ERROR : executing command 'ant', make sure you have ant installed and add
ed to your path.
From all of the posts that I have read, this is an issue with ANT_HOME, but it appears I have that part of it tackled. Edit I've installed ant 1.9.3 to program files, and bin resides in:
EDIT Changed to just ant, instead of apache-ant-1.9.3-bin\apache-ant-1.9.3
C:\Program Files\ant
Echo home:
C:\Projects\TestProj>echo %ANT_HOME%
C:\Program Files\ant
And of course I have %ANT_HOME%\bin in my path. Any help identifying the issue would be appreciated.
I think the path you use for ANT_HOME is wrong. C:\Users\Administrator\AppData\Roaming\npm\node_modules\ant\ant seems to be the path to the ant npm module but not the ant command.
Ant command more probably is somewhere in program files. In a cmd, run where ant to know where in your path ant is found and use this path for ANT_HOME. (in the folder you should see ant, ant.cmd and ant.bat)
After further investigation, I think your problem is caused half by cordova not correctly checking node errors and half because of registry setting in your computer (a cmd autorun parameter).
You can check answers in those posts for more info:
nodejs child_process exec 'java -version'
Windows CMD.exe "The system cannot find the path specified."
Check if you have a registry key HKCU\Software\Microsoft\Command Processor\AutoRun
after setting the variables, restart your machine. Closing command prompt etc will not help.
Even I was stuck for quite a long time and next day when I started my system, it was working fine :P

Coverity Set Up (Cygwin Warning)?

I am currently trying to run Coverity Prevent and I believe I have everything set up appropriately on my windows 7 build machine. I have run it with AnthillPro and when my code finishes and gets to Coverity it says that everything was built fine and the only error I get is:
Warning: Cygwin pathname conversion ignored; no applicable
'bash'/'mount', 'cygpath', or registry keys found.
I have even tried to install Cygwin to see if this could rectify the problem and I still end up with the same error.
I am currently using AnthillPro 3.7 and Coverity 5.5.3. The build log says that I have warnings but no errors and that it hasn't emitted anything. I have tried to run a script directly from the machine (not server) itself and I have the same error as I do using the Coverity Prevent in Anthill
This is the only information I get at the bottom of the build log.
Run from AnthillPro:
Build time (cov-build overall): 00:00:17.753597
[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:
d:\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
Run from Script:
The cov-build FAILED.
This may be because less than 90 percent of units were successfully compiled
Check for errors here:
D:\\Coverity\Scripts\build_AllToolsProjects.sln_pc_vs2010.bat
D:\\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
D:\\Coverity\Configuration\pc_vs2010
It sounds like you haven't configured the compiler - that's when you tell your Coverity Analysis installation which compiler you are using. devenv is not a compiler, cl.exe is.
Run the following command:
coverity-analysis-dir/bin/cov-configure --msvc
This will say that you are using the cl.exe compiler and it's of type msvc no matter where it's installed.
Then rerun your Coverity build and see if it captures more of your compilations.

BeagleBoard Narcissus ToolChain with OpenCv issue

I'm using Eclipse with Narcissus Cross-Compiler Toolchain to compile OpenCV project on my BeagleBoard-XM.
I followed those links to do this:
http://www.lvr.com/eclipse1.htm
http://groups.google.com/group/beagleboard/browse_thread/thread/1ec0c6585a2141c8?pli=1
When i try to compile the project i get an Error:
Description Resource Path Location Type
make: *** [hello_world.o] Error 1 hello_world C/C++ Problem
I think the problem is with the Toolchain itself, Any Ideas?
The CDT framework runs GNU Make under the hood to do the actual build (unless you are using the internal builder, which isn't the default). The error you see is because one of the makefile targets, of the managed project's auto-generated makefile, has failed to run successfully.
The output of the Problem view is insufficient information to answer your question. Only the Console view output for the build contains sufficient information to diagnose the problem. Please post the entire output of the CDT Build Console for the Console view.
At this point the only guess we can make is that something in the build process exited with exit code 1.

Resources