Thanks Richard I'm glad you pointed out that gcc version thing to me. But it doesn't change anything about compiling abiword unfortunately, with or without using g++.
The strange thing is that abiword-2.2.10 (the version I currently have installed) was only released last month sometime. So between then and now something has changed on my system to prevent it compiling properly. If gcc hasn't changed then what on earth could it be? Robert On October 22, 2005 02:00 pm Richard Fish was like: > Robert Persson wrote: > >I just did CC=g++ and I now get a different error, both with 1.2.11 and > > 1.4.1, namely: > > > > cdump.c: In function `int main(int, char**)': > > cdump.c:99: error: invalid conversion from `void*' to `unsigned char*' > > Hmm, yes, I guess this is to be expected. C++ is much more strict about > type conversions than C, so you can't really compile .c files as C++ and > expect good results... > > I just emerged 2.2.11, using gcc-3.3.4-r1, without any trouble. One > > thing I noticed though: > >zebedee ~ # emerge --info > >Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.5-r2, > > ... > > >[ebuild R ] sys-devel/gcc-3.4.4-r1 (-altivec) -bootstrap > > -boundschecking -build +fortran +gcj +gtk -hardened -ip28 (-multilib) > > -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp +objc -static -vanilla > > 26,919 kB > > I think this means that, even though have gcc-3.4.4 merged, you are > actually using 3.3.5 to compile things via portage. > > Take a look at the output of "gcc-config -l", and if necessary, change > the active profile with "gcc-config i686-pc-linux-gnu-3.4.4". Then try > emerging again. > > -Richard -- Robert Persson [EMAIL PROTECTED] YahooMess:ireneshusband AIM:shamanicpolice "Don't use nuclear weapons to troubleshoot faults." (US Air Force Instruction 91-111, 1 Oct 1997) -- gentoo-user@gentoo.org mailing list
