In message <[EMAIL PROTECTED]> "Akinori MUSHA" writes:
: Oops, obviously I missed the 'Major bumping of libFOO' thread. Take
: msun into account as well, thanks.
I had forgotten about msun :-(. However, I think we're going to try
to do this without an interface change in libc that breaks things
In message <[EMAIL PROTECTED]> "Akinori MUSHA" writes:
: Seems some 4.x/3.x binary that is linked with libm.so does not work on
: 5-CURRENT because libm.so is not properly associated with (the latest)
: libc.so.
:
: So, when a program lets libm refers to __stdout/__stderr from within,
: it fails
At Thu, 15 Feb 2001 20:47:57 +0900,
I wrote:
>
> Seems some 4.x/3.x binary that is linked with libm.so does not work on
> 5-CURRENT because libm.so is not properly associated with (the latest)
> libc.so.
>
> So, when a program lets libm refers to __stdout/__stderr from within,
> it fails as foll
Seems some 4.x/3.x binary that is linked with libm.so does not work on
5-CURRENT because libm.so is not properly associated with (the latest)
libc.so.
So, when a program lets libm refers to __stdout/__stderr from within,
it fails as follows. :(
/usr/libexec/ld-elf.so.1: /usr/lib/libm.so.
