On Wed, Jan 30, 2019 at 10:57:00PM +0100, Vaclav Masin via blfs-support wrote:
> > 
> > That is certainly my impression, but I've been wrong before on
> > errors that looks similar to that.  At
> > https://developer.mozilla.org/en-US/docs/Mozilla/Using_CXX_in_Mozilla_code
> > they claim gcc-6.1 is the minimum required - but that page of
> > documentation might just be out of date.
> > 
> > I assume you do not have clang (along with clang++, llvm-ar,
> > llvm-nm, llvm-ranlib) available ?  Old versions are probably good
> > enough (gentoo specify llvm >= 4.0, but again documentation might be
> > out of date).
> > 
> > Failing that, in the short term I guess that you can probably still
> > build 60.5.0esr, albeit that the mozconfig will differ.
> > 
> > ĸen
> > 
> 
> I do have all of that clang* and llvm* stuff available, current BLFS version, 
> too:
> 
> $ clang --version
> clang version 7.0.1 (tags/RELEASE_701/final)
> Target: x86_64-unknown-linux-gnu
> Thread model: posix
> InstalledDir: /usr/bin
> 
> $ llvm-ar --version
> LLVM (http://llvm.org/):
>   LLVM version 7.0.1
>   Optimized build.
>   Default target: x86_64-unknown-linux-gnu
>   Host CPU: penryn
> 
> I thought the rustc and LLVM packages are necessary to build newer Firefox 
> versions so I've 
> always tried to keep them current. Could them being available like this help 
> my current 
> situation somehow?
> 
> Thanks.

If you look at current BLFS, we should be exporting CC=clang,
CXX=clang++, etc.  With that set of exports it should build using
clang and clang++ for the non-rust parts.

In the previous release, using clang made it smaller.  But the tests
for that were mostly during the beta, I did not attempt to roll it
out to older systems until after the release, so I did not try
building with older gcc versions.

ĸen
-- 
thread 'main' panicked at 'giraffe',
/tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to