Firefox port fails make install


Since updating to U8 I’ve been unable to ‘make install’ the port of the (2) subsequent version changes of Firefox. Updated ports of other applications ‘make install’ sucessfully. I only port application versions that fail pkg audit and are not in App Cafe yet…
Seeming the error centres around:
/usr/include/c++/v1/type_traits:740:56: error: _Float16 is not supported on this target
template <> struct __libcpp_is_floating_point<_Float16> : public true_type {};
Does this imply a dependency for the make [from a pbi install (ie app cafe) perhaps] isn’t compatible with my system? Gmake?
Anyone else seeing this?
MAKE_JOBS_UNSAFE=yes still fails
Thanks, Steve

System Specs:
Boot Method: BIOS
Intel® Core™ i3-6100 CPU @ 3.70GHz
Physical CPUs: 4
Physical Memory: 7.85 GB

gmake[5]: *** [/usr/ports/www/firefox/work/firefox-66.0.3/config/ force-cargo-library-build] Error 101
gmake[5]: Leaving directory ‘/usr/ports/www/firefox/work/.build/toolkit/library/rust’
gmake[4]: *** [/usr/ports/www/firefox/work/firefox-66.0.3/config/ toolkit/library/rust/target] Error 2
gmake[4]: Leaving directory ‘/usr/ports/www/firefox/work/.build’
gmake[3]: *** [/usr/ports/www/firefox/work/firefox-66.0.3/config/ compile] Error 2
gmake[3]: Leaving directory ‘/usr/ports/www/firefox/work/.build’
gmake[2]: *** [/usr/ports/www/firefox/work/firefox-66.0.3/config/ all] Error 2
gmake[2]: Leaving directory ‘/usr/ports/www/firefox/work/.build’



Why did you need to use the ports of firefox, It is ore-built on Trident

how did you get the ports installed?

Did you read the info on the project-trident.web site?



Thanks Rod,
Firefox ‘Trident release’ is currently 66.0_1,1.
Ports (git pulls of clone) are here:

and is currently 66.0_3.1,1
mozilla – multiple vulnerabilities for 66.0_1,1 are
CVE: CVE-2019-9809
CVE: CVE-2019-9808
CVE: CVE-2019-9807
CVE: CVE-2019-9806
CVE: CVE-2019-9805
CVE: CVE-2019-9804
CVE: CVE-2019-9803
CVE: CVE-2019-9802
CVE: CVE-2019-9801
CVE: CVE-2019-9799
CVE: CVE-2019-9798
CVE: CVE-2019-9797
CVE: CVE-2019-9796
CVE: CVE-2019-9795
CVE: CVE-2019-9794
CVE: CVE-2019-9793
CVE: CVE-2019-9792
CVE: CVE-2019-9791
CVE: CVE-2019-9790
CVE: CVE-2019-9789
CVE: CVE-2019-9788
My understanfing is that as Firefox is not a part of the U8 release (Falkon is) it is then classed an external package - isn’t it? So, to get the latest non-vulnerable release requires using the port (if updates aren’t made available with the Trident systems update manager). App Cafe is currently two version changes behind.
Just trying to keep my favourite browser fully up to date.
Never had this make install issue before [<U8] for Firefox.



Firefox is available in U8, pkg install or app cafe to bring it in.
When you install a package that is not in the base install, it will get updated when you next update the system (as long as it is updated and continues to build).



Updates are expected every two weeks or so. If you can’t wait… :male_detective:



Thanks mer, just to be clear…
Firefox 66.0_1,1 IS in App Cafe and already installed on my system.
It has multiple vulnerabilities I wish to get past.
Firefox 66.0_3.1,1 is NOT in App Cafe but it IS in the Trident git repository:
= [up to date] trueos-master -> origin/trueos-master
= [up to date] freebsd/master -> origin/freebsd/master
= [up to date] freenas/12-stable -> origin/freenas/12-stable
= [up to date] ixlab -> origin/ixlab
= [up to date] quick-fixes -> origin/quick-fixes
= [up to date] syslog-ng-full -> origin/syslog-ng-full
= [up to date] trueos-stable-18.12 -> origin/trueos-stable-18.12



@nevets, thanks I understood all of that. It was a long winded way of saying “I think U9 should be coming out soon and if it were me I’d wait instead of building it myself”. The U9 builds look green, so they likely have a few days of QA cycle before release (I’d guess there will be a release this week).

Now as to the error, whatever it’s trying to build the c++ includes don’t seem to like it. I don’t know what compiler it is/should be using (i’d guess clang instead of gcc).
You could trying doing “git pull” in the firefox directory just in case you did your original clone inbetween something, then I’d look at the Makefile and any configuration to see. Don’t forget make clean in the directory before trying a rebuild.



This is actually a good time to state that “just because something has a vulnerability, doesn’t mean you need to panic”
In general I prefer to keep on top of security updates, but you need to understand them to decide how urgent it is for you.
example: CVE-2019-9801. If you go see what that is on the mozilla website, you find out “…Windows programs that are not URL handlers…” Well FreeBSD/Trident isn’t Windows :slight_smile: so this one is really a non issue for us. Anything else referring to “JIT compiler” means “turn off JavaScript”.

So @nevets, I agree with keeping on top, but you can mitigate a lot of browser exploits by being smart and then waiting for the package to get built.

1 Like


Thanks mer for the words of wisdom. I appreciate the assist. I’ll try for some patience.