[gentoo-user] using g++ instead of gcc to build abiword

[gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

I have been getting various error messages when I try to build abiword (e.g. 
"undefined reference to `operator delete(void*)'").  I get this problem both 
with abiword-2.2.11 and with a home-rolled ebuild for 2.4.1.  A google search 
suggests that these would be cured if I were to build abiword using g++ 
instead of gcc.  How can I do this in portage?  Do I need to emerge anything 
to be able to use g++?

Many thanks
Robert


-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Peter Gordon]

Robert Persson said:
> suggests that these would be cured if I were to build abiword using g++
> instead of gcc.  How can I do this in portage?  Do I need to emerge
> anything to be able to use g++?

Nope. You should have it by default, since it's part of GCC.

I'm not certain, but try adding 'CC=g++' to your /etc/make.conf file when
doing this. Actually, it may be a better idea to this with the ebuld only,
as you probably don't want to use g++ as your C compiler. In that case you
could add 'CC=g++' to the econf call in the src_compile function in the
.ebuild file.

Hope that gelps!
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Peter Gordon]

Peter Gordon said:
> Hope that gelps!
That should be "helps". Sorry about that. Please excuse my apparent
lack of caffeine. :o

--Peter
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Richard Fish]

Peter Gordon wrote:

>Robert Persson said:
>  
>
>>suggests that these would be cured if I were to build abiword using g++
>>instead of gcc.  How can I do this in portage?  Do I need to emerge
>>anything to be able to use g++?
>>    
>>
>
>Nope. You should have it by default, since it's part of GCC.
>  
>

Peter is right, unless you merged gcc with the "nocxx" USE flag.

Also, gcc will do "g++" automatically if the source files are named 
correctly (.cxx, .cc, or .cpp).  So the CC= trick should really not be 
necessary.  But rather than editing any files, you can try:

CC=g++ emerge abiword

If that doesn't work, I suggest posting the output of emerge --info and 
emerge --verbose --pretend gcc.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

No worries.  I ned all the hlep I can get ;-)

On October 21, 2005 05:12 pm Peter Gordon was like:
> Peter Gordon said:
> > Hope that gelps!
>
> That should be "helps". Sorry about that. Please excuse my apparent
> lack of caffeine. :o
>
> --Peter

-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

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*'

for 1.2.11 and something similar for 1.4.1.

zebedee ~ # emerge --info
Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.5-r2, 
2.6.13-mm1 i686)
=================================================================
System uname: 2.6.13-mm1 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.6.13
ccache version 2.3 [disabled]
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer -mfpmath=sse"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer -mfpmath=sse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org 
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dfx 3dnow 3dnowext X X509 aac acpi aim alsa apache2 apm arts artsd 
audiofile avi bash-completion berkdb bindist bitmap-fonts bzlib calendar 
cdparanoia cdr crypt cups curl dba dga directfb divx4linux doc dvb dvd dvdr 
eds emacs emboss encode erandom esd fam ffmpeg flac flash foomaticdb fortran 
freetds gcj gd gdbm gif gimpprint gphoto2 gpm gstreamer gtk gtk2 gtkhtml 
guile hal i8x0 icc ieee1394 imagemagick imap imlib innodb insecure-drivers 
ithreads jack jack-tmpfs java jikes jpeg jpeg2k junit kde kdeenablefinal 
kerberos krb4 ladcca ladspa ldap libg++ libwww lm_sensors lzo mad maildir 
matroska md5sum memlimit mikmod mime ming mmx motif mozilla mp3 mpeg 
multitarget mysql nas ncurses network nls nptl nptlonly objc odbc offensive 
ogg oggvorbis openal openexr opengl oss pam pcre pdflib perl php png 
portaudio postgres povray ppds python qt quicktime rdesktop readline real 
rrdtool rtc samba scanner sdk sdl session slang slp sndfile speex spell sse 
sse2 ssl svg svga tcltk tcpd tetex theora threads tiff truetype 
truetype-fonts type1-fonts udev unicode usb v4l v4l2 vhosts vorbis wmf x86 
xanim xine xinerama xml xml2 xmms xprint xscreensaver xv xvid xvmc yahoo 
zeroconf zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

