fixes #10: Removing warlock for the core [1]

Warlock has been removed from the Makefiles. Warlock files have been removed. Almost all warlock code is gone.

There is still cstyle.pl and some comments that still mention the warlock (maybe some NOTE directives that use it indirectly too).

Feel free to decline this pull request until everything is done.
Applied a second commit with the suggested changes.
As for the exception files, if you meant the
exception_list.{closed,common,open}, they have been updated already from
the first commit to not include warlock related files.

Will do the two full nightly builds, later today and let you know.

On Wed, Dec 3, 2014 at 11:29 AM, gdamore <notifications@github.com> wrote:

> In usr/src/uts/common/sys/scsi/targets/ses.h:
>
> > @@ -165,7 +163,6 @@ struct ses_softc {
> >  	uchar_t		ses_srqsbuf[MAX_SENSE_LENGTH];
> >  };
> >
> > -#ifndef	__lint				/* no warlock for X86 */
>
> Oh maybe I'm confusing elfcmp with the build noise. What I want to do is
> make sure that the binaries are unchanged. I'm AFK at present but can check
> later today.
> … <#14a113336e750ebf_>
> Sent from my iPhone
>  On Dec 3, 2014, at 9:26 AM, Serapheim Dimitropoulos <
> notifications@github.com> wrote: In
> usr/src/uts/common/sys/scsi/targets/ses.h: > @@ -165,7 +163,6 @@ struct
> ses_softc { > uchar_t ses_srqsbuf[MAX_SENSE_LENGTH]; > }; > > -#ifndef
> __lint /* no warlock for X86 */ OK will get to work and change the thinks
> that you pointed out. Will also update check/update the exception files.
> About the binary verification, isn't wsdiff ran from one full build to
> another? I mean that doing a full build of illumos core, applying my patch,
> doing a full build again and check if there are any changes in the mail_msg
> should be enough, right? … — Reply to this email directly or view it on
> GitHub.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gdamore/illumos-core/pull/131/files#r21248363>.
>