Date: Sat, 20 May 2000 11:47:34 -0700 From: Arun Sharma <adsharma@sharmas.dhs.org> To: "David O'Brien" <obrien@freebsd.org> Cc: kde-devel@kde.org, ports@freebsd.org Subject: Re: C++ exception handling and non Linux platforms Message-ID: <20000520114734.A2904@sharmas.dhs.org> In-Reply-To: <20000520103959.A12924@dragon.nuxi.com>; from David O'Brien on Sat, May 20, 2000 at 10:39:59AM -0700 References: <20000519083947.A47819@sharmas.dhs.org> <20000520103959.A12924@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 20, 2000 at 10:39:59AM -0700, David O'Brien wrote: > On Fri, May 19, 2000 at 08:39:47AM -0700, Arun Sharma wrote: > > Most non Linux platforms do not link in libgcc.a by default. > > Uh... NO! Try running ``cc -v'' sometimes on FreeBSD. libgcc.a is a > *REQUIRED* library to link against when using GCC. I didn't express myself correctly in that sentence. Though libgcc.a is linked by default, the symbols don't participate in dynamic linking. With -Wl,-export-dynamic: $ objdump -T .libs/konqueror | grep __eh 0804ad64 g DF .text 00000022 __eh_alloc 0804ad88 g DF .text 00000013 __eh_free 0804cf44 g DF .text 00000042 __eh_rtime_match and without -Wl,-export-dynamic: $ objdump -T .libs/konqueror | grep __eh 08049338 g DF .text 00000022 __eh_alloc > There is C++ exception handling code in Linux's glibc2, that I cannot > fathom why they put it there. I have a feeling your problems are the > fault of the software you are trying to port. I don't see any C++ exception handling symbols in Linux glibc2. $ nm /lib/libc.so.6 | grep eh 0005b8f0 t freehook 0005c0e0 t tr_freehook -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000520114734.A2904>