Arnt Karlsen wrote:

On Tue, 04 Jan 2005 16:20:41 -0600, Curtis wrote in message <[EMAIL PROTECTED]>:



Erik Hofman wrote:



Curtis L. Olson wrote:



Right, but in PM, Steve seems to have forgotten his original objections so I think we have a window of opportunity here if we


can > submit a reasonable looking patch.


Well, here is the original:

http://www.a1.nl/~ehofman/fgfs/download/Plib_ssgDList2-20020718.diff

I' not sure about the status of that patch right now (whether it
still applies or not).



..what am I doing wrong here? patch -p1 < never failed me even when the kernel said use " patch -p0 < ".
[EMAIL PROTECTED]:/mnt/sda2/local/src/plib/src/ssg # patch -p1 <
/mnt/sda2/local/src/Plib_ssgDList2-20020718.diff missing header for unified diff at line 3 of patch can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- /home/erik/src/CVS/fgfs/plib/src/ssg/ssgDList.cxx Mon Sep 2
|15:39:40 2002 +++ ssgDList.cxx Thu Jul 18 11:38:45 2002
--------------------------
File to patch: ssgDList.cxx
patching file ssgDList.cxx
Hunk #1 FAILED at 13.
Hunk #2 FAILED at 146.
Hunk #3 FAILED at 231.
3 out of 3 hunks FAILED -- saving rejects to file ssgDList.cxx.rej





I rarely manage to get the patch util to work [perfectly] which is one reason I like to avoid it. Inevitably, something has changed somewhere which causes an odd hunk or two to fail ... you sometimes really have to pay attention to catch it on large source trees or with large patches. You might have to go in and try to apply it by hand since it's created against a version of plib that's 2.5 years old.


Curt.

--
Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d



_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to