FVWM Bug Tracking notification

new message incoming/771

Message summary for PR#771
        From: [EMAIL PROTECTED]
        Subject: configure check for xpm version
        Date: Tue, 04 Sep 2001 07:29:16 -0500
        0 replies       0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From [EMAIL PROTECTED] Tue Sep 04 07:29:17 2001
Received: from karazm.math.uh.edu ([129.7.128.1])
        by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
        id 15eFKP-0008QE-00
        for [EMAIL PROTECTED]; Tue, 04 Sep 2001 07:29:17 -0500
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
        by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id HAA06243
        for <[EMAIL PROTECTED]>; Tue, 4 Sep 2001 07:29:16 -0500 (CDT)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
        by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
        id 15eFKO-0008QA-00
        for [EMAIL PROTECTED]; Tue, 04 Sep 2001 07:29:16 -0500
To: [EMAIL PROTECTED]
Subject: configure check for xpm version
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 04 Sep 2001 07:29:16 -0500

Full_Name: Richard Curnow
Version: 2.4.0
CVS_Date: 
OS: 
X_Server: MIT X11R6
Submission from: (NULL) (164.129.1.38)


When the check for Xpm version >=3.4g is done, I initially got a failure
even though I have 3.4k installed.
I am specifying both --with-xpm-includes and --with-xpm-library.
I tracked the problem down to the following.  In the gcc line used to do
this check, the order of the -L arguments needs changing, so that the
directory provided by --with-xpm-library overrides the directory where
libX11 etc are.  (i.e. in line 2481 of configure, the xpm_LIBS and X_LIBS
fields need swapping.  Then, if a newer version of xpm is installed in a
non-standard place, and it occludes an obsolete version in the X11
installation, it will be picked up correctly.



--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to