Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!uunet!mcsun!hp4nl!utrcu1!mi.eltn.utwente.nl!klamer From: klamer@mi.eltn.utwente.nl (Klamer Schutte) Newsgroups: comp.os.minix Subject: Re: c68/libc question Message-ID: Date: 25 Mar 91 10:47:44 GMT References: <1991Mar20.122335.4222@ukpoit.co.uk> Sender: news@utrcu1.UUCP Organization: University of Twente, BSC-El Lines: 24 In <1991Mar20.122335.4222@ukpoit.co.uk> paul@ukpoit.co.uk (Paul Wood) writes: >I assume the library where these should have been put is /usr/lib/libc but I am >a little wary of playing about with the library. Do I just compile all the *.s >files in lib68k and "ar r /usr/lib/libc xxx.o" them (resulting in a mixture of >ack and c68 in one library) or do I replace /usr/lib/libc completely? If I am to >replace the entire library, then what goes in and what gets left out? I have made a separate library with only the lib68k files. I specify them after the standard (ack) libc.a. This means that i now have 3 different way of linking files with cc: 1) ack 2) c68 with sizeof(int) == sizeof(short) 3) c68 with sizeof(int) == sizeof(long) Diffs (OK, hacks) for cc.c on request. But an official cc.c version for c68 >>should<< come from CvW. Klamer -- Klamer Schutte Faculty of electrical engineering -- University of Twente, The Netherlands klamer@mi.eltn.utwente.nl {backbone}!mcsun!mi.eltn.utwente.nl!klamer