hi
> hwclock --htctosys
> is not working anymore
>
> -->> hwclock: settimeofday() failed: Invalid argument
>
> I have hint about the fact it could be a glibc-2.31 related problem
>
> https://forum.artixlinux.org/index.php/topic,1311.msg9179.html
>
> Could someone concur about hwclck malfunction?
> I've been trying to build mesa-19.2.0 this afternoon and I can't get it
> to build.
that should have now been fixed upstream:
https://gitlab.freedesktop.org/mesa/mesa/issues/1844
ciao
gabriele
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ:
> Looking at fedora,
> https://src.fedoraproject.org/rpms/firefox/tree/master they seem to
> manage to build some sort of 69.0 but using a "shipped" cbindgen
> (and I've no idea where/how they got that). Without system
I usually (since 66.0) build cbindgen on the fly (as one of the very
first
> for the brave: librsvg-2.45.7 works fine for me for some time now. If
> compiled with rustc-1.35. But trying to compile it with rustc-1.36
> (get it from https://fossies.org/linux/misc/rustc-1.36.0-src.tar.xz)
> fails. A pretty late linking error - missing symbol deep down in what
> seems to
Pierre Labastie via blfs-dev writes:
> When running meson, I get:
> -
> [...]
> WARNING: Project targetting '>= 0.40.1' but tried to use feature
> introduced in '0.50.0': install arg in configure_file
> Configuring atspi-2.pc using configuration
>
> atspi/meson.build:60:0: ERROR:
hello
as you might have noticed, ff-63 (dev) requires a new rust package:
cbindgen (generate C/C++ bindings for rust crates).
Build instructions can be found at arch's site:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=cbindgen
Sadly, build is at least opaque, to use a delicate
> Well this is interesting. I tried to build llvm with:
>
> CC=gcc \
> CXX=g++ \
> cmake -DCMAKE_INSTALL_PREFIX=/usr \
>-DLLVM_ENABLE_FFI=ON \
>
hi,
> There remains to understand why Bruce has an error with libffi. There is no
> mention of libffi in my rust build log.
I routinely build rustc vs system llvm
I had no problems building rustc-1.25.0 vs llvm-6.0
I saw the "undefined symbol: ffi_type_float" error quite a long ago with
1.17.0
> I agree. Since rust and cargo are only used for FF (what about
> Thunderbird or Seamonkey?) then we should only consider updating
> rust/cargo when a new FF version is released.
(sadly) rust/cargo seem to be required also for librsvg: devel version
2.41.0 requires them and I guess they will