The following bug has been RESOLVED. ====================================================================== http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000138 ====================================================================== Reported By: xing Assigned To: aaron ====================================================================== Project: DBMail Bug ID: 138 Category: installation scripts Reproducibility: always Severity: minor Priority: normal Status: resolved Resolution: fixed ====================================================================== Date Submitted: 11-Dec-04 23:49 CET Last Modified: 09-Jan-05 10:19 CET ====================================================================== Summary: suggestions regarding binary location Description: As of 2.0.1, dbmail-smtp, imapd, and pop3d binaries are located in /usr/local/sbin/.libs/* folder by default.
This makes them harder to locate, less transparent, to the average admin. I think it's also a misnomer to put them in a libs directory when they are not libs. How about just creating a non-hidden dbmail-bin folder within /usr/local/sbin to put them in? This would accomplish the same task and improve transparency. ====================================================================== ---------------------------------------------------------------------- aaron - 12-Dec-04 00:21 CET ---------------------------------------------------------------------- You're very generous in making such reasonable suggestions of how to fix this libtool problem. The better question is how we managed to get our libtool so badly fucked up! This is definitely a very high priority problem. Few things we need to know: - What platform are you on? - What steps are required to reproduce this installation? - Did you rebuild the autotools stuff? - If so, what versions of the various autotools were you using? ---------------------------------------------------------------------- xing - 12-Dec-04 01:07 CET ---------------------------------------------------------------------- oops..had no idea this is the same problem with the missing lib config 1)Platform: Fedora 2 (fully update with up2date) 2) Steps: ./configure --with-mysql, make, make install 3) Rebuild autotools?: I didn't recompile/rebuild any of the Fedora's build tools. 4) Here are the installed packages: Packages: autoconf-2.59-3 automake16-1.6.3-2 automake14-1.4p6-9 automake17-1.7.9-2 automake15-1.5-10 autofs-4.1.2-2 automake-1.8.3-1 libtool-libs-1.5.6-1 libtool-1.5.6-1 ---------------------------------------------------------------------- paul - 12-Dec-04 09:37 CET ---------------------------------------------------------------------- Try running configure --with-mysql --prefix=/usr ---------------------------------------------------------------------- xing - 12-Dec-04 09:46 CET ---------------------------------------------------------------------- Paul's suggestion of adding --prefix=/usr fixed the problem. =) I first ran without the prefix addition to make sure the problem can be duplicated, and it did, and try the prefix fix which resolved the bug. ---------------------------------------------------------------------- paul - 27-Dec-04 11:02 CET ---------------------------------------------------------------------- This bug should probably be cancelled. Binaries *are* installed in /usr/local/sbin by default. Installation in .libs indicates a problem with libtool on xing's system. ---------------------------------------------------------------------- paul - 30-Dec-04 10:03 CET ---------------------------------------------------------------------- This bug seems serious, but independant confirmation of other fedora users is necessary. ---------------------------------------------------------------------- xing - 02-Jan-05 11:53 CET ---------------------------------------------------------------------- I just re-tested the scenario in a different machine with also Fedora 2 fully updated with the same autoconf, automake, libtools packages and did NOT encounter the same error, or any error for that matter. Guess this "bug" note should be closed. Perhaps while compiling some packages on the other machine corrupted/overwrote some ENV variables used by the build system? Who knows but this could not be reproduced on another Fedora 2 system. ---------------------------------------------------------------------- aaron - 09-Jan-05 10:19 CET ---------------------------------------------------------------------- Looks like it was a wild bug in one Fedora Core 2 system and not replicable. If someone finds this happening elsewhere, please reopen the bug with a test case! Bug History Date Modified Username Field Change ====================================================================== 11-Dec-04 23:49xing New Bug 12-Dec-04 00:21aaron Bugnote Added: 0000438 12-Dec-04 01:07xing Bugnote Added: 0000440 12-Dec-04 09:37paul Bugnote Added: 0000442 12-Dec-04 09:46xing Bugnote Added: 0000443 27-Dec-04 11:02paul Bugnote Added: 0000464 30-Dec-04 10:03paul Bugnote Added: 0000478 30-Dec-04 10:03paul platform => fedora2 30-Dec-04 10:03paul Projection none => tweak 30-Dec-04 10:03paul Status new => acknowledged 02-Jan-05 11:53xing Bugnote Added: 0000483 09-Jan-05 10:19aaron Bugnote Added: 0000495 09-Jan-05 10:19aaron Assigned To => aaron 09-Jan-05 10:19aaron Resolution open => fixed 09-Jan-05 10:19aaron Status acknowledged => resolved ======================================================================
