Date: Tue, 12 Oct 2004 17:41:58 +0200 From: Max Laier <max@love2party.net> To: freebsd-hackers@freebsd.org Cc: Jerry <cuoching@yahoo.com.tw> Subject: Re: Why present different size and md5 hash between the compiled code and FreeBSD's build-in binary ? Message-ID: <200410121742.06608.max@love2party.net> In-Reply-To: <416BBBCD.9050704@gmx.net> References: <20041012090959.69545.qmail@web17202.mail.tpe.yahoo.com> <416BBBCD.9050704@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3419989.qjQLSyGZFu Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 12 October 2004 13:11, Andreas Kohn wrote: > Jerry wrote: > > --- Andreas Kohn <andreas.kohn@gmx.net> wrote=A1G > > > >>Hi, > >> > >>you might be using different optimization flags than > >>the release > >>building cluster. > >>Also make sure that you have really the correct > >>sources, and not a newer > >>version from CVS. > > > >Hi~ Andreas, > > > >I just used make command with default Makefile to > >build the binary,without change any gcc flag or > >option. > >And never go through the CVS to get newer source, by > >the way, my test platfrom is Release-5.2 on x86, Have > >you ever met this kind of situation? Whether > >compile "binary command" or "kernel code" ? > > > >Best Regards. > >Jerry > > Hi, > > if your source files are *exactly* the same versions used as on the > building cluster, and you have *exactly* the same compilation options, > it would still be possible to have different binaries. For example if > the files included some reference to the current time, either in some > flags in the generated .o, .a, .so, or perhaps in the source code of > auto-generated headers. Some paths referenced could also be different on > your system than on the build cluster. > > In short: don't worry too much. It is normal. If you care to know what changed exactly, you might find objdump(1) helpful= =2E=20 You must have some experience with reading assembler, though. $ objdump -d bin.orig > dump.orig $ objdump -d bin | diff -u dump.orig - Also ident(1) is sometimes helpful to determine if you are *really* using t= he=20 same source files. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3419989.qjQLSyGZFu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBa/tOXyyEoT62BG0RAhq5AJ4+Msy4VfgzH7BkRR37QxqZHYmeLACfVG9V /ET/i4xAt5dgsNCzqCGlzho= =KDZD -----END PGP SIGNATURE----- --nextPart3419989.qjQLSyGZFu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410121742.06608.max>