[omniORB] Compilation
Belcher, Jim
belcher@inquiregroup.com
Tue, 14 Mar 2000 13:06:30 -0500
I don't know, the problem I am having seems to be
coming from a make or script file, not from a
compiler error. I built my gcc using the instructions
that came with the download, and it seems to
work fine on other things.
Jim
-----Original Message-----
From: James Riden [mailto:jamesr@harlequin.co.uk]
Sent: Tuesday, March 14, 2000 12:59 PM
To: Sai-Lai Lo
Cc: Belcher, Jim; omniorb-list@uk.research.att.com
Subject: Re: [omniORB] Compilation
Jim,
I've seen the same behaviour on Solaris 2.7 / gcc-2.95.2, and have put
it down to a misconfigured compiler. (figures, since I built it :)
Can anyone tell me the configure line they've used - this is what I've
got so far:
../gcc-2.95/configure --enable-threads --enable-cpp --with-gnu-gas
--with-gnu-ld --enable-languages=c++ --enable-shared
-prefix=/usr/local/gcc-2.95
cheers,
Jamie
Sai-Lai Lo <S.Lo@uk.research.att.com> writes:
> If omniidl2 core dump even if you have compiled it from scratch on linux,
> then there is a problem with your compiler or platform setup.
>
> There isn't much we suggest except to say that we have tested omniORB on:
>
> 1. Redhat 5.2 with gcc-2.95.1
> 2. Redhat 6.0 and 6.1 with their egcs-1.1.2 compiler.
>
> I don't know if gcc-2.95.2 itself is problematic or is it because you are
> mixing some glibc-2.1 and glibc-2.0 based libraries.
>
> Sai-Lai
>
> >>>>> Belcher, Jim writes:
>
> > Duncan,
> > I just downloaded the file you specified and attempted
> > the compile, with the same result.
>
> > Jim