Buildworld and not clean anything of a previous time

MG

MG

Use the existing completed results in /usr/obj.
What's the official way in FreeBSD 15 without using connfiguration files and only command parameters?

NO_CLEAN=1
WITHOUT_CLEAN=1
-DNOCLEAN
Other options involve changing make.conf or src.conf...
 
MG said:
What's the official way in FreeBSD 15
Click to expand...
As far as anything "official", NO_CLEAN (or any of the variations) certainly isn't recommended to do, it has a few caveats you need to be aware of. And they will bite you at some point.

A better solution, albeit not perfect, is WITH_META_MODE. It's definitely safer to do.


Though it says to put it in /etc/src-env.conf, it works just as fine from the command line; make -DWITH_META_MODE {...}
 
It won't bite me. Doing this for years. The system build compiler variables have never been consistent in my opinion.
What command do I need when I copied the entire /usr/obj to another clean system tree?
(This might sound overcomplicated but it's my phased 1-man custom release project. Need to keep track of things and not waste time on compiing the same all the time. Everything works already but I lost the not clean requirements. Is it me or 14>15?)
 
MG said:
What command do I need when I copied the entire /usr/obj to another clean system tree?
Click to expand...
Might be easier to NFS mount it? It's what I did for many years, NFS mounted /usr/src and /usr/obj, built world on a "big" machine and installed it on a "small" machine. You must make sure the time is correct on both machines though, or you'll get some weird issues.
 
I have a set of scripts that create a graphical system from only source data in a chroot tree. An entire run from scratch takes +/- 6 hours on my fast box. It currently completes without problems on different computers. The only thing about it is that it keeps SMP-building the entire world from nothing after a break and restart of my own 'build everything' system for any reason. The machines are ntp-synced.
I think I have to repeat everything manually to find the cause but that will take time. Going to try to work around it with nfs. But what's different then instead of copying everything? /usr/obj nfs-mounted from somewhere changes things?
 
MG said:
But what's different then instead of copying everything? /usr/obj nfs-mounted from somewhere changes things?
Click to expand...
Shouldn't be any difference, except you don't have to copy everything and can use it immediately. So it should save a bit of time.

Alternatively, you might want to have a look at building your own pkgbase packages. Same for building packages from ports, build once, install many. Packages are easier to distribute too.
 
All additional software comes from packages but built from source. The idea of my build system is to be able to quickly try out and change things on all levels without the need to recompi;e things that are already good. After a completed run, the target directory size is 300GB. This also includes things like the entire 40GB rust work directory. ISO's and USB images can be created from it. The actual "distribution" made of only source without 1 binary.
 
I was mistaken. The initial FreeBSD 15 binary programs to build everything with, like the fork base had bad files due to vague mech disk damage. It says write successful but can't read the written data guaranteed. The buildworld showed a file error and continued from clean state due to some invalid obj data. I tried to install everything on the same disk again but totally different random problems happen. Replaced and restored the disk and now it works like before. NO_CLEAN=yes is the correct option that I thought was ignored.
 
You must log in or register to reply here.
Back
Top