On Feb 28, 2011, at 19:35 PM, Andrew Watts <[email protected]> wrote:
> Bumping the version back to version 5.04 (r75061) fixes this problem.
Given that file @5.05 is the current version, how does one "roll back" the file
port to version @5.04 in Mac Ports?
Can you do something like, say,
sudo port uninstall file
sudo port install --version @5.04 file
or not? (I'm hesitant to try it because "mediatomb" depends on "file".)
Since file 5.05 cannot recognize single-architecture executables either, I'd
very much like to roll it back until the current version functions correctly.
--
[19:53] nightowl:~ % /usr/bin/file /opt/local/bin/pkg-config ; echo '' ;
/opt/local/bin/file /opt/local/bin/pkg-config
/opt/local/bin/pkg-config: Mach-O executable i386
/opt/local/bin/pkg-config: data
[19:53] nightowl:~ % /usr/bin/file /usr/bin/file ; echo '' ;
/opt/local/bin/file /usr/bin/file
/usr/bin/file: Mach-O universal binary with 2 architectures
/usr/bin/file (for architecture x86_64): Mach-O 64-bit executable x86_64
/usr/bin/file (for architecture i386): Mach-O executable i386
/usr/bin/file: Mach-O fat file with 2 architectures
(It would also be nice if file 5.05 identified *which* 2 architectures were in
the fat files it still recognizes, like the Mac OS X "file" does.)
- Greg
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
