Re: gprof problem

• To: Leigh Stoller <stoller@fast.cs.utah.edu>
• Subject: Re: gprof problem
• From: Voon-Li Chung <vlchung@cs.uwa.edu.au>
• Date: Thu, 19 Apr 2001 23:35:52 +0800 (WST)
• cc: oskit-users@fast.cs.utah.edu
• In-Reply-To: <15070.61486.719406.692877@stoller.casco.net>
• Sender: owner-oskit-users@fast.cs.utah.edu

If I remove the oskit_c_p line, I get hundreds of undefined reference
errors when compiling (I haven't included them to save bandwidth); these
go away if I do the recommended "link the C libraries over and over"
technique?

> The one odd thing I notice below is in the link line. You have both the
> freebsd C (-loskit_freebsd_c_p) library and OSKit minimal C library
> (-loskit_c_p) linking in. This could easily cause all kinds of problems
> given that these two libraries implement overlapping sets of functions in
> completely different ways. Get rid of oskit_c and see what happens.
> 
> Note that it looks like you compiled the threads library without STACKGUARD.
> No big deal, just mentioning it.

• Re: gprof problem
• From: Leigh Stoller <stoller@fast.cs.utah.edu>

• Re: gprof problem
• From: Leigh Stoller <stoller@fast.cs.utah.edu>

• Prev: Re: gprof problem
• Next: Re: gprof problem
• Index(es):
  • Main
  • Thread