Here's an odd one... I did "hg update -r m5_2.0_beta3" and tried to
build, and it failed because ext/libelf is missing.  It looks like
this is a side effect of Nate replacing GNU libelf with the FreeBSD
version.  Is the GNU libelf completely missing now?

Steve

On Wed, Jun 4, 2008 at 9:36 AM, nathan binkert <[EMAIL PROTECTED]> wrote:
> I put up a new repository and I think we're basically done.
>
> I'd like some help to verify that everything is done before we switch
> to it and make it publicly available.
>
> Basically, I want people to check out old revisions and diff them
> between the two trees.
>
> Things to verify.
> 1) only a few files should have been removed:
> skip_files = set([ 'src/arch/x86/template.hh',
>                   'util/setup-web99', 'util/setup-spec',
>                   'util/setup-specweb', 'util/greprevs',
>                   'util/chgcopyright'])
>
> 2) Only whitespace and comment blocks (i.e. copyright blocks) should
> change.  I fixed whitespace issues in the tree (leading tabs and
> trailing spaces), so there are differences there.  The -b option in
> diff is your firend.
>
> 3) For MIPS, UM, HP, there are only two copyrights.  Most should be
> the new M5 copyright, and stuff in x86 should have the HP no-sale
> copyright.
>
> 4) Almost all files should have a copyright on them.  Everything in
> the tip should, but a few things that didn't have a copyright in past
> revisions but did have a copyright added in the future won't have
> those copyrights in the past.  This is OK.
>
> 5) Since only comment blocks should have changed, everything should
> compile and run as it normally would.
>
> 6) I have a script that I wrote that tries to automatically remove as
> many differences as possible to reduce the diff output, but I'd prefer
> if people did it their own way so that we're not all looking at the
> same thing.  If you're unwilling to put effort in yourself, I can send
> you my scripts.
>
> Please, let's put this to bed.
>
>  Nate
>
>  Nate
> _______________________________________________
> m5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/m5-dev
>
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to