Re: [Mimedefang] x64 compatible?
Here is what I have done to help diagnose. Completely reloaded the server just as before, tried to run mimedefang, and still getting seg fault. I don't know how to compile with debugging symbols. Here's the backtrace. Doesn't make any sense to me, I'm hoping it does to you. [EMAIL PROTECTED] x86_64]# mimedefang -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock -d Segmentation fault (core dumped) [EMAIL PROTECTED] x86_64]# gdb mimedefang core.21348 GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libnsl.so.1 Reading symbols from /lib64/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libnss_files.so.2... (no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `mimedefang -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock -d'. Program terminated with signal 11, Segmentation fault. #0 0x00407806 in ?? () (gdb) bt #0 0x00407806 in ?? () #1 0x4d2f6c6f6f70732f in ?? () #2 0x44454d494d2f6c6f in ?? () #3 0x696d2f676e616665 in ?? () #4 0x676e61666564656d in ?? () #5 0x642d006b636f732e in ?? () #6 0x4d414e54534f4800 in ?? () #7 0x30353932676d3d45 in ?? () #8 0x736365746c65642e in ?? () #9 0x736e6f6974756c6f in ?? () #10 0x524554006d6f632e in ?? () #11 0x006d726574783d4d in ?? () #12 0x622f3d4c4c454853 in ?? () #13 0x00687361622f6e69 in ?? () #14 0x455a495354534948 in ?? () #15 0x535300303030313d in ?? () #16 0x544e45494c435f48 in ?? () #17 0x2e3034312e34373d in ?? () #18 0x35312037392e3337 in ?? () #19 0x5353003232203535 in ?? () #20 0x642f3d5954545f48 in ?? () #21 0x312f7374702f7665 in ?? () #22 0x6f723d5245535500 in ?? () ---Type return to continue, or q return to quit--- #23 0x4f435f534c00746f in ?? () #24 0x3d6f6e3d53524f4c in ?? () #25 0x30303d69663a3030 in ?? () #26 0x333b30303d69643a in ?? () #27 0x3b30303d6e6c3a34 in ?? () #28 0x30343d69703a3633 in ?? () #29 0x303d6f733a3b in ?? () #30 0x3d64623a35333b30 in ?? () #31 0x31303b3b3034 in ?? () #32 0x333b30343d64633a in ?? () #33 0x3d726f3a31303b33 in ?? () #34 0x37333b35303b3130 in ?? () #35 0x303d696d3a31343b in ?? () #36 0x3b37333b35303b31 in ?? () #37 0x30303d78653a3134 in ?? () #38 0x6d632e2a3a32333b in ?? () #39 0x3a32333b30303d64 in ?? () #40 0x30303d6578652e2a in ?? () #41 0x6f632e2a3a32333b in ?? () #42 0x3a32333b30303d6d in ?? () #43 0x30303d6d74622e2a in ?? () #44 0x61622e2a3a32333b in ?? () #45 0x3a32333b30303d74 in ?? () ---Type return to continue, or q return to quit--- #46 0x3b30303d68732e2a in ?? () #47 0x6873632e2a3a3233 in ?? () #48 0x2a3a32333b30303d in ?? () #49 0x3b30303d7261742e in ?? () #50 0x7a67742e2a3a3133 in ?? () #51 0x2a3a31333b30303d in ?? () #52 0x3b30303d6a72612e in ?? () #53 0x7a61742e2a3a3133 in ?? () #54 0x2a3a31333b30303d in ?? () #55 0x3b30303d687a6c2e in ?? () #56 0x70697a2e2a3a3133 in ?? () #57 0x2a3a31333b30303d in ?? () #58 0x31333b30303d7a2e in ?? () #59 0x3b30303d5a2e2a3a in ?? () #60 0x3d7a672e2a3a3133 in ?? () #61 0x2e2a3a31333b3030 in ?? () #62 0x333b30303d327a62 in ?? () #63 0x303d7a622e2a3a31 in ?? () #64 0x742e2a3a31333b30 in ?? () #65 0x3a31333b30303d7a in ?? () #66 0x30303d6d70722e2a in ?? () #67 0x70632e2a3a31333b in ?? () #68 0x31333b30303d6f69 in ?? () ---Type return to continue, or q return to quit--- #69 0x303d67706a2e2a3a in ?? () #70 0x672e2a3a35333b30 in ?? () #71 0x35333b30303d6669 in ?? () #72 0x303d706d622e2a3a in ?? () #73 0x782e2a3a35333b30 in ?? () #74 0x35333b30303d6d62 in ?? () #75 0x303d6d70782e2a3a in ?? () #76 0x702e2a3a35333b30 in ?? () #77 0x35333b30303d676e in ?? () #78 0x303d6669742e2a3a in ?? () #79 0x414d003a35333b30 in ?? () #80 0x2f7261762f3d4c49 in ?? () #81 0x616d2f6c6f6f7073 in ?? () #82 0x00746f6f722f6c69 in ?? () #83 0x73752f3d48544150 in ?? () #84 0x72656272656b2f72 in ?? () #85 0x3a6e6962732f736f in ?? () #86 0x72656b2f7273752f in ?? () #87 0x69622f736f726562 in ?? () #88 0x6c2f7273752f3a6e in ?? () #89 0x6962732f6c61636f in ?? () #90 0x6c2f7273752f3a6e in ?? () #91 0x6e69622f6c61636f in ?? () ---Type return to continue, or q return to quit--- #92 0x2f3a6e6962732f3a in ?? () #93 0x7273752f3a6e6962 in ?? () #94
[Mimedefang] (no subject)
-- on Tue 11/14/2006 7:00 PM Kenneth Porter wrote: At this prompt, type bt to get a stack backtrace which should show the routine where the crash happened. Make sure you built MD with debugging information so that actual routine names will be displayed. This backtrace actually has an error in it. Cannot access memory at address 0x7fff02c0cffd Does this help? Still don't know how to compile with debugging. When I build the RPM, it makes a mimedefang-2.58.1.x86_64.rpm and a mimedefang-debuginfo-2.58.1.x86_64.rpm file. I install them both, but still only get what is listed below. [EMAIL PROTECTED] ~]# /usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMEDefang/mimedefang-multiplexor.sock -R -1 -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock Segmentation fault (core dumped) [EMAIL PROTECTED] ~]# ls anaconda-ks.cfg Desktop Mail-SpamAssassin-3.1.7.tar.gz clamav-0.88.6.tar.gz install.log mimedefang-2.58.tar.gz core.21429install.log.syslog [EMAIL PROTECTED] ~]# gdb mimedefang core.21429 GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libnsl.so.1 Reading symbols from /lib64/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libnss_files.so.2... (no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMED'. Program terminated with signal 11, Segmentation fault. #0 0x00407806 in ?? () (gdb) bt #0 0x00407806 in ?? () #1 0x4d2f6c6f6f70732f in ?? () #2 0x44454d494d2f6c6f in ?? () #3 0x696d2f676e616665 in ?? () #4 0x676e61666564656d in ?? () #5 0x4f48006b636f732e in ?? () #6 0x6d3d454d414e5453 in ?? () #7 0x65642e3035393267 in ?? () #8 0x756c6f736365746c in ?? () #9 0x6f632e736e6f6974 in ?? () #10 0x783d4d524554006d in ?? () #11 0x454853006d726574 in ?? () #12 0x2f6e69622f3d4c4c in ?? () #13 0x5349480068736162 in ?? () #14 0x30313d455a495354 in ?? () #15 0x435f485353003030 in ?? () #16 0x34373d544e45494c in ?? () #17 0x2e33372e3034312e in ?? () #18 0x2035353531203739 in ?? () #19 0x545f485353003232 in ?? () #20 0x2f7665642f3d5954 in ?? () #21 0x535500312f737470 in ?? () #22 0x00746f6f723d5245 in ?? () ---Type return to continue, or q return to quit--- #23 0x524f4c4f435f534c in ?? () #24 0x3a30303d6f6e3d53 in ?? () #25 0x69643a30303d6966 in ?? () #26 0x6c3a34333b30303d in ?? () #27 0x3a36333b30303d6e in ?? () #28 0x3b30343d6970 in ?? () #29 0x333b30303d6f733a in ?? () #30 0x3b30343d64623a35 in ?? () #31 0x64633a31303b in ?? () #32 0x303b3b30343d in ?? () #33 0x3b31303d726f3a31 in ?? () #34 0x31343b37333b3530 in ?? () #35 0x303b31303d696d3a in ?? () #36 0x3a31343b37333b35 in ?? () #37 0x32333b30303d7865 in ?? () #38 0x303d646d632e2a3a in ?? () #39 0x652e2a3a32333b30 in ?? () #40 0x32333b30303d6578 in ?? () #41 0x303d6d6f632e2a3a in ?? () #42 0x622e2a3a32333b30 in ?? () #43 0x32333b30303d6d74 in ?? () #44 0x303d7461622e2a3a in ?? () #45 0x732e2a3a32333b30 in ?? () ---Type return to continue, or q return to quit--- #46 0x3a32333b30303d68 in ?? () #47 0x30303d6873632e2a in ?? () #48 0x61742e2a3a32333b in ?? () #49 0x3a31333b30303d72 in ?? () #50 0x30303d7a67742e2a in ?? () #51 0x72612e2a3a31333b in ?? () #52 0x3a31333b30303d6a in ?? () #53 0x30303d7a61742e2a in ?? () #54 0x7a6c2e2a3a31333b in ?? () #55 0x3a31333b30303d68 in ?? () #56 0x30303d70697a2e2a in ?? () #57 0x3d7a2e2a3a31333b in ?? () #58 0x2e2a3a31333b3030 in ?? () #59 0x3a31333b30303d5a in ?? () #60 0x3b30303d7a672e2a in ?? () #61 0x327a622e2a3a3133 in ?? () #62 0x2a3a31333b30303d in ?? () #63 0x333b30303d7a622e in ?? () #64 0x303d7a742e2a3a31 in ?? () #65 0x722e2a3a31333b30 in ?? () #66 0x31333b30303d6d70 in ?? () #67 0x3d6f6970632e2a3a in ?? () #68 0x2e2a3a31333b3030 in ?? () ---Type return to continue, or q return to quit--- #69 0x333b30303d67706a in ?? () #70 0x3d6669672e2a3a35 in ?? () #71 0x2e2a3a35333b3030 in ?? () #72 0x333b30303d706d62 in ?? () #73 0x3d6d62782e2a3a35 in ?? () #74 0x2e2a3a35333b3030 in ?? () #75 0x333b30303d6d7078 in ?? () #76
Re: [Mimedefang] x64 compatible?
-- on Tue 11/14/2006 7:00 PM Kenneth Porter wrote: At this prompt, type bt to get a stack backtrace which should show the routine where the crash happened. Make sure you built MD with debugging information so that actual routine names will be displayed. This backtrace actually has an error in it. Cannot access memory at address 0x7fff02c0cffd Does this help? Still don't know how to compile with debugging. When I build the RPM, it makes a mimedefang-2.58.1.x86_64.rpm and a mimedefang-debuginfo-2.58.1.x86_64.rpm file. I install them both, but still only get what is listed below. [EMAIL PROTECTED] ~]# /usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMEDefang/mimedefang-multiplexor.sock -R -1 -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock Segmentation fault (core dumped) [EMAIL PROTECTED] ~]# ls anaconda-ks.cfg Desktop Mail-SpamAssassin-3.1.7.tar.gz clamav-0.88.6.tar.gz install.log mimedefang-2.58.tar.gz core.21429install.log.syslog [EMAIL PROTECTED] ~]# gdb mimedefang core.21429 GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libnsl.so.1 Reading symbols from /lib64/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libnss_files.so.2... (no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMED'. Program terminated with signal 11, Segmentation fault. #0 0x00407806 in ?? () (gdb) bt #0 0x00407806 in ?? () #1 0x4d2f6c6f6f70732f in ?? () #2 0x44454d494d2f6c6f in ?? () #3 0x696d2f676e616665 in ?? () #4 0x676e61666564656d in ?? () #5 0x4f48006b636f732e in ?? () #6 0x6d3d454d414e5453 in ?? () #7 0x65642e3035393267 in ?? () #8 0x756c6f736365746c in ?? () #9 0x6f632e736e6f6974 in ?? () #10 0x783d4d524554006d in ?? () #11 0x454853006d726574 in ?? () #12 0x2f6e69622f3d4c4c in ?? () #13 0x5349480068736162 in ?? () #14 0x30313d455a495354 in ?? () #15 0x435f485353003030 in ?? () #16 0x34373d544e45494c in ?? () #17 0x2e33372e3034312e in ?? () #18 0x2035353531203739 in ?? () #19 0x545f485353003232 in ?? () #20 0x2f7665642f3d5954 in ?? () #21 0x535500312f737470 in ?? () #22 0x00746f6f723d5245 in ?? () ---Type return to continue, or q return to quit--- #23 0x524f4c4f435f534c in ?? () #24 0x3a30303d6f6e3d53 in ?? () #25 0x69643a30303d6966 in ?? () #26 0x6c3a34333b30303d in ?? () #27 0x3a36333b30303d6e in ?? () #28 0x3b30343d6970 in ?? () #29 0x333b30303d6f733a in ?? () #30 0x3b30343d64623a35 in ?? () #31 0x64633a31303b in ?? () #32 0x303b3b30343d in ?? () #33 0x3b31303d726f3a31 in ?? () #34 0x31343b37333b3530 in ?? () #35 0x303b31303d696d3a in ?? () #36 0x3a31343b37333b35 in ?? () #37 0x32333b30303d7865 in ?? () #38 0x303d646d632e2a3a in ?? () #39 0x652e2a3a32333b30 in ?? () #40 0x32333b30303d6578 in ?? () #41 0x303d6d6f632e2a3a in ?? () #42 0x622e2a3a32333b30 in ?? () #43 0x32333b30303d6d74 in ?? () #44 0x303d7461622e2a3a in ?? () #45 0x732e2a3a32333b30 in ?? () ---Type return to continue, or q return to quit--- #46 0x3a32333b30303d68 in ?? () #47 0x30303d6873632e2a in ?? () #48 0x61742e2a3a32333b in ?? () #49 0x3a31333b30303d72 in ?? () #50 0x30303d7a67742e2a in ?? () #51 0x72612e2a3a31333b in ?? () #52 0x3a31333b30303d6a in ?? () #53 0x30303d7a61742e2a in ?? () #54 0x7a6c2e2a3a31333b in ?? () #55 0x3a31333b30303d68 in ?? () #56 0x30303d70697a2e2a in ?? () #57 0x3d7a2e2a3a31333b in ?? () #58 0x2e2a3a31333b3030 in ?? () #59 0x3a31333b30303d5a in ?? () #60 0x3b30303d7a672e2a in ?? () #61 0x327a622e2a3a3133 in ?? () #62 0x2a3a31333b30303d in ?? () #63 0x333b30303d7a622e in ?? () #64 0x303d7a742e2a3a31 in ?? () #65 0x722e2a3a31333b30 in ?? () #66 0x31333b30303d6d70 in ?? () #67 0x3d6f6970632e2a3a in ?? () #68 0x2e2a3a31333b3030 in ?? () ---Type return to continue, or q return to quit--- #69 0x333b30303d67706a in ?? () #70 0x3d6669672e2a3a35 in ?? () #71 0x2e2a3a35333b3030 in ?? () #72 0x333b30303d706d62 in ?? () #73 0x3d6d62782e2a3a35 in ?? () #74 0x2e2a3a35333b3030 in ?? () #75 0x333b30303d6d7078 in ?? () #76
[Mimedefang] rDNS weirdness in MdF
I'm seeing the following in my logs:
Nov 19 11:49:39 mail mimedefang.pl[11501]: no rDNS: reject [207.220.83.13]
Nov 19 11:49:39 mail mimedefang.pl[11501]: filter_relay tempfailed host
207.220.83.13 ([207.220.83.13])
Nov 19 11:49:39 mail sendmail[15385]: kAJInd3l015385: Milter: connect:
host=host13.mainsequence.net, addr=207.220.83.13, temp failing commands
which I don't understand. This means that:
sub filter_relay($$) {
my ($hostip, $hostname) = @_;
...
# we have to tempfail, since we might not be able to rDNS
# because of transient non-authoritative server failures.
# we could get more sophisticated and look at the exact failure
# reason... this might offer a clue as to whether we can REJECT
# or simply TEMPFAIL. we TEMPFAIL because of a bug in Bind
# involving TTL's less than 600 seconds.
if ($hostname eq [$hostip]) {
md_syslog('info', no rDNS: reject [$hostip]);
return ('TEMPFAIL', No rDNS records found);
}
...
got triggered in my mimedefang-filter code.
So, the obvious question is, why is Sendmail able to resolve the
IP address but MdF can't?
I've set up my sendmail.cf as:
# name resolver options
O ResolverOptions=+AAONLY -DNSRCH -DEFNAMES
but this shouldn't be making a difference (since these affect
name-to-address lookups only).
(And is there direct access to h_errno? It would be nice if
the functions that call gethostby*() exported the value of $?
in a global variable like $h_errno...)
What am I missing here?
Thanks,
-Philip
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] (no subject)
Two things: first, you might need to tell gdb where to look for the symbol file, with the file command or with an extra argument from the shell when you start it up. second: your stack is corrupt. From #1 onwards, all of these are dumps are pointing into text... Not stack. If you decode the hex, you'll find that it is either string table or symbol table. Picking a random entry, like #23, we get: ROLOC_SL which came out of your string table I'm guessing. How big was this process before it died? I just looked at mimedefang-debuginfo-2.57-1.x86_64.rpm on my system, and it was empty. Odd. No files. David? -Philip [EMAIL PROTECTED] wrote: -- on Tue 11/14/2006 7:00 PM Kenneth Porter wrote: [snip] Still don't know how to compile with debugging. When I build the RPM, it makes a mimedefang-2.58.1.x86_64.rpm and a mimedefang-debuginfo-2.58.1.x86_64.rpm file. I install them both, but still only get what is listed below. [EMAIL PROTECTED] ~]# /usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMEDefang/mimedefang-multiplexor.sock -R -1 -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock Segmentation fault (core dumped) [EMAIL PROTECTED] ~]# ls anaconda-ks.cfg Desktop Mail-SpamAssassin-3.1.7.tar.gz clamav-0.88.6.tar.gz install.log mimedefang-2.58.tar.gz core.21429install.log.syslog [EMAIL PROTECTED] ~]# gdb mimedefang core.21429 GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib64/libthread_db.so.1. [snip] Core was generated by `/usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m /var/spool/MIMED'. Program terminated with signal 11, Segmentation fault. #0 0x00407806 in ?? () (gdb) bt #0 0x00407806 in ?? () #1 0x4d2f6c6f6f70732f in ?? () [snip] #23 0x524f4c4f435f534c in ?? () [snip] ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] x64 compatible?
On 11/19/2006 08:57, [EMAIL PROTECTED] wrote: Still don't know how to compile with debugging. Usually there's an option in the ./Configure script that turns it on. If there's no ./Configure, then look at the Makefile and check for the CFLAGS and CXXFLAGS vars which contain flags that get passed to the C and C++ (respectively) compilers. You want to look for or add -g in there to get passed to gcc. Some (but not all) ./Configure scripts look for the $CFLAGS and $CXXFLAGS environment variable. This can throw a wrench into your efforts depending on how things are. If things are buggy, the Makefile (or rpm) can do things like running the strip program on your fresh binaries. This action can remove the debugging symbols you worked so hard to add in the first place. Just things to look for... ~Jason -- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] More on mimedefang and x86_64
Hmmm... I run sendmail/cyrus-imapd/spamassassin/mimedefang on an x86_64 machine (FC5 on an Athalon64 2800+) and it works fine. To keep the mail server simple, however, I wanted to build mimedefang-2.58 on a different machine, so I went ahead and grabbed all of the dependencies. I have to say, I was a bit configured. It seems that the build-time dependencies have been muddled with the run-time dependencies. You don't need: BuildRequires: perl-Digest-SHA1 perl-MIME-tools perl-IO-stringy perl-MailTools in the .spec file, do you? Can we yank this? I just pulled it out and things built fine (oh, after adding --disable-check-perl-modules to the ./configure line). Further, if you install sendmail-devel but don't actually have sendmail installed on the machine (since your building, but not actually running)... then you might run afoul of the following scenario. sendmail-devel installs (on an x86_64 architecture) /usr/lib64/libmilter.a only. So, from configure.in: AC_PATH_PROG(LIBMILTER, libmilter.a, no, $MILTERLIB:$SMPATH:/usr/local/lib:/lib:/usr/lib:/usr/lib/libmilter) SMPATH=`echo ../sendmail-*/obj.*/libsm` AC_PATH_PROG(LIBSM, libsm.a, no, $SMPATH:/usr/local/lib:/lib:/usr/lib:/usr/lib/libmilter) dnl find libmilter.so in case we have shared libraries AC_PATH_PROG(LIBMILTERSO, libmilter.so, no, $MILTERLIB:$SMPATH:/usr/local/lib:/lib:/usr/lib:/usr/lib/libmilter) should we add /lib64 and /usr/lib64 before /lib and /usr/lib, respectively? I changed the .spec file to include: ./configure ... --with-libmilter=/usr/lib64 ... and it seems to build... but it might make more sense to fix this in the configure.in file instead, as above. Opinions? Oh, and do we need the symbol file for /usr/bin/mimedefang to put into mimedefang-debuginfo-2.58? -Philip ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] More on mimedefang and x86_64
Philip Prindeville wrote: I have to say, I was a bit configured. It seems that the build-time dependencies have been muddled with the run-time dependencies. Grrr... dropping big chunks of text. a bit confused on how it's configured. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
