>> On Tue, 21 Jan 1997 17:36:58 -0500 (EST),
>> Randall S Winchester(r) wrote:
r> On Fri, 17 Jan 1997, Eddy J. Gurney wrote:
r> : On Jan 17, 23:25, Albrecht Kadlec wrote:
r> :
r> : ....stuff deleted.
r> :
r> : Finally, something that needs to be fixed in Fvwm.tmpl: in order for
r> : the Solaris dynamic linker to find the X libraries, I needed to change
r> : the FvwmModuleTarget and FvwmProgramTarget from '$(CC) -o $_at_...' to
r> : '$(CCLINK) -o $_at_...'. This is very important! It makes sure the
r> : LD_LIBRARY_PATH gets set before the link so the dynamic linker can find
r> : the X libraries. Prior to making this change, 'fvwm2' would not run,
r> This is indeed a problem with CC=cc. It is also true with some versions of
r> gcc. I have just upgraded from gcc 2.7.0 which did not have this problem to
r> 2.7.2 which does as well as older gcc 2.6.*. In the gcc case it is not
r> LD_LIBRARY_PATH that gets set but rather LD_RUN_PATH, but the end result is
I see LD_RUN_PATH set as well. I always explicitly unset LD_LIBRARY_PATH
before any builds -- it seems to always lead to trouble
here. Solaris-2.5, cc-4.0, X11R6.3.
r> the same. Either of thses are supposed to get set to $(USRLIBDIR). In my
r> case this would be USRLIBDIR = /usr/local/X11R6/lib. Imake of corse thakes
r> care of this part.
This (use of CCLINK instead of CC) is a nice trick -- do older xmkmf's
generate this CCLINK as well?
Previously I was building with
make EXTRA_LDOPTIONS=-R/usr/local/X11R6/lib
which also works (but is more typing).
Thanks.
--
-mb-
--
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 Thu Jan 23 1997 - 10:49:28 GMT