>>>>> "MK" == Michael Kirby <kirby_at_ess.mc.xerox.com> writes:
MK> On 22 Jan 97 at 11:17, Scott Seighman wrote:
MK> [SNIP]
>> I used "nm" to determined if it (_mcount) was defined, and all appears
>> well...
>> windows.o -O -pipe -L/usr/openwin/lib ../libs/libfvwm2.a -lXpm
>> -lXext -lX11
MK> Well,
MK> When you reference an already installed libfvwm2.a file it isn't
MK> using the one you just compiled, so if there were any changes to
MK> the fvwm library you are going to be hosed.
MK> My suggestion is not to install the fvwm2 library (you shouldn't
MK> need it, unless you are doing some kind of programming), and if
MK> you do, you should be careful of this bug in the future.
MK> Chuck, I thought this was fixed in the makefile, to make it look
MK> for the locally compiled library, instead of an installed on.
Umm...it is:
>> windows.o -O -pipe -L/usr/openwin/lib ../libs/libfvwm2.a -lXpm
^^^^^^^^^^^^^^^^^^
Fully specified path to the local lib. That isn't the problem here.
The _mcount subroutine has is used with profiling, which means that at
least part of the source was compiled with the profiling support
turned on, but the -p (or -pg) option is not being given to the link
step, so it's not linking in the appropriate libs to do the profiling,
hence the missing function.
Chuck
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Jan 22 1997 - 14:58:17 GMT