On 10/15/20 4:51 PM, Ken Moffat via blfs-dev wrote:
On Wed, Oct 14, 2020 at 03:59:32PM +0100, Ken Moffat via blfs-dev wrote:
On Wed, Oct 14, 2020 at 02:14:56PM +0100, Ken Moffat via blfs-dev wrote:
On Wed, Oct 14, 2020 at 04:17:50PM +0800, Xi Ruoyao via blfs-dev wrote:
On 2020-10-14 02:45 +0100, Ken Moffat via blfs-dev wrote:
On Wed, Oct 14, 2020 at 02:21:39AM +0100, Ken Moffat via blfs-dev wrote:
On Mon, Oct 12, 2020 at 09:15:30PM +0100, Ken Moffat via blfs-dev wrote:


I aim to update my builds for the packages which use rust (cbindgen,
librsvg, thunderbird to whatever is currently in the book) and to
use firefox-78.3.0, current seamonkey.

If these all build, we will be able to update rustc along with llvm.
If not, I assume we will need to revert to rustc using its shipped
llvm whenever llvm-11 goes into the book.

Have I overlooked anything ?

ĸen

Unfortunately, I _did_ overlook something - I've got several scripts
to build rustc (different versions with prefix and sysllvm or
shipped) and I accidentally built 1.46.0 on llvm-11.0.0.  That did
build, and built all of cbindgen, firefox-esr, frefox-82.0 candidate
1, librsvg, seamonkey, thunderbird.  Currently building
rustc-1.47.0, will attempt to rebuild them all in due course.

Second fault in that first attempt - I was using the shipped llvm,
so of course it built.

I can confirm that rustc-1.47.0 builds OK with system LLVM-11.0.0, and it can
build librsvg & js78 with no problem.


Thanks.

I didn't test firefox 78, though.


firefox 78 fails to build, I have not identified the error amongst
the warnings.

ĸen

https://bugzilla.mozilla.org/show_bug.cgi?id=1663715#c7

Three patches (0036-0038) in gentoo's
firefox-esr-78-patches-03.tar.xz but a hunk of the second does not
apply. I have not looked at the detail of the rejection.

Meanwhile, the (first) candidate for 78.4.0 is out.  In that the
changes in the first two patches, but not the third, have been
applied.  Will see if 78.4.0 needs that third patch.

Seamonkey builds without problems, currently attempting to build
thunderbird.

Status report (I hesitate to call it progress).

And thunderbird has similar issue(s) to firefox-esr (gentoo use
their firefox patches for thunderbird).

Meanwhile, firefox-82.0 (technically, build candidate 2) is fine.
But until thunderbird can be built, there seems little point in
even thinking about going back to current firefox.

Then I took another look at the gentoo patches.  First, their second
rust-1.47 patch (0037) was not applying because 0036 changed the
same file - I'd overlooked that, and was trying dry runs on each
before applying any of them.  Applied al three to 78.3.0, diff'd,
then realised I had not edited the last, and biggest, patch (their
0038).  Gentoo patches create extra files which they then pass to
patch, out patches get applied directly.  So I'm now working through
this one, and boy, is it long (over 30000 lines).

I'm again hopeful that the three will fix 78.3, and that the third
on its own will fix 78.4.  But not particularly close to testing
that.

On one of the updated cargo packages (proc-macro2) in the patch -
version updated from 1.0.5 to 1.0.24 - in its caro.toml I see the
following:

+targets = ["x86_64-unknown-linux-gnu"]

(no other targets mentioned near that)

A quick gurgle on github shows this is the full latest version of
it, so I am _hopeful_ that 32-bit x86 doesn't need this.  But I'll
mention it now just in case it comes back to bite someone.

Over the weekend I expect to start updating my other systems to
firefox-78.4.0 latest candidate (so far only one, build2) so I
suspect that progress on moving the book to llvm-11 with
rustc-1.47.0 and patches for 78 versions of firefox and thunderbird
will now be a week away (or more if I decide to update all my
packages and build a fresh up to date system).

Thanks for the update Ken. No big hurry. A week will be fine. It would help if you took the tickets though to reduce the possibility of conflicts.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to