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.
Related
I am trying to build a hello world project to see if gtk4-rs is working correctly, which always fails at creating the binaries. The rest of the build seems to fine (tried to run cargo clean and cargo check a couple of times, those do not produce any errors). My Cargo.toml just uses the version specified in the crate:
[dependencies]
gtk4 = "0.4.8"
My error is exactly the same as the one in this question, but running the cargo build in an admin powershell also fails with the same error.
I am on Win 11 and I've followed the installation instructions linked to by GTK themselves, https://github.com/wingtk/gvsbuild.
The linking error seems to indicate that gobject-2.0.lib is missing:
LINK : fatal error LNK1181: cannot open input file 'gobject-2.0.lib'
(Full error message (with redacted user directory) on Pastebin)
That file is found at c:\gtk-build\gtk\x64\release\lib, which is the default location for an installation produced by gvsbuild, as far as I can tell (I haven't messed with the files at all).
Both c:\gtk-build\gtk\x64\release\lib and c:\gtk-build\gtk\x64\release\bin are part of the path, restarting the machine did not seem to fix anything in this regard either.
I have not found anything close to helpful on the internet, so any pointers to what could be wrong here would be great.
I am working on a project that uses yocto project (bitbake) and an operating system using q++/qcc compiler. When I call bitbake to build my packages, it does not show the q++/qcc warning messages in the console log as well as the log file.
The only way I can see these warnings is when I run bitbake --verbose , but along with it, I get all the other log processes information. Is there any way to work around this issue such that I can only see the q++/qcc warnings that were detected during the compilation of the C++/C source files?
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.
I'm trying to compile geany-plugins-1.28. The debugger plugin (the only one I need) gives the error:
debug.c:53:21: fatal error: vte/vte.h: No such file or directory
#include <vte/vte.h>
Clearly it needs to know where this file is located to compile. I found the vte.h file in the src directory of the main program geany-1.28. When running
sudo ./configure cflags=-I/home/pi/Desktop/geany-1.28/src
I get the same error about the missing header later trying to compile the debugger plugin.
I ran
./configure --help
to get all the flag options. The output is here
How do I get this to configure correctly so that it compiles. I need to compile the debugger version 1.28 myself because apt only installs 1.24 which I think has a bug because it crashes when I run my code with the error:
close failed in file object destructor:
sys.execpthook is missing
lost sys.stderr
CFLAGS is case-sensitive environment variable, so you should set it before running configure, not try to pass it as a command line argument. This variant:
$ export CFLAGS=-I/home/pi/Desktop/geany-1.28/src
$ ./configure
leaves CFLAGS set for current shell until you leave it. While this:
$ CFLAGS=-I/home/pi/Desktop/geany-1.28/src ./configure
sets variable only for current command, i.e. configure.
Some other issues:
You do not need sudo to configure and make. It is also unnecessary for make install if you set PREFIX to a path you have privileges to write to.
Does plugin's build system also builds all it's dependencies? If not, you may face linker errors a bit later.
Update:
I have tried to build debugger plugin and got rid of your error. It seems that vte.h coming with Geany is it's intrinsic, while the plugin requires full-featured file from the library. So I just installed vte and vte-devel from repos. Nevertheless, I got some other unrelated errors coming from Glib. I will not continue my attempts to build all this right now. Hope my effort will be helpful at least a little.
As in this answer stated, vte.h is not the file you are looking for. Install libvte(-dev) package on your system and rerun configure.
Just for the record: vte.h on Geany is a dummy to allow Geany to kind of dynamical enable vte or disable it depending on vte is installed on the system or not.
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.