I have an already built linux kernel image (zImage) and I want to generate the source for it.
However I'm facing trouble in that: I understand major/minor numbers meaning but I couldn't compile the same version:
target version: 4.5.0-00183-g4647b69-dirty
I even don't know the meaning of "00183-g4647b69-dirty" and how apply it.
thank in advance.
NB: I've copied the config.gz from the target kernel but in vain.
Both my own image and the other one are cross-compiled
I think you have a CONFIG_LOCALVERSION_AUTO=y. This option gets the kernel name from the "git describe" output.
In your version 4.5.0-00183-g4647b69-dirty,
"4.5.0" means the kernel version tag v4.5.0,
"00183" means you have 183 commits on top of v4.5.0
"g4647b69" means your HEAD commit SHA1 is 4647b69. (g is a prefix)
"-dirty" means you have local changes not committed to git.
What you probably need is CONFIG_LOCALVERSION=. You will be able to recreate your builds with this.
Related
I am trying vsomeip on the latest yocto/poky branch kirkstone. I modified the yocto recipe to some extent. Hardcoded Vsomeip to be 3.1.20.1 with no patches and chose BOOST 1.74 after lot of experiments and errors. But still compilation fails. I get a string of errors like:
/basic_socket_ext_local.hpp:133:7: error: no matching function for call to 'boost::asio::detail::io_object_impl<boost::asio::detail::reactive_socket_service_ext_local<boost::asio::local::stream_protocol_ext>, boost::asio::executor>::io_object_impl(boost::asio::io_context&)'
Can anyone tell me the right BOOST version that is compatible with VSOMEIP version? or any patch for 3.1.20 (the patch that came 0001-Support-boost-v1.66.patch didnt work either) Any repo with vsomeip on kirkstone available?
I want to install a previous, specific version of k8slens (https://k8slens.dev/) but impossible for me to find this (neither for mac nor windows !) Do I have to download the source code and rebuild it? Even with this there is no "install" section in the makefile !
Why is it so difficult to find a specific version?
Yes, you can easily download the source code for a specific version tag and the compile and use it. The list of tags is here.
Once you get the source code of your desired version you can generate the binary with :
make build
And then simply run that binary to get your required version. Just know that install simply means copying a compiled binary in a known Path of the system so it can be executed. There is nothing special about it.
The question was made some time ago but just in case you haven't reached the answer yet, One thing I did to solve this problem was that i went to the lens repo : https://github.com/lensapp/lens/releases and search through the old release versions seeking for a binary asset (.exe) (the news version provide the source code but not the binary) then i managed to find the binary of the version 4.2.3. ( release in Apr 26, 2021)
Worked perfectly for me. Hope it helps
I opened VSCode and was presented with a notification that there was a conflict between two versions of a file. I followed the prompts and got a side-by-side comparison of two versions. I clicked the button that accepts the newer version, believing that VSCode had correctly inferred which version was newer. It had not, and I lost a significant number of changes to the file. Is there a cached copy of the other version anywhere?
Thank you!
ps - I seem to have failed to actually commit the changes in git as well. Not sure how that happened.
After searching through the VSCode appdata, I concluded that it wasn't likely that there was a copy. I found a copy of the bytecode (.pyc file) and used uncompyle6 to get an approximate copy of the version of the .py file I needed to recover. Was able to manually merge from there.
I was flummoxed by this one too. The answer is that you can restore the old version by hitting undo until before the change was made.
Summary:
I created a patch in my local machine, but I need to apply this patch in a remote machine.
I'm using Tortoise in both machines. How can I do this in a proper way ?
Context:
I have development environment in a project that is not very common, I guess. I could develop it in a remote VM, but the Eclipse and the entire machine are so slow that I think is unproductive. Also, I have to use a VPN to connect to the VM, which makes my connection slower. Because of that, I want to develop in my local machine, but, for the build I need to apply this patch in this remote VM to test if the changes were made correctly. I noticed that a patch can't be applied to a unversioned file, for that, I have to clean my entire remote repository with Tortoise and apply the patch again. But I wonder if this is the best approach.
If you are working with two build environments, you have to version ALL of the source files. The only thing that will not be under version control are the build directory and the machine-specific configuration files.
So if a file is not under version control somewhere, it is likely because your project setup is not correct. Take the time put everything in a single folder that can be under version control, start tracking it and then have the two machines communicating with the same repository.
Side note : it is quite common to develop on a machine and build on an other, you should be able to get a simple and efficient work environment quite easily.
I hope I got you question right. If not, please provide more specific info like your project's tree, the reason why you cannot test on your development machine, why is this specific file not under version control and anything else relevant.
I get this error in realtion to my [username].mode1v3 package file:
Error: 155015 (A conflict in the
working copy obstructs the current
operation) Description: Commit failed
(details follow):
I can do a compare from the SCM results menu on this file. Doing so reveals 102 conflicts (differences) between my local copy and the latest version in the repository. Problem is I don't understand what this file relates to or how to fix it. Differences occur in the file under keys like
PBXSmartGroupTreeModuleColumnWidthsKey
which I have no idea about.
I am the only one working on this project. How is it possible to resolve a conflict such as this?
Many thanks.
Sounds like you're probably working on two computers?
Any conflicts that happen in that file can safely be ignored - just tell your SCM to accept your local version. It's one of the files Xcode uses to keep track of your project state within the IDE.
I'd recommend taking it out of source control and telling your SCM system to ignore it.
This file contains your personal Xcode settings (like window positions and so on). It should not be under version control at all.