After submitting a bug report to the web interface at www.fvwm.org (as
"guest"), I received the attached bounce message reporting that
<[EMAIL PROTECTED]> is undeliverable.
The "incoming" directory in the bug tracking system doesn't appear to
have any new entries since 05 Apr 2002.
Is this a known problem?
--
Dan Astoorian People shouldn't think that it's better to have
Sysadmin, CSLab loved and lost than never loved at all. It's
[EMAIL PROTECTED] not, it's better to have loved and won. All
www.cs.toronto.edu/~djast/ the other options really suck. --Dan Redican
--- Begin Message ---
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>:
host util2.math.uh.edu [129.7.128.23]: 550 unknown user
------ This is a copy of the message, including all the headers. ------
Return-path: <[EMAIL PROTECTED]>
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 17CnqU-0000sg-00
for [EMAIL PROTECTED]; Tue, 28 May 2002 15:45:30 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: configure --with-xpm-library under Solaris link problem
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 28 May 2002 15:45:30 -0500
Full_Name: Dan Astoorian
Version: 2.4.7
CVS_Date:
OS: SunOS 5.8
X_Server: SUNWxwplt
Submission from: (NULL) (128.100.2.38)
When the configure script compiles the test program for XPM support, it
inserts a -L option for the directory specified by the --with-xpm-library
option. However, if libXpm is a shared object, and is not in the
standard library path, the test program will be unable to locate the
shared object at runtime.
Under SunOS 5.x (Solaris), the library path needs to be declared with -R
options in addition to -L . This is done for, e.g., $x_libraries, but not
for $xpm_LIBS .
Please note that setting LD_LIBRARY_PATH is not an acceptable solution.
(See http://www.visi.com/~barr/ldpath.html for a list of reasons why.)
This doesn't appear to have been fixed in the current version, 2.5.1.
--- End Message ---
