On 05/23/2013 06:52 AM, Jack Mc Lauren wrote:
> Hi
> find //usr/obj/usr/src/release/dist/doc -empty -delete
> find: -delete: //usr/obj/usr/src/release/dist/doc: relative path potentially
> not
> safe
> *** [distributeworld] Error code 1
> What's wrong with this?
> Thanks in advance
Huh. Appare
Hi
I'm trying to make my own release ...
# cd /usr/src
# make buildkernel KERNCONF=MYKERN
# make -j4 buildworld
# cd release/
# make release NODOC=YES NOPORTS=YES NOSRC=YES
and that's the error while making release:
find //usr/obj/usr/src/release/dist/doc -empty -delete
find: -delete: //usr/obj
Michael Dexter <[EMAIL PROTECTED]> writes:
> Having complete control over the build of my network OS is simply
> revolutionary... but I was hoping this revolution would not be so
> bloody.
You can get *that* with one of the supported update options. "make
release" was never intended for anybody
Greetings again,
Regarding the make release mentioned earlier...
After peppering my /usr/ports/distfiles/ tree with very redundant
distfiles, i.e. the same files in /usr/ports and
/usr/ports/ghostscript and /usr/ports/ghostscript-gnu, things finally
worked. (Ending on a vn present failure but
Greetings from Latvia,
I am very, very excited about FreeBSD's "make release" ability but
like many others I have read about on the various list archives, I my
builds are hanging on trivial failures. In this case, the
eplaser-3.0.4-651.tgz file is failing its checksum, bringing the
build to a
