Re: [gnu.utils.bug] AC_PROG_CC_G, et al, are not very robust

[Alexandre Oliva]

On Jun 16, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:

> This is kind of wacky because the only way I could figure
> out how to get the length of a binary file was to use
> od and then measure the string length of that.

How about using the same strategy GCC bootstrap's `compare' target
uses:

        for file in *$(objext); do \
          tail +16c ./$$file > tmp-foo1; \
          tail +16c stage$$stage/$$file > tmp-foo2 \
            && (cmp tmp-foo1 tmp-foo2 > /dev/null 2>&1 || echo $$file differs >> 
.bad_compare) || true; \
        done

If the object files are identical (except for the first few bytes,
that sometimes contain timestamps), we can assume no debugging info is
generated.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me