From owner-freebsd-bugs@FreeBSD.ORG Fri Dec 26 08:10:19 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CBE216A4CE for ; Fri, 26 Dec 2003 08:10:19 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9909C43D39 for ; Fri, 26 Dec 2003 08:10:16 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) hBQGAGFR063848 for ; Fri, 26 Dec 2003 08:10:16 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBQGAGt3063847; Fri, 26 Dec 2003 08:10:16 -0800 (PST) (envelope-from gnats) Date: Fri, 26 Dec 2003 08:10:16 -0800 (PST) Message-Id: <200312261610.hBQGAGt3063847@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Subject: Re: misc/60243: Problem in calling kpathsea library from Python extension X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2003 16:10:19 -0000 The following reply was made to PR misc/60243; it has been noted by GNATS. From: Kris Kennaway To: Jin-Hwan Cho Cc: FreeBSD-gnats-submit@FreeBSD.org, "Cho, Jin-Hwan" Subject: Re: misc/60243: Problem in calling kpathsea library from Python extension Date: Fri, 26 Dec 2003 08:00:35 -0800 On Mon, Dec 15, 2003 at 09:48:59AM +0900, Jin-Hwan Cho wrote: > calling "hash_create()" function (defined in hash.c). However, in FreeBSD, > the "hash_create()" was not called properly. After changing the name > "hash_create()" to another one, for example, "hash_create2()", everything > worked fine. I'd like to know exact reason why this kind of problem > occurs in FreeBSD. hash_create is a symbol defined in libc.so.4. You're calling that function instead of the one in your library. I'm not sure whether this symbol needs to be exported from libc, because it doesn't appear to be in libc.so.5. Kris