after running a build of chrome for 24 hours I had to stop the slackbuild
this computer is pretty much useless during a build (run level 1 )
so is there a way to save that 24hours of work the computer did ?
if this helps it was still compiling

I suggest using Alien Bob's Chromium package: https://alien.slackbook.org/blog/chr...nd-32bit-pain/

It works great.

can't get it down loaded on my wifi connection
just about any web site having to do with wifi,networking and most of github is blocked even mozilla's web site is blocked it's gotten worse lately so it looks like I'm going have to move the computer some place else and run it on an inverter to download it

You can't download from slackware.com ??? Why, are you in prison or what? Or using someone else's Internet connection?

2 members found this post helpful.

I echo the other members' suggestion of using Alien's package, however, to answer your original question...

By default, no, there is no way to resume a package. However, it can be done with some tweaking of the SlackBuild. The first big one is removing (or commenting out) the rm command that would remove the source directory. In fact, you'd probably want to comment/remove extracting the tarball as well. In most SlackBuilds on SBo, the corresponding lines would look something like:

Many times this is enough to continue the build from where it left off, but that could also depend on the build system. I noticed the build system for chromium on SBo uses ninja, and unfortunately, I'm not familiar enough with that one to know how it does on resuming compiles that have been halted.

2 members found this post helpful.

This seems relevant. https://ninja-build.org/manual.html

1 members found this post helpful.

Two more choices: use a VM that you can pause and resume, or maybe try this: https://criu.org/Main_Page

1 members found this post helpful.

Normally running make in the build directory will resume the compilation (only compile not yet compiled targets)
In case of SlackBuild, look into the script where the build directory is and do script steps by hand to create the package
Or copy SlackBuild relevant steps and variables to create the package into a new script and execute it

[edit]
Ninja? oh well... forget this post then

You could set up ccache, it will speed up additional builds of any programs you have already compiled. However I suspect it will require a very large ccache with chrome...

https://docs.slackware.com/studiowar...=ccache#ccache

"are you in prison "
not far from it I'm being gang stalked by the white slave trade
including an on going attempted homosexual rape

"using someone else's Internet connection?" YES public wifi


got it thanks Alien Bob

1 members found this post helpful.

.....

This topic took an unexpected turn...

Anyway, Eric's builds have been invaluable to me on a low-powered machine. Specifically Libreoffice, qt5 and openjdk. I installed Eric's binary for Chromium but tend to use Qupzilla instead.

Well maybe you should stop wearing such sexy shoes!
....
.....
.......


My apology for this feeble attempt at humor about the common male misconception that women who are raped 'were asking for it". I couldn't tell for certain that OP was kidding or not and took the risk that in either case a lil' levity might be welcome. I mean i could've said "Just tell them you've been abducted dozens of times by some really filthy aliens and "probed" endlessly so unless they fancy a serious interstellar STD, they need to bugger off!


OT to this thread it is my regarded opinion that even if you can find a way to skip repeating preliminary steps you really shouldn't. Given that the build stopped short because of an error it's safe to assume you made changes. The build should then be against those changes or risk failure yet again. Thorough is good. Slow is smooth. Smooth is fast.

I hope that was a strange attempt at humor, but I think this is a time where those kids on the internet would post this picture:

http://i0.kym-cdn.com/photos/images/...53/279/e31.jpg