I'm working with inet and veins in omnet++, when I build inet project, there is always an error like the following in the console:
please rebuild precompiled header 'inet/common/precompiled_debug.h.pch'
I can not understand how to solve the error. I tried to run ./configure then make clean and make. However the error still exists. I appreciate if anyone can guid me.
make cleanall should solve that, but simply deleting the inet/common/precompiled_debug.h.pch file will also solve the problem.
Related
lsp linting clangd throws a linting error
when doing an include
e.g
#include <iostream> error bits/c++config.h file not found
I already installed mingw(via choco install) and added it to my path
also tried added the includes
enter image description here
same with LLVM!
but when I tried to build a hello world program using cmake it works
as expected.
I also copied the compile_command.json to my root generated by cmake
I been spending 2 days to solve this, but still no luck
here's the linting problem. (lsp clangd windows)
any help is greatly appreciated.
the include errors occur because of wrong lsp clangd config
Finally. ah. sigh.. I fixed it. I'm doing things wrong from the start.
there's no need to add flags to include everything e.g -I that has been missing. There's nothing wrong on the clangd itself. The problem lies on your lsp config.
I'm using windows,powershell, no wsl, nvim -> lunarvim and cmake
the fix is simple you just need to add the compile command path
on your --query-driver on your clang lsp config
after that everything should work nice and smooth
the include errors occur because of wrong lsp clangd config
here is my solution for solving the issue
here's the path that you should have into your --query-driver,
remember it depends on your compile_command.json.
compile_command.json generated by cmake
Your --query-driver should be the same as your command path listed on your compile_command.json
lsp clangd config
after that errors about missing includes should gone by now
errors gone
I'm cross-compiling ecasound, which goes well up to the point that all binaries get compiled, but fails during (at the end of?) the installation phase.
The thing is, I don't see any error message or anything, so I'm left guessing here:
ecasound: installs files in /home/buildroot/buildroot-2018.02-rc2/output/target//home/buildroot/buildroot-2018.02-rc2/output
make[1]: *** [/home/buildroot/buildroot-2018.02-rc2/output/build/ecasound-2.9.1/.stamp_target_installed] Error 1
make: *** [_all] Error 2
Full output: https://pastebin.com/ca6FJebB (hope this contains enough details)
Presumably the ecasound 'make install' returns (silently?) with an error. We don't have an ecasound package in upstream Buildroot, so it is hard to know what you are doing, but the install location (../output/target/home/buildroot/..) certainly looks wrong.
It did work after first doing a complete build, followed by ecasound seperately, indicating it was missing dependencies. Turned out the missing piece here was: BR2_PACKAGE_PYTHON_CURSES.
In case anyone wants to build ecasound for buildroot, a working package is available in my github account.. Not sure if it's clean code/by the book, but it works..
The problem is your install path somehow duplicated itself
/home/buildroot/.../target//home/buildroot/...
I have seen this several times too, and havent really found a way to fix it except to make clean & make again
I am trying to build Linux for my Raspberry Pi 3.
When I do make, I get the below error.
make[2]: /home/rohit/workplace/rp/buildroot/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabihf-gcc: Command not found
A little background will help. I am following this link . To summarize this is what I ran.
make raspberrypi3_defconfig
make linux-menuconfig
make
From the error I get that the cross gcc is not available at the path as it should be. But I am not sure what I am missing.
The complete log of the make is pasted here. The output/host/usr/bin folder also doesn't contain arm-buildroot-linux-uclibcgnueabihf-gcc, though it does contain arm-buildroot-linux-uclibcgnueabi-gcc. I have pasted the contents of the folder here.
Please help.
i was having this problem and after a make clean the problem was solved. I think the error was because different toolchains used in different builds. The manual says that is one of the cases that you have to do a make clean
I am working on a project with the Beaglebone Black and ran into an issue. As part of my project, I would like to use OpenBTS to communicate over the GSM network. However, because the Beaglebone is ARM based, the Transceiver52M that ships with OpenBTS is unusable. Therefore, I need to install an ARM friendly transceiver. The transceiver that I think will do best is Osmo-Trx.
I followed the instructions on their website:
http://openbsc.osmocom.org/trac/wiki/OsmoTRX
However, when it came to making the project, got an error and am really stuck. When I do the command "make" after "./configure --with-neon", I get the error:
make: ***No rule to make target '/Makefile.common', needed by 'Makefile.in'. Stop.
Would anyone be able to help me fix this. I've search around and can't find any applicable answers. I would really appreciate it. Thank you so much in advance!
P.S. All the source code for the OsmoTRX can be found at: https://github.com/osmocom/osmo-trx
A missing Makefile is often caused by a missed/failed step in the autotools process.
My suspcion is that you either forgot to run autoreconf -i or it wasn't successfull. Try
cd osmo-trx
git clean -xdf ##Attention: clean slate afterwards!
autoreconf -i ##make sure it reports success
./configure --with-neon ## make sure it reports success
make ## make sure it reports success
sudo make install
I'm trying to build a package from source. The ./configure and make steps work out, but sudo make install or sudo checkinstall results in an error:
As we can see drbd is listed twice in the /usr/bin/install -c line.
The problem is I don't really know how to go about this. As expected, this list of files (ha resource agents) is not present in any of the Makefiles or install-sh, but generated somehow on the go.
Any ideas of where to look for or how to remove duplicate entry from this list? Thank you.
Actually I was mistaken and the above list was present in one of Makefile.am files. Here is the post that helped me out:
This issue is caused because for those earlier versions we incorrectly
had those specified files listed twice in the Makefile.am and with the
newer Automake versions this causes the errors you received.
p.s. Sorry, it was a haste to ask the question. Let this thread be for reference in that case.