Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jun 2017 06:23:30 -0700 (PDT)
From:      "Jeffrey Bouquet" <jbtakk@iherebuywisely.com>
To:        "Benjamin Kaduk" <kaduk@mit.edu>
Cc:        "current" <current@freebsd.org>
Subject:   Re: Unsure about buildworld
Message-ID:  <E1dNfbW-0003uv-MK@rmmprod05.runbox>
In-Reply-To: <20170621031517.GE39245@kduck.kaduk.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On Tue, 20 Jun 2017 22:15:18 -0500, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Tue, Jun 20, 2017 at 01:58:58PM -0700, Jeffrey Bouquet wrote:
> > Used rsync to put /usr/src/.svn to
> >                             /usr2/src/.svn [another disk]
> > did an svn up of that          ^^
>=20
> Is there some reason (e.g., documentation) to believe that will
> result in a stable and self-consistent checkout?

  I've had enough installworlds that failed mid-install to be overly hesita=
nt and thus
sort of wish-listing for a
make -DNVIDIA-ASSURES-BUILDING-AND-INSTALLWORLD-TEST-COMPLETED=3Dyes
for resilency.   Not to mention a /usr/src/UPDATING method of cli fetching/=
wget/curl
base.txz and then " gcp -R  - / < unxz base.txz "  [ do not quote any of th=
ese ]
as a installworld-went-awry recovery-from-thumbdrive method...=20
................
tl;dr, ... wish list... newbie by infrequency of updates.
................


>=20
> > # sh
> > export CC=3D/usr/local/bin/clang39    # and the two others
>=20
> I don't think that's the correct variable(s) to set to use an
> external compiler.
>=20
I've in a .sh  or two...  usually works. Someone may correct me.=20

> > cd /usr2/src
> > MAKEOBJDIRPREFIX=3D/usr2/obj -DNO_PROFILE ... buildworld.
> >=20
> > ................................
> > which halts on some error=20
> > ranlib -d ... .a
> > exec(ranlib) no such file or directory
> > ...............................
> > Is there a more knowledgeable way of putting both src and obj on a sepe=
rate disk
> > and having the build complete AND
> > be sure where it builds, [ obj ] and the precise way to test an install=
  [ pre-rsync to the
> > production system , so to speak ]    or
> > some other *preferred* way,  extract base.txz ...   or even a clean 12.=
0-CURRENT snapshot
> > system to rsync onto the present one...=20
>=20
> Building a release and extracting the tarballs is something that
> people do, though I don't have any personal experience to recommend
> it.
>=20

  I've done the latter [ recovered by base.txz ] but never tried to build a=
 release or
anything other than bw bk ik iw ... unless incremental binaries or failing =
disks... and
since switching to SATA from EIDE many less of the latter.=20

> -Ben
>=20
> > .................................
> >   My motivation is I do not wish to attempt an svn upgrade of the deskt=
op without a
> > certainty that the installworld will complete so the nvidia-driver can =
more likely
> > than not be restored to a working state.
> > ............................
> >=20=20=20
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o=
rg"
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1dNfbW-0003uv-MK>