zebedee ~ # emerge -pv gcc

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[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

Total size of downloads: 26,919 kB

On October 21, 2005 05:14 pm Richard Fish was like:
> Also, gcc will do "g++" automatically if the source files are named
> correctly (.cxx, .cc, or .cpp).  So the CC= trick should really not be
> necessary.  But rather than editing any files, you can try:
>
> CC=g++ emerge abiword
>
> If that doesn't work, I suggest posting the output of emerge --info and
> emerge --verbose --pretend gcc.
>
> -Richard

-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

Oops.  I meant to refer to releases 2.2.11 and 2.4.1.

On October 21, 2005 08:14 pm Robert Persson was like:
> I just did CC=g++ and I now get a different error, both with 1.2.11 and
> 1.4.1, namely:

-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword - more weirdness

[Robert Persson]

I just tried to re-emerge abiword-2.2.10, the ebuild of which obviously worked 
successfully last time I emerged it, but this time it fails for the same 
reason that 2.2.11 and my hand-rolled 2.4.1 keep failing, namely:

	undefined reference to `__gxx_personality_v0'

when I "emerge =abiword-2.x.x" and

	cdump.c: In function `int main(int, char**)':
	cdump.c:99: error: invalid conversion from `void*' to `unsigned char*'

when I "CC=g++ emerge =abiword-2.x.x".

I haven't changed anything recently except for what gets done automatically 
when I emerge -u world (and then accept most of the config file changes 
offered by etc-update).

Any ideas?

Thanks
Robert

-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Richard Fish]

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

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

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
ireneshusband@fastmail.fm
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

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Dave Nebinger]

On Saturday 22 October 2005 07:29 pm, Robert Persson wrote:
> 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?

I think at this point you'll have to post some of the output generated when 
the ebuild fails before we'll be able to help you any further...

Just saying you're getting error on delete(void*) doesn't really provide much 
info in regards to what was happening at the time.

Dave
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

On October 22, 2005 04:38 pm Dave Nebinger was like:
> I think at this point you'll have to post some of the output generated when
> the ebuild fails before we'll be able to help you any further...

Well here goes...

...
UnixMain.o ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../!
 src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a 
-lglade-2.0 -lgtk-x11-2.0 -lxml2 -lpthread -lz -lgdk-x11-2.0 -latk-1.0 
-lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 
-lgmodule-2.0 -ldl -lglib-2.0     -lSM -lICE -lX11  -Wl,--export-dynamic 
-lgmodule-2.0 -ldl -lglib-2.0    -Wl,--export-dynamic -lgnomeprintui-2-2 
-lgnomeprint-2-2 -lgnomecanvas-2 -lxml2 -lpthread -lz -lart_lgpl_2 
-lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm 
-lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl 
-lglib-2.0   -Wl,--export-dynamic -lenchant -lgmodule-2.0 -ldl -lglib-2.0   
-L/usr/lib -lxml2 -lz -lpthread -lm   -lfribidi -lwv -lwmf -lwmflite 
-lfreetype -lSM -lICE -lX11 -lexpat -ljpeg -lxml2 -lpthread -lglib-2.0 -lpng 
-lz -lm   -lglib-2.0    -lpng12 -lz -lm   -lz -lpopt -lXft -lX11 -lfreetype 
-lXrender -lfontconfig    -pthread -lgthread-2.0 -lglib-2.0    
UnixMain.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x3ef): In function 
`AP_UnixApp::loadStringsFromDisk(char const*, AP_BuiltinStringSet*)':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x45b): In function 
`AP_UnixApp::loadStringsFromDisk(char const*, AP_BuiltinStringSet*)':
: undefined reference to `operator delete(void*)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x489): In function 
`AP_UnixApp::newFrame()':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x4b7): In function 
`AP_UnixApp::newFrame()':
: undefined reference to `operator delete(void*)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x70b): In function 
`AP_UnixApp::copyToClipboard(PD_DocumentRange*, bool)':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x743): In function 
`AP_UnixApp::copyToClipboard(PD_DocumentRange*, bool)':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x783): In function 
`AP_UnixApp::copyToClipboard(PD_DocumentRange*, bool)':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x7bf): In function 
`AP_UnixApp::copyToClipboard(PD_DocumentRange*, bool)':
: undefined reference to `operator new(unsigned int)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x9cc): In function 
`AP_UnixApp::copyToClipboard(PD_DocumentRange*, bool)':
: undefined reference to `operator delete(void*)'
../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0xb98): In function 
`AP_UnixApp::pasteFromClipboard(PD_DocumentRange*, bool, bool)':
: undefined reference to `operator new(unsigned int)'

...about 2 glorious MB of messages about "undefined references" until...


../../../../src/text/fmt/xp/libFmt.a(fl_SelectionPreserver.o)(.eh_frame+0x11): 
undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status
make[4]: *** [AbiWord-2.4] Error 1
make[4]: Leaving directory 
`/var/tmp/portage/abiword-2.4.1/work/abiword-2.4.1/abi/src/wp/main/unix'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/var/tmp/portage/abiword-2.4.1/work/abiword-2.4.1/abi/src/wp/main'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/var/tmp/portage/abiword-2.4.1/work/abiword-2.4.1/abi/src/wp'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/var/tmp/portage/abiword-2.4.1/work/abiword-2.4.1/abi/src'
make: *** [all-recursive] Error 1

