From owner-freebsd-amd64@FreeBSD.ORG  Sun Nov 23 04:47:53 2003
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9550C16A4CE
	for <amd64@freebsd.org>; Sun, 23 Nov 2003 04:47:53 -0800 (PST)
Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F385643FCB
	for <amd64@freebsd.org>; Sun, 23 Nov 2003 04:47:51 -0800 (PST)
	(envelope-from adridg@cs.kun.nl)
Received: from localhost by pandora.cs.kun.nl
	via odin.cs.kun.nl [131.174.33.33] with ESMTP for <amd64@freebsd.org>
	id hANClnmU003937 (8.12.10/3.58);
	Sun, 23 Nov 2003 13:47:50 +0100 (MET)
From: Adriaan de Groot <adridg@cs.kun.nl>
To: amd64@freebsd.org
Date: Sun, 23 Nov 2003 13:47:38 +0100
User-Agent: KMail/1.5.93
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200311231347.38353.adridg@cs.kun.nl>
Subject: Ports mixing libc and libc_r
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Nov 2003 12:47:53 -0000

ogg123 bus errors on me all the time, in code that looks perfectly innocuous
	sprintf(data,"%05li:%05.2f",min,sec);
and i suspect it's because ogg123 links against both libc_r and libc:

beans.ebn.kun.nl$ldd `which ogg123`
/usr/local/bin/ogg123:
        libvorbisfile.so.3 => /usr/local/lib/libvorbisfile.so.3 (0x20063d000)
        libvorbis.so.2 => /usr/local/lib/libvorbis.so.2 (0x200744000)
        libm.so.2 => /lib/libm.so.2 (0x200875000)
        libogg.so.4 => /usr/local/lib/libogg.so.4 (0x20099d000)
        libao.so.3 => /usr/local/lib/libao.so.3 (0x200aa2000)
        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x200ba8000)
        libcurl.so.2 => /usr/local/lib/libcurl.so.2 (0x200d98000)
        libintl.so.5 => /usr/local/lib/libintl.so.5 (0x200ec6000)
        libc_r.so.5 => /usr/lib/libc_r.so.5 (0x200fcf000)
        libc.so.5 => /lib/libc.so.5 (0x2010ff000)
        libssl.so.3 => /usr/lib/libssl.so.3 (0x201330000)
        libcrypto.so.3 => /lib/libcrypto.so.3 (0x201475000)
        libz.so.2 => /lib/libz.so.2 (0x201708000)


this is after a straightforward ports make && make install. Now, before I go 
chasing phantoms, (1) is this bad? (2) the final link of ogg123 explicitly 
links with -lc_r, is that bad?

Thanks,
[ade]

-- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org>
            If the door is ajar, can we fill it with door-jamb?