john@bradley.UUCP (04/23/87)
/* Written 9:16 am Apr 23, 1987 by bradley.UUCP!john in bradley:comp.sys.att */ /* ---------- "Binary incompatibility on SysV R2.1" ---------- */ I have a 3B2/300 running System V Release 2.1 and while trying to run some commercial programs (filePro 16/Crystalwriter), I get the following error: foo: cannot execute In the 2.1 Release notes and it says that certain programs compiled with an older C compiler will cause this problem. It then tells you to recompile the offending program with a 3.0 or newer version of the C compiler. It also says that you can to a 'dump -vf foo' and if you see a F_BM32RST flag set, then you must recompile it. What does the F_BM32RST flag do and is there a way to convert the binary to get it to run? We are going to upgrade our machine(s) to release 3 this summer, will this problem also exist when I upgrade to 3.[01] When I mentioned the problem to the hot line about filePro not being able to run, they basically refused to listen to me since filePro is not supported by AT&T. I just wanted to find out what the differences were between 2.0 and 2.1, but they still wouldn't listen. They told me it wasn't their problem and that I could talk to Small Computer Company (makers of filePro 16) By the way, Small wouldn't listen to me either, they said it "wasn't their problem, and I should talk to AT&T) It is good to see that somethings never change. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv John Lengeling UUCP: {cepu,ihnp4,uiucdcs}!bradley!john Bradley University ARPA: cepu!bradley!john@UCLA-LOCUS Bradley Hall Room 6F PH: (309) 677-2230 Peoria, IL 61625 /* End of text from bradley:comp.sys.att */