Date: Fri, 29 Jul 2005 00:30:30 +0200 From: Joerg Sonnenberger <joerg@britannica.bec.de> To: freebsd-hackers@FreeBSD.org Subject: Re: ProPolice symbols in libc or libssp ? Message-ID: <20050728223030.GA4570@britannica.bec.de> In-Reply-To: <20050728221447.GF68965@obiwan.tataz.chchile.org> References: <20050705153933.GP73907@obiwan.tataz.chchile.org> <20050726232645.GN1610@obiwan.tataz.chchile.org> <20050727000054.GA15018@britannica.bec.de> <20050727233842.GW1610@obiwan.tataz.chchile.org> <20050728023239.GA21179@britannica.bec.de> <20050728221447.GF68965@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 29, 2005 at 12:14:47AM +0200, Jeremie Le Hen wrote: > > Make sure you patch the right place and _not_ the shared part. Does the > > attached patch work for you? > > Yes, this worked, thank you ! This implies that libssp must be linked > with -nodefaultlibs option to avoid linking itself against libssp. But > this also prevents it from being linked against libgcc. Is it > something harmful or not (in other words should I manually add -lgcc to > LDFLAGS) ? The problem with linking -lssp is that you normally want to aovid the circular dependency with libc. For static libraries that's not a problem, but for dynamic loading it is a bit nasty. One idea is to build libssp similiar to RTLD by directly linking the necessary parts of libc in, you can use a linker script to hide the symbols. For linking -lssp itself, you could try to exploit "-fno-stack-protector" and use that to not link libssp into. Joerg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050728223030.GA4570>