[SOLVED] Building Firefox And Applying A Patch

Pinonoir · 03-27-2015, 03:30 PM

I'm wanting to find a way build, and also apply, a*.patch file to firefox in a simple way (from CLI using traditional unix and CLI based tools preferably). Looking on google gets a myriad of results that don't seem to help at all.

I'd appreciate any and help as I'm terrible with understanding source code as it is.
Thanks a bunch.

Keith Hedger · 03-27-2015, 05:41 PM

have a look at the beyond linux from scratch book ( google it ) it has full instructions to build firefox, beware though you will need at least 6g ram/swap and it will take a couple of hours to compile/link depending on your system

Pinonoir · 03-27-2015, 08:57 PM

I looked at the book and I didn't see any info regarding patching it.

somyasmith001 · 03-27-2015, 11:32 PM

sorry buddy but i am not knowing more about it but i suggest one thing that sometimes you need to restarts your device and it the problem will solve automatically but that will done often times not every-time.

Keith Hedger · 03-28-2015, 07:01 AM

just read the man page for patch.
what patch are you trying to apply anyway?

Pinonoir · 03-28-2015, 10:43 AM

The patch for firefox from opensuse and KDE found here https://build.opensuse.org/package/v...patch?expand=1

Keith Hedger · 03-28-2015, 11:23 AM

Exract the firefox source tarball, save the patch to the same folder that you are extracting the source in which should give you somthing like lis

Code:

keithhedger@LFSCerebro:/media/SkyNet/LFSSourceArchives-7.7/DESKTOP/firefox-36.0.1.source-> ls
firefox-kde.patch  mozilla-release

cd into the mozilla-release folder and run

Code:

patch -Np1 -i ../firefox-kde.patch

if all is well you should see this

Code:

patching file browser/base/content/browser-kde.xul
patching file browser/base/content/browser.xul
patching file browser/base/jar.mn
patching file browser/components/build/nsModule.cpp
patching file browser/components/preferences/main.js
patching file browser/components/shell/moz.build
patching file browser/components/shell/nsKDEShellService.cpp
patching file browser/components/shell/nsKDEShellService.h
patching file browser/components/shell/nsUnixShellService.cpp
patching file browser/components/shell/nsUnixShellService.h
patching file browser/installer/package-manifest.in

Then configure and build in the normal way.

Pinonoir · 03-28-2015, 01:02 PM

Ran into this.

Code:

The next patch would create the file 
browser/base/content/browser-kde.xul, which already exists!  Skipping 
patch. 1 out of 1 hunk ignored patching file 
browser/base/content/browser.xul Hunk #1 FAILED at 174. Hunk #2 FAILED 
at 1198. 2 out of 2 hunks FAILED -- saving rejects to file 
browser/base/content/browser.xul.rej patching file browser/base/jar.mn 
Reversed (or previously applied) patch detected!  Skipping patch. 1 out 
of 1 hunk ignored -- saving rejects to file browser/base/jar.mn.rej 
patching file browser/components/build/nsModule.cpp Hunk #1 FAILED at 8. 
Hunk #2 FAILED at 31. Hunk #3 FAILED at 60. 3 out of 3 hunks FAILED -- 
saving rejects to file browser/components/build/nsModule.cpp.rej 
patching file browser/components/preferences/main.js Hunk #1 FAILED at 
12. Hunk #2 FAILED at 572. 2 out of 2 hunks FAILED -- saving rejects to 
file browser/components/preferences/main.js.rej patching file 
browser/components/shell/moz.build Hunk #1 FAILED at 30. 1 out of 1 hunk 
FAILED -- saving rejects to file browser/components/shell/moz.build.rej 
The next patch would create the file 
browser/components/shell/nsKDEShellService.cpp, which already exists!  
Skipping patch. 1 out of 1 hunk ignored The next patch would create the 
file browser/components/shell/nsKDEShellService.h, which already exists!  
Skipping patch. 1 out of 1 hunk ignored The next patch would create the 
file browser/components/shell/nsUnixShellService.cpp, which already 
exists!  Skipping patch. 1 out of 1 hunk ignored The next patch would 
create the file browser/components/shell/nsUnixShellService.h, which 
already exists!  Skipping patch. 1 out of 1 hunk ignored patching file 
browser/installer/package-manifest.in Reversed (or previously applied) 
patch detected!  Skipping patch. 1 out of 1 hunk ignored -- saving 
rejects to file browser/installer/package-manifest.in.rej

Keith Hedger · 03-28-2015, 01:10 PM

this patch is not suitable for the firefox version you are trying to compile it patches fine on version 36.0.1, what version of firefox are you trying to patch? do you have the src archive because if you are trying to patch an archive with the firefox binary's it wont work.

Pinonoir · 03-28-2015, 01:26 PM

Quote:

Originally Posted by Keith Hedger

this patch is not suitable for the firefox version you are trying to compile it patches fine on version 36.0.1, what version of firefox are you trying to patch? do you have the src archive because if you are trying to patch an archive with the firefox binary's it wont work.

Whoops, messed up the first time as I had the wrong source.
I'm using firefox-36.0.1.source.tar.bz2 now which I untared and tried to patch; gave the same error.

Keith Hedger · 03-28-2015, 01:42 PM

where did you get the source from was it from mozilla? if it was from your distros repos it may already be patched.

Pinonoir · 03-28-2015, 01:57 PM

Quote:

Originally Posted by Keith Hedger

where did you get the source from was it from mozilla? if it was from your distros repos it may already be patched.

I tried from mozila.
ftp://ftp.mozilla.org/pub/mozilla.or...36.0.1/source/
Nothing has changed.

Keith Hedger · 03-28-2015, 02:12 PM

The only other thing is that mozilla has made minor updates to the source without bumping the version number which is not unknown or you have some how corrupted the patch try downloading it with wget like so

Code:

wget https://build.opensuse.org/source/mozilla:Factory/MozillaFirefox/firefox-kde.patch

Make sure you remove the mozilla-release folder, re extract the source and try again, make sure you run te patch before making any changes to the contents of the mozilla-release folder.

Pinonoir · 03-28-2015, 02:56 PM

It worked!
Do I still make a mozconfig and configure the options? Or should I just do a standard configure without it?

Keith Hedger · 03-28-2015, 03:08 PM

A mozconfig file is recommended because of the large number of options though I have on occasion built firefox using ./configure --prefix=/usr ... , but I would stick to using the config file method.
Don't forget to mark the thread as solved, and give my ego a rub and click the "Did you find this post helpful? Yes" link.