Jivin Gavin Lambert lays it down ...
> Quoth Claude:
> > I've got an stupid question, I think: Given a uclinux release, how
> > patches are applied?
> > I always have avoided patching code by downloading the latest
> > releases, but I think I should learn how to patch them.
>
> This doesn't exactly answer your question, but probably the easiest thing to
> do is something like this:
>
> 1. Unpack a "clean" version of the release you already have.
> 2. Run a "make clean" in your current source tree (to get rid of files that
> get autogenerated).
> 3. Run a diff between the clean version and your current source tree (in
> that order) to generate a patch containing your changes to the dist.
> 4. Hand edit the patch (if necessary) to remove files/changes that shouldn't
> have been included.
> 5. Unpack the latest (full) version of the dist.
> 6. Apply your patch (use --pretend first, to verify the changes are
> compatible!) to bring your modifications into the new dist tree.
So that is how you create a patch to send in :-)
If you just want to apply patches then it is usually one of these two:
1) cd uClinux-dist; patch -p1 < patch-file
2) cd uClinux-dist; patch -p0 < patch-file
The only difference between the two is how many leading directories need
to be removed from the files names in the patch to find the correct file
in the dist. If you get "can't find which file to patch" errors applying
a patch then it's probably because you need a different number after -p,
Same approach works for kernels and so on,
Cheers,
Davidm
--
David McCullough, [EMAIL PROTECTED], Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
