Date: Sat, 21 Jun 1997 15:15:41 -0700 From: John Polstra <jdp@polstra.com> To: jkh@time.cdrom.com Cc: current@freebsd.org Subject: Re: Hmmmm, this is new.. Message-ID: <199706212215.PAA08801@austin.polstra.com> In-Reply-To: <21993.866920877@time.cdrom.com> References: <21993.866920877@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> While compiling today's 3.0 SNAP release over at current.freebsd.org, > I noticed: > > building shared tcl library (version 75.1) > ld: /usr/lib/libm.a(i387_s_tan.o): RRS text relocation at 0x2e9d3 for "___generic_tan" > ld: /usr/lib/libm.a(i387_s_tan.o): RRS text relocation at 0x2e9c5 for "___get_hw_float" > ld: /usr/lib/libm.a(i387_s_ceil.o): RRS text relocation at 0x2ea53 for "___generic_ceil" > ld: /usr/lib/libm.a(i387_s_ceil.o): RRS text relocation at 0x2ea45 for "___get_hw_float" > ld: /usr/lib/libm.a(w_sinh.o): RRS text relocation at 0x2ea9c for "___ieee754_si > > It seems to build OK, but I don't recall seeing these in libm before? They should not be happening. It looks a lot like your system has lost its /usr/lib/libm.so.3.0. The Makefile for libtcl adds "-lm" to the command that builds the shared library. That's fine -- it just makes sure that libm is pulled in whenever the shared libtcl is used. But if your shared version of libm is missing or cannot be found, it will statically link in /usr/lib/libm.a instead. (Maybe it should refuse.) Since libm.a is not built PIC, you get the linker warnings. They probably won't prevent programs from working, but they're bad from an efficiency standpoint. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706212215.PAA08801>