It was suggested to me regarding the .hgignore fix I am working on, that
I do a full userland build to see if there are any other temporary files
that ought to be included in the file. I started the build, but there
apparently was some type of network error, and the build failed because
a tarball was unavailable. That problem was transient and the tarball is
now available.
Normally, when something goes wrong with a build within a component and
the build fails, typing "gmake publish" uses the make dependencies and
picks up where it left off. However doing this at the root of the
directory seems to start the whole thing over again from scratch, so it
is what we would call "a clobber build". I expected it to run gmake in
all of the same component directories, but I also expected them to
up-to-date and quickly move to the next. No such luck.
So, is there a target or flag that can be used to keep this from
starting over from scratch?
--
blu
Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. - Martin Golding
-----------------------------------------------------------------------|
Brian Utterback - Solaris RPE, Oracle Corporation.
Ph:603-262-3916, Em:[email protected]
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
