Date: Thu, 27 Oct 2005 13:51:57 -0500 From: Will Maier <willmaier@ml1.net> To: freebsd-questions@freebsd.org Subject: Re: Which version of FreeBSD a binary was compiled for? Message-ID: <20051027185157.GV29508@localdomain> In-Reply-To: <43611E22.5030408@ywave.com> References: <cb5206420510251524r32ddd9adx7d4fdce8f82a85be@mail.gmail.com> <17247.39311.203645.265116@jerusalem.litteratus.org> <cb5206420510260818p664df038g39a1035c747ac315@mail.gmail.com> <200510262115.48144.krinklyfig@comcast.net> <cb5206420510270116k27ad6e13r5dd17dbc7323c01f@mail.gmail.com> <4360DB59.7010900@ywave.com> <20051027154408.GS29508@localdomain> <43611E22.5030408@ywave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 27, 2005 at 11:36:18AM -0700, Micah wrote:
> In other words, it's not file that broken, but /every/ executable
> on the broken machine is broken. Now why would that be? A
> compiler flag or something?
Must be -- some flag produces unique bits in the executables. I'm a
little surprised there isn't (AFAICT) anything descriptive in
file(1)'s manpage or /u/s/mi/magic that would explain the
discrepancy. Didn't see anything in quick looks through gcc(1) or
make(1), either.
Weird.
--
o--------------------------{ Will Maier }--------------------------o
| jabber:..wcmaier@jabber.ccc.de | email:..........wcmaier@ml1.net |
| \.........wcmaier@cae.wisc.edu | \..........wcmaier@cae.wisc.edu |
*------------------[ BSD Unix: Live Free or Die ]------------------*
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051027185157.GV29508>