[Bug 238482] x11-fonts/fontconfig: Firefox print pre-formatting is HORRIBLE ("bitmap font by default")

2019-06-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238482 --- Comment #25 from Ronald F. Guilmette --- Created attachment 205192 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205192=edit Installed package/port versions list Kubilay Kocak requested that I provide several bits of

rust and llvm (Re: Firefox and llvm)

2019-06-17 Thread Mikhail T.
On 17.06.19 00:10, Charlie Li wrote: Rust will not revert back to providing an option to use an external LLVM. Rust needs to use its own LLVM, which not only tracks upstream trunk, but has been forked and a few API bits added (which will not be upstreamed) for Rust use. Some of these API bits

Re: Firefox and llvm

2019-06-17 Thread Mikhail T.
On 17.06.19 00:19, Jan Beich wrote: Good luck. Make sure to test in a clean environment e.g., via poudriere Jan, this is the job of the port's maintainer... The current situation -- requiring a rebuild of LLVM twice -- is ridiculous, should never have come about, and should not remain for

[Bug 238639] devel/gn: maybe unusable by www/firefox

2019-06-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238639 --- Comment #2 from Oleh Hushchenkov --- Currently (version 75) chromium uses outdated by 4 months bundled version of gn. The old behavior was changed by this https://gn.googlesource.com/gn/+/8730b0feb6b991fa47368566501ab9ccfb453c92

[Bug 238639] devel/gn: maybe unusable by www/firefox

2019-06-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238639 --- Comment #1 from Oleh Hushchenkov --- (In reply to Jan Beich from comment #0) I will look on it. -- You are receiving this mail because: You are on the CC list for the bug. ___

Re: Firefox and llvm

2019-06-17 Thread Christoph Moench-Tegeder
## Mikhail T. (mi+t...@aldan.algebra.com): > > Good luck. Make sure to test in a clean environment e.g., via poudriere > > Jan, this is the job of the port's maintainer... The current situation > -- requiring a rebuild of LLVM twice -- is ridiculous, should never have > come about, and should