Re: Static Library startup

2011-12-05 Thread Dave Martin
On Mon, Dec 05, 2011 at 04:47:08PM +, Richard Sandiford wrote: > Richard Sandiford writes: > > Dave Martin writes: > >> Another way of doing a similar thing is to mark __mylib_constructor > >> as undefined in all the objects that make up the library. > >> > >> Unfortunately, there seems to be

Re: Static Library startup

2011-12-05 Thread Richard Sandiford
Richard Sandiford writes: > Dave Martin writes: >> Another way of doing a similar thing is to mark __mylib_constructor >> as undefined in all the objects that make up the library. >> >> Unfortunately, there seems to be no obvious way of doing that: the >> assembler generates undefined symbol refe

Re: Static Library startup

2011-12-05 Thread Richard Sandiford
Dave Martin writes: > Another way of doing a similar thing is to mark __mylib_constructor > as undefined in all the objects that make up the library. > > Unfortunately, there seems to be no obvious way of doing that: the > assembler generates undefined symbol references automatically for > unresol

Re: Static Library startup

2011-12-05 Thread Dave Martin
> On Mon, Dec 5, 2011 at 1:40 AM, Tom Gall wrote: > > I probably know the answer to this already but ... > > > > For shared libs one can define and use something like: > > > > void __attribute__ ((constructor)) my_init(void); > > void __attribute__ ((destructor)) my_fini(void); > > > > Which of co