griffin@frith.egr.msu.edu (03/19/90)
Can one link arp.lib with Manx 5.0a? I cannot get the linker to accept any version of arp.lib that I have (1.3 ARP) arp.lib 11524 21-Aug-89 arp.lib 17472 27-Jul-89 <-- Manx version arp.lib 3180 10-May-88 <-- Lattice version Using either of the first two gives me a 'not an object module' error, and it doesn't understand Lattice's, although it looks like an object module to the linker. Wasn't there something about not needing glue routines anymore? Do I need a newer arp.lib? I haven't seen any. I'm back to using 3.6a until then. Dan Griffin griffin@frith.egr.msu.edu "We're waiting for Godot..."
scotth@corp.sgi.com (Scott Henry) (03/19/90)
Dan> Can one link arp.lib with Manx 5.0a? I cannot get the linker to Dan> accept any version of arp.lib that I have (1.3 ARP) Dan> arp.lib 11524 21-Aug-89 arp.lib 17472 27-Jul-89 <-- Manx version arp.lib 3180 10-May-88 <-- Lattice version Dan> Using either of the first two gives me a 'not an object module' error, Dan> and it doesn't understand Lattice's, although it looks like an object Dan> module to the linker. Wasn't there something about not needing glue Dan> routines anymore? Do I need a newer arp.lib? I haven't seen any. I'm Dan> back to using 3.6a until then. In the documentation sent with Manx Aztec C v5.0, they state that libraries from v3.6 and earlier will need to be recompiled, as the format changed incompatibly. I haven't checked to see if the v3.6 linker option "+L <lattice-lib> +L" still works, allowing Manx to link against Lattice libs (I never used it under 3.6). I just finished re-compiling the ARP glue libraries from source. Manx changed the way make works, so I am having trouble compiling my program that will use the ARP interface... BTW: Manx changed the default .c.o action in make so that if the source is in a different directory than the current, the object goes in the other directory, instead of the old Manx (and current Unix -- I think) action that the object goes in the current directory. Does anybody else think that this is a mistake? -- Scott Henry <scotth@sgi.com> | These are my | Tardis Express -- when it Information Services, | Opinions only! | absolutely, positively Silicon Graphics, Inc | Whose else? | has to be there -- yesterday.
chymes@fribourg.csmil.umich.edu (Charles Hymes) (03/20/90)
In article <6981@cps3xx.UUCP> griffin@frith.egr.msu.edu () writes: >Can one link arp.lib with Manx 5.0a? I cannot get the linker to >accept any version of arp.lib that I have (1.3 ARP) > >arp.lib 11524 21-Aug-89 >arp.lib 17472 27-Jul-89 <-- Manx version >arp.lib 3180 10-May-88 <-- Lattice version > >Using either of the first two gives me a 'not an object module' error, >and it doesn't understand Lattice's, although it looks like an object >module to the linker. Wasn't there something about not needing glue >routines anymore? Do I need a newer arp.lib? I haven't seen any. I'm >back to using 3.6a until then. > >Dan Griffin >griffin@frith.egr.msu.edu "We're waiting for Godot..." This is EXACTLY the problem that I have been messing with for three weeks, and it is really pissing me off. Yes, we have to wait until A) The kind folks on the ARP progect release a Manx 5.0a compatible arp.lib B) The above mentioned omnipotent Gurus release the source to ARP C) Our helpful buddies at Manx release some program that will convert old object files to a form that can be handed by the new complier-linker. This is essential to the Amiga programming community, because none of us can use any of the linkable libraries with the new compiler. If anyone knows anything about A, B or C kindly post it to the net, or at least me and Dan. Charweed Hymerfan, Mad as Hell and unable to do anything but take it.
hessmann@unipas.fmi.uni-passau.de (Georg Hessmann) (03/20/90)
In article <1990Mar19.164137.20616@csmil.umich.edu> chymes@fribourg.csmil.umich.edu (Charles Hymes) writes: ]In article <6981@cps3xx.UUCP> griffin@frith.egr.msu.edu () writes: ]>Can one link arp.lib with Manx 5.0a? I cannot get the linker to ]>accept any version of arp.lib that I have (1.3 ARP) ]> [...] ] ]This is EXACTLY the problem that I have been messing with for three weeks, and it ]is really pissing me off. ]Yes, we have to wait until ]A) The kind folks on the ARP progect release a Manx 5.0a compatible arp.lib ]B) The above mentioned omnipotent Gurus release the source to ARP ]C) Our helpful buddies at Manx release some program that will convert old object ] files to a form that can be handed by the new complier-linker. ] ] ]This is essential to the Amiga programming community, because none of us can use ]any of the linkable libraries with the new compiler. ]If anyone knows anything about A, B or C kindly post it to the net, or at least ]me and Dan. I can't help you using the arp.lib with the new Manx Compiler. But why don't you use the #pragma command to call the functions of the arp.library directly? Either use the arp_proto.h with the Lattice pragmas (Manx understands them), or use the example program (I have forgotten it's name) to convert .fd files to Manx pragmas. This works fine with my programs. Hope this helps, even if that doesn't solve the original problem, Georg. -- hessmann@unipas.fmi.uni-passau.de hessmann@unipas.uucp
vkr@osupyr.mps.ohio-state.edu (Vidhyanath K. Rao) (03/24/90)
In article <951@unipas.fmi.uni-passau.de> hessmann@unipas.fmi.uni-passau.de (Georg Hessmann) writes: [... dealing with using ARP with Manx 5.0] >But why don't you use the #pragma command to call the functions of the >arp.library directly? > >Either use the arp_proto.h with the Lattice pragmas (Manx understands them), >or use the example program (I have forgotten it's name) to convert .fd files >to Manx pragmas. [The program referred to is MAPFD] This doens't work all the time, as several functions have two return values: In particlular anything that is tracked by ARP, such as ArpOpen. And of course, there are the Printf type calls. I am trying to build arp.lib and arp16.lib by mixing the prototypes and glues for the rest of the modules. All the necessary source files were there, but not the library. There was another message in this thread that somebody else was doing the same. Hopefully this will be uploaded. I have other questions concerning Manx 5.0 files: function.h, which declares the prototypes of all Amiga functions declares many parameters that I thought were ULONGs to be long: draw mode, pen color etc. Would this ever be a problem [in 1.4, 1.5]? exec_lib.i is still missing the macro FUNCDEF. This is true of the Manx file, the 1.3 include files in the developer's update I got from CATS etc. The Manx crt0.asm refers to "asmsupp.i" which is not there. The ARexx "rxslib.i" file seems to refer to a file called "exec/macros.i". [Actually, it checks to see if "EXEC_MACROS_I" is defined. I don't have this file either. Can anybody enlighten me on this? Better yet, where can I find all the macros I am supposed to have, but don't? Thanks in advance for any information you can shed on this. -- It is the man, not the method, that Nath solves the problem. vkr@osupyr.mps.ohio-state.edu -Poincare. (614)-366-9341