|
146u2 patch problem (now solved, nothing to see here)
#292189 - 07/19/12 01:10 PM
|
|
|
Hi guys,
I threw a few search terms into the search and came up blank.
I apologise in advance if this has already been covered.
I have been using patch -p0 -E <0xxxux.diff forever.
With 146u2 I get this complaint:
J:\applications\mingw64-w64\mamesrc>patch -p0 -E <0146u2.diff
patching file src/mame/mame.lst
missing header for unified diff at line 28 of patch
can't find file to patch at input line 28
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|,6 @@
| pengob // bootleg
| penta // bootleg
| jrpacmbl // bootleg on Pengo HW
|-
| jrpacman // (c) 1983 Midway
|
| // Epos games
--------------------------
File to patch:
Could someone shed some light please?
Cheers, doc
Edited by Doc (07/20/12 12:04 AM)
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: 146u2 patch problem
[Re: Doc]
#292191 - 07/19/12 01:49 PM
|
|
|
> Hi guys,
> I threw a few search terms into the search and came up blank.
> I apologise in advance if this has already been covered.
> I have been using patch -p0 -E <0xxxux.diff forever.
> With 146u2 I get this complaint:
>
> J:\applications\mingw64-w64\mamesrc>patch -p0 -E <0146u2.diff
> patching file src/mame/mame.lst
> missing header for unified diff at line 28 of patch
> can't find file to patch at input line 28
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |,6 @@
> | pengob // bootleg
> | penta // bootleg
> | jrpacmbl // bootleg on Pengo HW
> |-
> | jrpacman // (c) 1983 Midway
> |
> | // Epos games
> --------------------------
> File to patch:
>
>
> Could someone shed some light please?
> Cheers, doc
There has been no reported of issues with .DIFF recently that I am aware of. Sometimes, it easiest to simply create source from base (0.146) and then add the .DIFF patches one at a time again. In many instances this 'starting fresh' fixes problems people have. Also, reacquire the .DIFF patches from mamedev.org, in case there was a release in which a problemed patch was replaced without your knowledge.
|
|
|
|
Re: 146u2 patch problem
[Re: Tafoid]
#292198 - 07/19/12 03:59 PM
|
|
|
Thanks Tafoid,
I rebooted, did a virgin install, same complaint.
It has been literally years, but I thought that -p0 -E was compile as split merged sets.
If I am mistaken or misguided, I would love some help.
Craig
|
|
|
| Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: 146u2 patch problem
[Re: Doc]
#292209 - 07/19/12 05:50 PM
|
|
|
> Thanks Tafoid,
> I rebooted, did a virgin install, same complaint.
> It has been literally years, but I thought that -p0 -E was compile as split merged
> sets.
> If I am mistaken or misguided, I would love some help.
> Craig
Nope. I use the same patch routine and have for years. The only thing I can think of, like I mentioned before, is if you are right on top of the releases you might have gotten a .DIFF archive that was quietly fixed shortly after a release announcement. It happens sometimes.
Go to http://mamedev.org/updates.html and re-download the .DIFF files. Compare dates inside the .zip and see if you might have an earlier (superseded) .DIFF.
Other than that - I'm not sure what else to suggest.
|
|
|
|
Re: 146u2 patch problem
[Re: Tafoid]
#292234 - 07/20/12 12:04 AM
|
|
|
Thanks again Tafoid,
In more than 10 years of compiling MAME, I have never come across this issue. You were 100% correct, I grabbed the diff file again from mamedev.org, problem solved.
Thanks for the advice and the solution!
doc
|
|
|
Previous 
Index 
Next 
Threaded 
146u2 patch problem (now solved, nothing to see here)
Reply
[Re: 