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 a
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 long
## 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 n
"Mikhail T." writes:
> On 16.06.19 22:25, Jan Beich wrote:
>
>> clang-sys didn't support llvm80 when gecko@ switched to it. I'm not
>> sure myself why but maybe bindgen uses a subset of bindings that're
>> stable
>
> Perhaps, this is something the port's maintainers should research?
If bindgen w
Mikhail T. wrote:
> Perhaps, this is something the port's maintainers should research? Along
> with the possibility of switching lang/rust back to the llvm provided by
> the base (best) or installed by a port (second best)?
>
Rust will not revert back to providing an option to use an external
LLVM
On 16.06.19 22:25, Jan Beich wrote:
clang-sys didn't support llvm80 when gecko@ switched to it. I'm not
sure myself why but maybe bindgen uses a subset of bindings that're stable
Perhaps, this is something the port's maintainers should research? Along
with the possibility of switching lang/rus
"Mikhail T." writes:
> On 16.06.19 21:31, Jan Beich wrote:
>
>> "Mikhail T." writes:
>>
>>> Gentlemen, do you realize, building Firefox on FreeBSD today one has
>>> to wait for the entire LLVM to be recompiled -- /twice/: once because
>>> gecko, inexplicably, wants LLVM itself, and also because
On 16.06.19 21:31, Jan Beich wrote:
"Mikhail T." writes:
Gentlemen, do you realize, building Firefox on FreeBSD today one has
to wait for the entire LLVM to be recompiled -- /twice/: once because
gecko, inexplicably, wants LLVM itself, and also because rust builds
its own bundled version...
W
"Mikhail T." writes:
> Gentlemen, do you realize, building Firefox on FreeBSD today one has
> to wait for the entire LLVM to be recompiled -- /twice/: once because
> gecko, inexplicably, wants LLVM itself, and also because rust builds
> its own bundled version...
>
> What's wrong with the binarie
Gentlemen, do you realize, building Firefox on FreeBSD today one has to
wait for the entire LLVM to be recompiled -- /twice/: once because
gecko, inexplicably, wants LLVM itself, and also because rust builds its
own bundled version...
What's wrong with the binaries provided by the base OS?.. Y
10 matches
Mail list logo
