Does this page help? 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=101048

A Google search on "hidden symbol __dso_handle" doesn't turn up many
other useful entries.

On Mon, Jul 05, 2004 at 11:17:04AM +0100, James Vanns wrote:
> Thats great! Cheers Wei Dei - it worked fine. However, when trying to
> link against the resulting shared library I get this error from ld:
> 
> /usr/bin/ld: cryptest: hidden symbol `__dso_handle' in
> /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/crtbegin.o is referenced by DSO
> 
> This includes the cryptest executable as well as bespoke code. Any
> ideas?
> 
> Sorry!
> 
> Jim
> 
> On Sat, 2004-07-03 at 03:03, Wei Dai wrote:
> > Please try the attached patch.
> > 
> > On Fri, Jul 02, 2004 at 12:35:20PM +0100, James Vanns wrote:
> > > All,
> > > 
> > > When trying to compile integer.cpp with the following:
> > > 
> > > g++ -pipe -msse2 -march=i386 -O1 -fPIC -c integer.cpp
> > > 
> > > I get the error:
> > > 
> > > integer.cpp: In function `void CryptoPP::CpuId(unsigned int, word32*)':
> > > integer.cpp:877: error: can't find a register in class `BREG' while
> > > reloading
> > >    `asm'
> > > 
> > > Now, I know it's because of fPIC but I'd like to try and build this as a
> > > shared library. Anyone know of any workarounds for this? The code g++ is
> > > complaining about is:
> > > 
> > > __asm__
> > > (
> > >    "cpuid"
> > >    : "=a" (output[0]), "=b" (output[1]), "=c" (output[2]), "=d"
> > > (output[3])
> > >    : "a" (input)
> > > );
> > > 
> > > I'm afraid I know next to nothing about embedded/inline ASM!
> > > 
> > > Cheers
> > > 
> > > Jim Vanns
> > > 
> > > -- 
> > > James Vanns BSc (Hons) MCP
> > > Senior Software Engineer (Linux / C & C++)
> > > Canterbury Christ Church University College
> > > Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x24045370
> > > 
> -- 
> James Vanns BSc (Hons) MCP
> Senior Software Engineer (Linux / C & C++)
> Canterbury Christ Church University College
> Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x24045370
> 

Reply via email to