jeff@dsndata.uucp (Jeff Minnig) (02/11/91)
In article <63300024@hpl-opus.hpl.hp.com> jewett@hpl-opus.hpl.hp.com (Bob Jewett) writes: > From: jewett@hpl-opus.hpl.hp.com (Bob Jewett) > Newsgroups: comp.sys.hp > Date: 5 Feb 91 20:08:41 GMT > References: <13092@sunquest.UUCP> > Organization: HP Labs, High Speed Electronics Dept., Palo Alto, CA > Lines: 14 > > > The above statement, that all 200, 300, and 400 binaries are > > identical, is corroborated by an invocation of "file /bin/*", which > > describes all the executables as written for the "s200 ..." > > architecture. I ran this on a 300 series machine, that returns "HP-UX > > kzin 7.0 B 9000/375 kzin" for "uname -a". > > This is due to a deficiency in /usr/bin/file and/or /etc/magic. It > looks like all occurrences of "s200" in /etc/magic ought to be > "s300/s400" now. This is *not* a flame. Just simple disagreement.... I disagree. For various reasons, we are still developing code for the 68010 processor. If I have one of the *old* binaries on my system, I want file to tell me that it is s200. File should be altered to scan an object/executable for the extended op codes supported by the '030 and (real soon now :-) the '040. > In addition, /usr/bin/file seems not to notice that a > file has been compiled with the -ffpa flag and requires an FPA card to > run (on a 9000/350, for example). > Again, this would have to be a source-level change to 'file' to scan for the fpa instructions... Wouldn't be very hard to do... > Bob > [Not an official, etc.] -jeff- -- ---------------------------------------------------------------------- I said it, not the people I work for. ---------------------------------------------------------------------- Jeff Minnig | (402) 476-8278 Design Data | 1033 'O' St. Suite 324 | {hpfcla,sparky,unocss}!dsndata!jeff Lincoln NE 68508 | ---------------------------------------------------------------------- Home is where your keyboard is. ----------------------------------------------------------------------
graham@hparc0.HP.COM (Graham Eddy) (02/12/91)
#include <standard/disclaimer.h>
> vendor has done the Right Thing(tm).
^^^^
aha! now the bunfight begins: which vendor OWNS "Right Thing"?
what do the others do..?
-graham "if you see a head, kick it"
mike@hpfcso.FC.HP.COM (Mike McNelly) (02/12/91)
> I disagree. For various reasons, we are still developing code > for the 68010 processor. If I have one of the *old* binaries on my > system, I want file to tell me that it is s200. File should be > altered to scan an object/executable for the extended op codes > supported by the '030 and (real soon now :-) the '040. I hope you're either using your own compilers or you're saving away the old HP 68010 compilers because HP no longer supports a 68010 mode for new releases on its compiler packages. Mike McNelly mike@fc.hp.com