From: Michael Galetzka Date: Wed, 11 May 94 12:55:13 +0200 To: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: using an own malloc.c I've got a software which uses an own memory manager based on sbrk(). I want to link it together with my programs, which use the malloc(), free() and realloc() routines. They are, of course, unhappy about calling sbrk() directly. That's why I wrote own malloc(), free() and realloc() using the memory manager provided by that software package and added it to that library. (I remember that this worked in a quite similar case on the same machine.) Now I get a error message from the linker malloc.c(.text+0): multiple definition of `malloc (.text)' memblock.c(.text+5bc): first seen here and some similar messages. The same procedure does work with the same files on an UNIX machine with SunOS and GNU-C 2.5.8. On PC I'm using DJGPP 1.1m5. How can I prevent the linker using the malloc() routines from the standard library and make him using my own instead? Many thanks, Michael Galetzka __________________________________________________________________ | | |-|-|-|-| Dipl.-Ing. Michael Galetzka | |---|---|-|-|-|-| | | | |-|-|-|-| Fraunhofer-Institut fuer Integrierte | |---------------| Schaltungen (IIS), Erlangen | | ___ __ | Aussenstelle fuer die Automatisierung | | /_ /__ / _ | des Schaltkreis und Systementwurfs | |/ / / /__/ | | |_______________| Zeunerstrasse 38 | | # # ### D-01069 Dresden | | # # # | | # # ### Tel: +49 351 4640-740 | | # # # Fax: +49 351 4640-703 | | # # #### Email: galetzka AT eas DOT iis DOT fhg DOT de | |__________________________________________________________________|