On Sun, Mar 29, 2020 at 09:06:10PM +0100, Ken Moffat via blfs-dev wrote:
> On Sun, Mar 29, 2020 at 01:55:27PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 3/29/20 12:56 PM, Ken Moffat via blfs-dev wrote:
> > > On Sun, Mar 29, 2020 at 10:30:39AM -0500, Bruce Dubbs via blfs-dev wrote:
> > > > On 3/29/20 10:13 AM, Ken Moffat via blfs-dev wrote:
> > > > Did you log the install? Is it doing a complete rebuild? What happens
> > > > if
> > > > we just did
> > > >
> > > > DESTDIR=${PWD}/install python3 ./x.py install
> > > >
> > > > without the build. I know that the tests would not be run until after
> > > > the
> > > > install. Also, do we need --exclude src/tools/miri on the install
> > > > line?
> > > >
> > > > -- Bruce
> > >
> > > Hi Bruce,
> > >
> > > I did log it, but after discovering it had been swapping, finally
> > > grokking Pierre's comment re the grep and then killing everything
> > > unnecessary on that box it is now rerunning the build.
> > >
> > > Interesting ideas. I'll try to test all of them.
> >
> > I do not think the above works. I tried and the build failed.
> >
> > On the other hand, I used the current instructions for 1.42.0 and it took
> > about 21 minutes at -j10 for the build and only 2m39s for the install
> > portion.
> >
> > -- Bruce
>
> My repeat build was already running, but when I edited my notes on
> what I was doing I found that from time to time the desktop stalled
> for a few seconds - top showed 4 rustc processes each running at 103
> to 107%.
>
> When the build finished I copied the tree to -built, then went back
> in and installed. Nice and quick, although I think it was about 50%
> longer than your (I'm back on my laptop, while the build machine
> tries a straight ./install with all variables set including
> DESTDIR).
>
> The alternative install with --exclude src/tools/miri took an extra
> 0.38 SBU, but that was probably the normal "rust is a PITA for
> varying timings, because it may build in a random order." I noticed
> that the sizes in MB for each of those two builds, and the original,
> were the same for the build tree, install copied to /tmp, and
> ~/.cargo : but the total in MB varied by 2MB (first build biggest,
> last build smallest).
>
> I'll go back later to see if my "only run the install" also failed.
>
For me, just running ./x.py install (with RUSTFLAGS, LIBSSH...,
DESTDIR all exported) worked. Space was in the middle of the
previous three builds, but the time was the slowest of the builds
where it did not swap (unrounded 32.99 SBU, 33.37 SBU, 34.33 SBU).
I suspect that is yet again "normal variation when compiling with
rust." If we wanted, we could do it and then run the tests before
copying from the DESTDIR, though I cannot see any benefit. But a
useful experiment. Thanks.
Now to put the offline cores back online, and look at some other
stuff.
ĸen
--
When alle is ſayed and all is done, ye must chooſe your faces wisely,
for soon enouff ye will be playing with fyre."
The Nice and Accurate Prophecies of Agnes Nutter, Prophecy 5004
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
