Re: popen & pclose; How to report platform-specific bugs?

[Konstantinos Margaritis <kmargar@cc.uoa.gr>]

-----BEGIN PGP SIGNED MESSAGE-----

On Fri, 19 Feb 1999, Randy Gobbel wrote:

>Comments?
>
>Has anyone else run into the popen/pclose problem, or know why it's
>happening?  Seems like my system has been getting more unstable lately.

I had similar problems, after installing libstdc++ 2.91.60. I tried to compile
ace-4.6.17(beta) and it failed with the following excerpt from config.log:

-----
configure:1495: c++ -o conftest -O3 -O3  conftest.C  1>&5
/usr/lib/gcc-lib/powerpc-linux/egcs-2.91.60/libstdc++.so: undefined reference to
 `_IO_proc_close@@GLIBC_2.1'
/usr/lib/gcc-lib/powerpc-linux/egcs-2.91.60/libstdc++.so: undefined reference to
 `_IO_proc_open@@GLIBC_2.1'
collect2: ld returned 1 exit status
configure: failed program was:

#line 1490 "configure"
#include "confdefs.h"

int main(){return(0);}
-----

things went back to normal after I replaced with the old (2.91.58) libstdc++.
I believe it has to do with the fact that the libc I'm using (2.0.100-2) is not
quite fully 2.1-compliant, and some symbols don't have GLIBC2.1 versions. Of
course, I maybe wrong... 

--
Konstantinos Margaritis
kmargar@cc.uoa.gr

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: jtl3UJnmFcFM5RBfofprPBj3NjDMOuDS

iQEVAwUBNsyk3XLbhkskV78BAQG/zggAgnFm98Us4aRwjpyFOZWKODG0V0mJSU8C
Xq+08fVxQ/9AzP6VT5kaZq25GSq9sG9uokTGzO2R2UKxXaPXOGmBx6y89F12iTQI
OPyN9GrqnTfNlLJG1Id+SQU3NrMJh4AZIh65cIxKTgpuUNVYbgI+4Nb3wvi5ZZSc
i/VhdCZzj/sww7fB4HxblOW1bk6HB5UMgx3m0hxMLMV/Q/0TjJ7Vn67A4XzDdCV5
tgBEfzd3/sY3l9AvZjZnyaym73IXtx1lpks5YB8LH3oAGnoygRaT17DaQmxXH25z
mdAvkFuun7wnU+2eWjhAeOY4OvNAbsxDVjhmR3qDwhIt9Qx++3f3yQ==
=RDhl
-----END PGP SIGNATURE-----