Date: Tue, 15 Feb 2005 08:58:53 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Kris Kennaway <kris@obsecurity.org> Cc: sparc64@FreeBSD.org Subject: Re: file(1) broken on sparc64 Message-ID: <20050215165853.GA38158@dragon.nuxi.com> In-Reply-To: <20050215152803.GA11423@xor.obsecurity.org> References: <20050122213501.GA22882@xor.obsecurity.org> <1106501671.677.1.camel@heater.rainbow-runner.nl> <20050123200201.GA81234@xor.obsecurity.org> <1108478248.30515.13.camel@heater.rainbow-runner.nl> <20050215152803.GA11423@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 15, 2005 at 07:28:04AM -0800, Kris Kennaway wrote: > On Tue, Feb 15, 2005 at 03:37:28PM +0100, Koop Mast wrote: > > >I wonder if the problem is with worlds cross-built from i386. > > >Can you try a buildworld on i386 with TARGET_ARCH=sparc64 and see if > > >it still works? > > > > I did a cross buildworld on a i386 machine, and copied the resulting > > file binary over to my sparc box. It works just like the native file > > binary. I even replaced libc.so.6 with the one from the cross build. But > > that also didn't change anything. > > The problem turns out to be a mis-compiled /usr/share/misc/magic.mgc. > If you remove it (it is only used for runtime optimization), file(1) > works fine. If you recreate it natively using file -C, it also works. A-HA! Are all the file(1) problems you've mentioned only occurring for cross-arch builds? If this is the case, we can disable building magic.mgc if TARGET_ARCH != MACHINE_ARCH. > AFAIK, the underlying reason hasn't been tracked down. To date we've never guaranteed that a cross-arch built world is usable. We only officially support cross-arch compiles for compile testing. There are other things in the tree that aren't size & endian-clean that prevent usable cross-arch release builds. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050215165853.GA38158>