Re: [OpenH323]Compilation error under debian
Sorry all, a pb between gcc3 and gcc 2.95.4.
don't acte !
François
On Wed, 12 Dec 2001 13:40:25 +0100
François Chenais <francois@chenais.net> wrote:
> Hello
>
> Look at this error while trying to build openh323 1.7.4 uder debian woody
> gcc version 2.95.4
>
>
> any idea ? Thanks
>
>
> François
>
>
> Francois : make
> Created dependencies.
> set -e; make -C src optdepend; make -C samples/simple optdepend;
> make[1]: Entering directory `/disks/opt/OPENH323/openh323-1.7.4/src'
> /opt/OPENH323/pwlib/tools/asnparser/obj_linux_x86_r/asnparser -s2 -m H225 -r MULTIMEDIA-SYSTEM-CONTROL=H245 -c /opt/OPENH323/
> openh323/src/h225.asn
> /opt/OPENH323/pwlib/tools/asnparser/obj_linux_x86_r/asnparser: error while loading shared libraries: libgcc_s.so.1: cannot op
> en shared object file: No such file or directory
> make[1]: *** [/opt/OPENH323/openh323/include/h225.h] Error 127
> make[1]: Leaving directory `/disks/opt/OPENH323/openh323-1.7.4/src'
> make: *** [optdepend] Error 2
>
> --
> Francois.Chenais@citb.bull.net
> BULL-CITB tel:(+33) 556 437 848 Home: francois@chenais.net
> 207, cours du Médoc fax:(+33) 556 437 978 http://www.citb.bull.net
> 33000 Bordeaux BullCom: 227 7848 ICQ :3886291
> -------------------------------------------------------------- Linux -----
> ------------------------------------------------------------------------
> Check the FAQ before asking! - http://www.openh323.org/~openh323/fom.cgi
> The OpenH323 Project mailing list, using Mailman. To unsubscribe or
> change your subscription options, goto
> http://www.openh323.org/mailman/listinfo/openh323
> Maintained by Quicknet Technologies, Inc - http://www.quicknet.net
> ------------------------------------------------------------------------
>
--
Francois.Chenais@citb.bull.net
BULL-CITB tel:(+33) 556 437 848 Home: francois@chenais.net
207, cours du Médoc fax:(+33) 556 437 978 http://www.citb.bull.net
33000 Bordeaux BullCom: 227 7848 ICQ :3886291
-------------------------------------------------------------- Linux -----
Reply to: