[Bug 227130] lang/rust: Update to 1.25
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227130 --- Comment #24 from Jean-Sébastien Pédron --- The aarch64 bootstraps were uploaded to `LOCAL/dumbbell`. bdrewery, could you please update the `distinfo` in your patch and possibly commit it? -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: www/firefox-esr build dependencies
"14th.presid...@gmail.com" <14th.presid...@gmail.com> writes: > Greetings, > > I just got bit by having SECURE_DELETE turned off in > databases/sqlite3, in that firefox failed the configure stage > but only after a couple of hours of building other stuff had > transpired. I assume this applies equally to the other > firefox ports, and probably seamonkey, as well. SECURE_DELETE is documented by 20120726 in /usr/ports/UPDATING. Properly fixing would require the ports framework to support a way to specify dependencies with options, similar to flavors. > I know that other ports have checks to make sure that > certain flags are turned on in dependencies before > trying to build, but I'm not sure how much of a headache > that would be. Those hacks tend to bitrot or grow out of sync over time e.g., https://svnweb.freebsd.org/changeset/ports/402343 There're not enough gecko@ peers to maintain existing hacks, so I'm not enthused to add more for marginal benefit. After binary packages became stable regular users shouldn't be using ports and power users should be experienced enough to route around quirks. If you feel strongly power up more and submit a patch. ;) ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
www/firefox-esr build dependencies
Greetings, I just got bit by having SECURE_DELETE turned off in databases/sqlite3, in that firefox failed the configure stage but only after a couple of hours of building other stuff had transpired. I assume this applies equally to the other firefox ports, and probably seamonkey, as well. I know that other ports have checks to make sure that certain flags are turned on in dependencies before trying to build, but I'm not sure how much of a headache that would be. Anyway, thank you for all your hard work, and cheers! ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
www/firefox-esr build dependencies
___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 226476] www/firefox: update to 60.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226476 --- Comment #29 from D. Ebdrup --- (In reply to Jan Beich from comment #27) >OpenBSD But I'm using FreeBSD, so I don't see how that's relevant. Still, I've upped kern.ipc.shmall to 262k instead of the 131k it was at - so whatever limits there may be shouldn't be a problem. >Logging I'll try messing around with it anyhow - with pkg, it's remarkably easy to switch between the working and non-working version of Firefox, so I should be able to tell if it reports anything different, and possibly find out what that means. >Disable DTRACE option The thing is, I only get the dtrace errors if the DEBUG option is turned on. The first package that I built, and that I'm using to test with, is built with default options and didn't get any errors. Long of the short of it is - Don't feel you have to delay the port on my account, though - if I need webrtc, I'll install the working version temporarily, no reason to have that delay a new version of the port going out. If I find a real bug in FreeBSDs port, or better yet a fix, I'll file a separate report. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
