Ports mixing libc and libc_r

[Adriaan de Groot]

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 at kde.org>
            If the door is ajar, can we fill it with door-jamb?