[Dovecot] ./configure dovecot
When I do a ./configure in dovecot (2.2.1) I get this notice (first line):
configure: WARNING: you should use --build, --host, --target
Then, much later on:
checking sys/ucred.h presence... yes configure: WARNING: sys/ucred.h: present but cannot be compiled configure: WARNING: sys/ucred.h: check for missing prerequisite headers? configure: WARNING: sys/ucred.h: see the Autoconf documentation configure: WARNING: sys/ucred.h: section "Present But Cannot Be Compiled" configure: WARNING: sys/ucred.h: proceeding with the compiler's result configure: WARNING: ## ---------------------------------- ## configure: WARNING: ## Report this to dovecot@dovecot.org ## configure: WARNING: ## ---------------------------------- ## checking for sys/ucred.h... no
at the end I get:
configure: creating ./config.status
Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : kqueue I/O notifys .... : kqueue SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file pam checkpassword : -shadow -bsdauth -sia -ldap -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword nss : -ldap -sql -vpopmail SQL drivers .... : : -pgsql -mysql -sqlite Full text search : squat : -lucene -solr
but there is no makefile created.
./configure --help just runs the configure script again, and none of --build --host or --target have any effect on the errors shown, including the first line error.
So I think, ok, fine, I'll grab the latest build (2.2.4).
Same result.
OK, fine. Let's look at 1.2.17.
Same thing, only without the cured.h warning. Still the same error on the first line after ./configure and still no make file.
There's no big flashing warning anywhere that I can see that says, "Hey, dummy, this isn't going to work."
config.log even ends with a "configure: exit 0"
(The system already has dovecot 1.2.17 installed, but I was looking at installing $LATEST).
-- May you live in interesting times
On Fri, 2 Aug 2013 04:38:25 -0600 LuKreme articulated:
When I do a ./configure in dovecot (2.2.1) I get this notice (first line):
configure: WARNING: you should use --build, --host, --target
{snip}
What OS and version are you attempting this on?
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On 02 Aug 2013, at 05:52 , Jerry jerry@seibercom.net wrote:
What OS and version are you attempting this on?
FreeBSD 6.3-RELEASE
-- Gehm's Corollary to Clarke's law: Any technology distinguishable from magic is insufficiently advanced.
On Fri, 2 Aug 2013 11:57:06 -0600 LuKreme articulated:
FreeBSD 6.3-RELEASE
That version is not even supported anymore.
Did you try to install Dovecot via the ports system?
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On 02 Aug 2013, at 16:02 , Jerry jerry@seibercom.net wrote:
On Fri, 2 Aug 2013 11:57:06 -0600 LuKreme articulated:
FreeBSD 6.3-RELEASE
- That version is not even supported anymore.
True, but it is what it is, and it was supported when 1.2.17 was current.
- Did you try to install Dovecot via the ports system?
That is how it was originally installed, I believe (there is a dovecot binary of 1.2.17 installed, but seems to be missing many other needed files).
I am trying to get permission to move the server to at least FreeBSD8, but I've been trying to get that for ... years.
-- "There will always be women in rubber flirting with me."
On Fri, 2 Aug 2013 21:45:33 -0600 LuKreme articulated:
On 02 Aug 2013, at 16:02 , Jerry jerry@seibercom.net wrote:
On Fri, 2 Aug 2013 11:57:06 -0600 LuKreme articulated:
FreeBSD 6.3-RELEASE
- That version is not even supported anymore.
True, but it is what it is, and it was supported when 1.2.17 was current.
- Did you try to install Dovecot via the ports system?
That is how it was originally installed, I believe (there is a dovecot binary of 1.2.17 installed, but seems to be missing many other needed files).
I am trying to get permission to move the server to at least FreeBSD8, but I've been trying to get that for ... years.
Both dovecot-1.2.17 and dovecot-2.2.4 are available in the ports. If you feel something is wrong with the version you have installed, and you have not demonstrated that yet, simply do a deinstall & reinstall of the port or use a port management program to force a reinstall of the port.
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On 02 Aug 2013, at 23:50 , Jerry jerry@seibercom.net wrote:
If you feel something is wrong with the version you have installed, and you have not demonstrated that yet,
From reading on how to setup dovecot with postfix there should be a /etc/dovecot/conf.d/ or /usr/local/etc/dovecot/conf.d/ folder with 10-auth.conf and 10-master.conf files. It appears to be missing.
simply do a deinstall & reinstall of the port or use a port management program to force a reinstall of the port.
Yes, if I could do that I would have.
-- YOU [humans] NEED TO BELIEVE IN THINGS THAT AREN'T TRUE. HOW ELSE CAN THEY BECOME? --Hogfather
On Sat, 3 Aug 2013 10:19:36 -0600 LuKreme articulated:
On 02 Aug 2013, at 23:50 , Jerry jerry@seibercom.net wrote:
If you feel something is wrong with the version you have installed, and you have not demonstrated that yet,
From reading on how to setup dovecot with postfix there should be a /etc/dovecot/conf.d/ or /usr/local/etc/dovecot/conf.d/ folder with 10-auth.conf and 10-master.conf files. It appears to be missing.
I many be wrong; however, I believe that is only for 2.x versions of Dovecot. You are on version 1.x I believe.
simply do a deinstall & reinstall of the port or use a port management program to force a reinstall of the port.
Yes, if I could do that I would have.
Something like: "portupgrade -Cfev mail/dovecot" should do it. You could eliminate the "C" flag if you are sure everything is configured correctly. I would insure that you have updated your ports list and updated your other programs first thought.
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On Fri, 2 Aug 2013 21:45:33 -0600 LuKreme articulated:
I am trying to get permission to move the server to at least FreeBSD8, but I've been trying to get that for ... years.
8.x is okay, but 9.x sucks. I would wait until the 10.x version is released. By that time they should have gotten the "clang" problems ironed out as well as those pesky "package" problems. I am still on 8.3 myself. In any case, I would strongly recommend that you do a fresh install. Format the disk and start over. I hear horror stories about left over crap from a previous installation that causes massive headaches. Besides, it gives you a good excuse to update your applications, like Dovecot.
Just my 2¢
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On 03 Aug 2013, at 08:12 , Jerry jerry@seibercom.net wrote:
8.x is okay, but 9.x sucks.
Much like Windows, it seems best to avoid the alternate numbered versions, although for windows you want the ODD and for FreeBSD you want the even. I don't recall anyone singing the praises for FreeBSD 7.
:)
-- When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is probably wrong.
participants (2)
-
Jerry
-
LuKreme