[Boost-users] g++ linker messages when using boost (gnu.linkonce)

Subject: [Boost-users] g++ linker messages when using boost (gnu.linkonce)
From: peter_foelsche_at_[hidden]
Date: 2008-12-02 14:03:39

/usr/bin/ld: 
`.gnu.linkonce.t._ZSt26__uninitialized_fill_n_auxIPN5boost7variantIchstijlmdePKc
PvNS0_6detail7variant5void_ES7_S7_S7_S7_S7_S7_S7_EEmS8_EvT_T0_RKT1_St12__false_t
ype' referenced in section 
`.gnu.linkonce.r._ZSt26__uninitialized_fill_n_auxIPN5boost7variantIchstijlmdePKc
PvNS0_6detail7variant5void_ES7_S7_S7_S7_S7_S7_S7_EEmS8_EvT_T0_RKT1_St12__false_t
ype' of /shared/eng/build-o/latest_HEAD/linux_x86_64/lib/libclasslib.a
(sprintf2.o): defined in discarded section 
`.gnu.linkonce.t._ZSt26__uninitialized_fill_n_auxIPN5boost7variantIchstijlmdePKc
PvNS0_6detail7variant5void_ES7_S7_S7_S7_S7_S7_S7_EEmS8_EvT_T0_RKT1_St12__false_t
ype' of /shared/eng/build-o/latest_HEAD/linux_x86_64/lib/libclasslib.a
(sprintf2.o)
 
anybody got a clue what is causing these messages and how to avoid them?
It looks like these messages appear only when linking two object files with different optimization flags.
 
Peter

 

 

"The first point (using an init() function in preference to a constructor) is bogus. Using constructors and exception handling is a more general and systematic way of dealing with resource acquisition and initialization errors. This style is a relic of pre-exception C++." -- Stroustrup