Solved Firefox port patching fails

S

semi-ambivalent

Anybody else here experiencing this?:
Code: 
...
===>   firefox-68.0_3,1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by firefox-68.0_3,1 for building
=> SHA256 Checksum OK for firefox-68.0.source.tar.xz.
===>  Patching for firefox-68.0_3,1
===>  Applying FreeBSD patches for firefox-68.0_3,1
No such line 323 in input file, ignoring
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to gfx/webrender_bindings/RenderThread.cpp.rej
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to gfx/webrender_bindings/src/bindings.rs.rej
=> FreeBSD patch patch-bug1511726 failed to apply cleanly.
=> Patch(es)  patch-addon-search patch-browser-app-nsBrowserApp.cpp patch-bug1288587 patch-bug1507655 applied cleanly.
*** Error code 1
...
I'm still on 63.0.3 because the various port releases just don't like the patches. Or something. Or something at my end not fixed by 'make distclean'.
thx
 
Well, well, well. It's redone nss and now compiling sqlite, much farther than earlier tries. I did a make clean and deleted files/* then re-ran svn update and it said it restored files into files/. I don't understand why earlier make cleans didn't actually clean out old cruft in the port's directory but appears just to check that the currently needed patches are put there while ignoring the presence of no-longer-needed patches, which then borks the patching. There's lots of ports I've compiled that have a healthy list of patches and subsequent compiles of later releases very near to never have this problem.

End-of-rant. Thank you.
 
It never ends. :)
The compile of the latest firefox eventually compiles the latest rust (1.36) and then rust-cbindgen, which dies with 'error 11'. I have a working firefox so I'm just going to have some ice cream now and forget security for a while. lol
 
Just some closure for this thread. After a good bit of web searching I stumbled across a post from someone with a very similar problem. The user was running ssl from ports and this was evidently causing the problem with rust/rust-cbindgen. Switching to ssl in base solved problem for user and I both although the fix touched icu and required quite a lot of re-compling (icu, llvm8, ...)
 
You must log in or register to reply here.
Back
Top