!!! ERROR: app-office/abiword-2.4.1 failed.
!!! Function src_compile, Line 60, Exitcode 2

-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Richard Fish]

Robert Persson wrote:

>On October 22, 2005 04:38 pm Dave Nebinger was like:
>  
>
>>I think at this point you'll have to post some of the output generated when
>>the ebuild fails before we'll be able to help you any further...
>>    
>>
>
>Well here goes...
>
>...
>UnixMain.o ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../..!
 /!
> src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a ../../../../src/wp/ap/libAp.a ../../../../src/wp/impexp/libImpExp.a ../../../../src/af/xap/libXap.a ../../../../src/af/util/libUtil.a ../../../../src/af/gr/libGr.a ../../../../src/af/ev/libEv.a ../../../../src/other/spell/xp/libSpell.a ../../../../src/other/ttftool/unix/libTtfTool.a ../../../../src/pkg/linux/apkg/libApkg.a ../../../../src/text/fmt/xp/libFmt.a ../../../../src/text/ptbl/xp/libPtbl.a 
>-lglade-2.0 -lgtk-x11-2.0 -lxml2 -lpthread -lz -lgdk-x11-2.0 -latk-1.0 
>-lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 
>-lgmodule-2.0 -ldl -lglib-2.0     -lSM -lICE -lX11  -Wl,--export-dynamic 
>-lgmodule-2.0 -ldl -lglib-2.0    -Wl,--export-dynamic -lgnomeprintui-2-2 
>-lgnomeprint-2-2 -lgnomecanvas-2 -lxml2 -lpthread -lz -lart_lgpl_2 
>-lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm 
>-lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl 
>-lglib-2.0   -Wl,--export-dynamic -lenchant -lgmodule-2.0 -ldl -lglib-2.0   
>-L/usr/lib -lxml2 -lz -lpthread -lm   -lfribidi -lwv -lwmf -lwmflite 
>-lfreetype -lSM -lICE -lX11 -lexpat -ljpeg -lxml2 -lpthread -lglib-2.0 -lpng 
>-lz -lm   -lglib-2.0    -lpng12 -lz -lm   -lz -lpopt -lXft -lX11 -lfreetype 
>-lXrender -lfontconfig    -pthread -lgthread-2.0 -lglib-2.0    
>UnixMain.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
>../../../../src/wp/ap/libAp.a(ap_UnixApp.o)(.text+0x3ef): In function 
>`AP_UnixApp::loadStringsFromDisk(char const*, AP_BuiltinStringSet*)':
>  
>

Could you post the output of "gcc -print-search-dirs"?

Particularly, I am looking to see something like:

libraries: =/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/...

I think the libstdc++ library in this directory contains the 
gxx_personality_v0 symbol, but the stdc++ in /usr/lib does not.  If gcc 
was somehow linking against /usr/lib first, it would pull in the 
libstdc++ from there, and you would end up with the problem above.  So 
you should also check that /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 contains 
usable libstdc++ files:

carcharias lib # ll /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++*
-rw-r--r--  1 root root 1702000 Sep 10 20:22 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.a
-rwxr-xr-x  1 root root     957 Sep 10 20:22 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
lrwxrwxrwx  1 root root      18 Oct  9 00:49 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so -> libstdc++.so.6.0.3
lrwxrwxrwx  1 root root      18 Oct  9 00:49 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 -> libstdc++.so.6.0.3
-rwxr-xr-x  1 root root 1077149 Sep 10 20:22 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6.0.3
-rw-r--r--  1 root root 1798478 Sep 10 20:22 
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++_pic.a

-Richard



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Hans-Werner Hilse]

Hi,

On Sat, 22 Oct 2005 18:08:47 -0700
Robert Persson <ireneshusband@yahoo.co.uk> wrote:

> On October 22, 2005 04:38 pm Dave Nebinger was like:
> > I think at this point you'll have to post some of the output generated when
> > the ebuild fails before we'll be able to help you any further...
> 
> Well here goes...
> [...]

What you cited then looks like the final linking step. My first guess
is that the ebuild doesn't list all dependencies of abiword that it
actually has and in your case you're missing one. Check the -lxxxxx
lines (libraries) if something is obviously not yet installed. I don't
really know which library is supposed to provide those missing
functions, and searching for them doesn't make lot of sense - I guess
"new" and "delete" aren't very typical for one certain library...

Have you got some old .h header files lying around
in /usr/local/include? This might totally mess up things, as well as
duplicate libraries (of different versions) in /usr/lib
and /usr/local/lib.

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

On October 22, 2005 11:53 pm Richard Fish was like:

> Could you post the output of "gcc -print-search-dirs"?
>
> Particularly, I am looking to see something like:
>
> libraries: =/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/...
>
> I think the libstdc++ library in this directory contains the
> gxx_personality_v0 symbol, but the stdc++ in /usr/lib does not.  If gcc
> was somehow linking against /usr/lib first, it would pull in the
> libstdc++ from there, and you would end up with the problem above.

zebedee ~ # gcc -print-search-dirs
install: /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/
programs: 
=/usr/libexec/gcc/i686-pc-linux-gnu/3.4.4/:/usr/libexec/gcc/i686-pc-linux-gnu/3.4.4/:/usr/libexec/gcc/i686-pc-linux-gnu/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/:/usr/libexec/gcc/i686-pc-linux-gnu/3.4.4/:/usr/libexec/gcc/i686-pc-linux-gnu/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/
libraries: 
=/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/lib/i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/lib/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../i686-pc-linux-gnu/3.4.4/:/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../:/lib/i686-pc-linux-gnu/3.4.4/:/lib/:/usr/lib/i686-pc-linux-gnu/3.4.4/:/usr/lib/

There is a lot of convoluted repetition here.  Would that make a difference? 

> So 
> you should also check that /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 contains
> usable libstdc++ files:
>
> carcharias lib # ll /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++*
> -rw-r--r--  1 root root 1702000 Sep 10 20:22
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.a
> -rwxr-xr-x  1 root root     957 Sep 10 20:22
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
> lrwxrwxrwx  1 root root      18 Oct  9 00:49
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so -> libstdc++.so.6.0.3
> lrwxrwxrwx  1 root root      18 Oct  9 00:49
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 -> libstdc++.so.6.0.3
> -rwxr-xr-x  1 root root 1077149 Sep 10 20:22
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6.0.3
> -rw-r--r--  1 root root 1798478 Sep 10 20:22
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++_pic.a

All of the above are where they should be on my system.

> -Richard

Thanks
Robert
-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

On October 23, 2005 02:39 am Hans-Werner Hilse was like:

> What you cited then looks like the final linking step. My first guess
> is that the ebuild doesn't list all dependencies of abiword that it
> actually has and in your case you're missing one. Check the -lxxxxx
> lines (libraries) if something is obviously not yet installed. I don't
> really know which library is supposed to provide those missing
> functions, and searching for them doesn't make lot of sense - I guess
> "new" and "delete" aren't very typical for one certain library...

It sounds, from what Richard Fish has said, as if libstdc++ is the culprit, 
and I do have that installed.  I have also been having the same kind of error 
with some other ebuilds, some of which had also worked fine in the past, 
which is another reason to believe abiword itself isn't the problem.  
Couldn't find anything weird beginning "-l" in the emerge stdout/stderr.
>
> Have you got some old .h header files lying around
> in /usr/local/include? This might totally mess up things, as well as
> duplicate libraries (of different versions) in /usr/lib
> and /usr/local/lib.

Nope.  Nothing like that.  Only stuff to do with audio processing and a couple 
of other obscure things.  But both you and Richard agree that multiple 
installed library versions may be the problem.  That certainly sounds 
plausible to me.

Many thanks
Robert
 
-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] using g++ instead of gcc to build abiword

[Robert Persson]

On October 22, 2005 11:53 pm Richard Fish was like:
> I think the libstdc++ library in this directory contains the
> gxx_personality_v0 symbol, but the stdc++ in /usr/lib does not.  If gcc
> was somehow linking against /usr/lib first, it would pull in the
> libstdc++ from there, and you would end up with the problem above.  So
> you should also check that /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 contains
> usable libstdc++ files:

Halleluia!

I moved libstdc++.so.2.8.0 and libstdc++.so.2.9.0 out of /usr/lib and abiword 
then compiled and linked cleanly.

Do those libraries I moved serve any useful purpose?  I thought that 
libstdc++-v3 was supposed meant to ensure backward compatibility.  So why do 
I have version 2 libraries on my system at all?  Should I make a bug report 
about this?  If so, should I say it is a portage problem, a gcc problem or 
something else?

Anyway, many thanks, Richard and others, for helping me (fingers crossed!) 
solve this problem.

Robert
-- 
Robert Persson

"Don't use nuclear weapons to troubleshoot faults."
(US Air Force Instruction 91-111, 1 Oct 1997)

-- 
gentoo-user@gentoo.org mailing list