Rockbox Development > Starting Development and Compiling
Compressed file ends unexpectedly, While compiling
nls:
that i probably a git patch, they usually come with these paths beginning with a and b, use -p1 for the patch command to strip these.
bluebrother:
--- Quote from: psgarcha92 on May 03, 2011, 02:55:19 AM ---prabhdeepsingh@ubuntu:~/rockbox$ sudo patch --binary -p0 < enable.diff
--- End quote ---
1. don't use sudo for applying patches. sudo is only needed for operations that require super user priviledges. Installing packages via the systems package manager needs that, building Rockbox at no point does.
2. You usually don't need --binary when applying patched. It doesn't hurt though.
--- Quote ---patching file b/firmware/export/config/sansaclipplus.h
Hunk #1 FAILED at 179.
1 out of 1 hunk FAILED -- saving rejects to file b/firmware/export/config/sansaclipplus.h.rej
patching file b/firmware/export/config/sansafuzev2.h
--- End quote ---
The patch doesn't apply anymore. This can happen when the original file has been changed in the meanwhile and the changes made in that file conflict with the changes the patch would do. You need to apply the changes by hand.
psgarcha92:
guys, are these patches to be applied before compiling?
i mean, i go to terminal, type in cd rockbox/tools
then chmod +x rockboxdev.sh, and then i run ./rockboxdev.sh
select e, press enter and it starts to do all the downloading and compiling, i guess.
the patch can't be applied after this process right?
but in my case why are the patches not being installed/written?
saratoga:
--- Quote from: psgarcha92 on May 03, 2011, 05:30:00 PM ---guys, are these patches to be applied before compiling?
i mean, i go to terminal, type in cd rockbox/tools
then chmod +x rockboxdev.sh, and then i run ./rockboxdev.sh
select e, press enter and it starts to do all the downloading and compiling, i guess.
the patch can't be applied after this process right?
--- End quote ---
I think you're confusing a couple things here. rockboxdev.sh compiles gcc. If you want to patch gcc, then yes you'd have to patch the gcc source code before compiling it, but then you can't compile a patched gcc with rockboxdev.sh anyway (at least not without editing it quite a lot).
If you want to patch rockbox (which is what it sounds like you're doing), then you need to apply the patch before compiling rockbox. It doesn't matter if you apply the patch before building gcc, but usually people install gcc first since you can't actually do much of anything without it.
--- Quote from: psgarcha92 on May 03, 2011, 05:30:00 PM ---but in my case why are the patches not being installed/written?
--- End quote ---
As bluebrother said, your patch is no good. You'll have to manually apply its changes.
Edit: Have you seen this? http://www.rockbox.org/wiki/DevelopmentGuide
Particularly the parts about settings up the dev tools and how to use patch would probably help you understand what you're doing.
torne:
Er, as nls said, the patch is a git-style patch which needs to be applied with -p1
It may *also* be out of date and not apply, but -p0 will definately not work.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version