similar to: dovecot2 beta and gcc3(?) - compile problem

Displaying 20 results from an estimated 3000 matches similar to: "dovecot2 beta and gcc3(?) - compile problem"

2010 Sep 16
2
Dovecot2 and mdbox problem
Hello, I've just installed Dovecot from the http://xi.rename-it.nl/debian/ repository. But I have a problem with the mdbox Format. When the home folder is empty Dovecot should create the folder structure if the first mail arrived or the user logs in the first time. But I get following error: Sep 16 12:30:41 smtp dovecot: lmtp(31244): Connect from local Sep 16 12:30:41 smtp dovecot:
2008 Jun 19
4
v1.1.rc12 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz.sig Sorry, one more RC because of the mbox+quota bug. v1.1.0 still planned for tomorrow. - mbox: Don't give "Can't find next message offset" warnings when plugin (e.g. quota) accesses the message being saved. - deliver: Settings inside protocol imap {}
2008 Jun 19
4
v1.1.rc12 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz.sig Sorry, one more RC because of the mbox+quota bug. v1.1.0 still planned for tomorrow. - mbox: Don't give "Can't find next message offset" warnings when plugin (e.g. quota) accesses the message being saved. - deliver: Settings inside protocol imap {}
2006 Nov 05
2
1.0.rc12 released
http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz.sig Since rc11 has problems compiling with BSDs, here's a new release. Just two changes: - rc11 didn't compile with some compilers - default_mail_env fallbacking was broken with --exec-mail Here's also again the rc11 changes: * Renamed default_mail_env to mail_location.
2006 Nov 05
2
1.0.rc12 released
http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz.sig Since rc11 has problems compiling with BSDs, here's a new release. Just two changes: - rc11 didn't compile with some compilers - default_mail_env fallbacking was broken with --exec-mail Here's also again the rc11 changes: * Renamed default_mail_env to mail_location.
2008 Sep 17
2
[LLVMdev] bc file only with llvm-gcc3?
question about: http://llvm.org/docs/FAQ.html#translatec++ "With llvm-gcc3, this will generate program and program.bc." Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? I have 'llvm-g++ (GCC) 4.2.1 (Based on Apple Inc. build 5546) (LLVM build)' installed on Ubuntu and followed that guide and it creates indeed no .bc file. Regards, -mr
2008 May 03
1
Replication milestone 1
5 milestones planned currently. I'll start with the always-on multi-master replication, because that's the most difficult one to get working correctly and efficiently. So if during its implementation I find some design problems, less code needs to be fixed. Milestone 0 will hopefully be done within a month. This includes reading and replying to the rest of the mails on this list and
2006 Dec 04
0
[LLVMdev] Dropping support for llvm-gcc3
LLVMers, This doesn't affect release 1.X users, only those using the LLVM current (CVS head) version. With recent changes, the current version of LLVM will no longer read old assembly or bytecode files. The upgrade path from 1.X to 2.0 is now provided by the new llvm-upgrade tool. See: http://llvm.org/docs/CommandGuide/html/llvm-upgrade.html for details on how to use this command.
2008 Sep 17
0
[LLVMdev] bc file only with llvm-gcc3?
On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach <michael_reichenbach at freenet.de> wrote: > question about: > http://llvm.org/docs/FAQ.html#translatec++ > "With llvm-gcc3, this will generate program and program.bc." > > Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? Those instructions are out of date; the current version of llvm-gcc
2004 Aug 06
1
Possibly solved: Re: Does Ices need GCC3? Was: Re: Trouble running IceS
On Sunday 28 July 2002 02:06 am, you wrote: > On Sunday 28 July 2002 01:30 am, you wrote: > > Whenever I try to run it (ices)I get errors: > > > > cadmium:/work/dl/Audio/streaming/ices-0.2.3 # /usr/local/icecast/bin/ices > > --help /usr/local/icecast/bin/ices: error while loading shared libraries: > > libgcc_s.so.1: cannot open shared object file: No such file or
2010 Jun 27
1
Compile error sieve plugin for dovecot2
Hello, I'm trying to compile the sieve plugin for dovecot2 Dovecot2-beta6 is allready running and working. i did a hg clone http://hg.renamie-it.nl/dovecot-2.0-pigeonhole and ran the autogen.sh script as mentioned in the INSTALL file configure options: /configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-dovecot=/usr/lib/dovecot/ --with-managesieve=no compiling gives an
2016 Jul 07
3
Compile error Dovecot2-pigeonhole
FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in
2009 Mar 25
2
v1.2.beta4 released
http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there
2009 Mar 25
2
v1.2.beta4 released
http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there
2013 Aug 21
0
dovecot2, antispam and sieve versions
I'm currently running dovecot2 v2.2.5 with dovecot2-antispam 0.0-51 and dovecot2-sieve 0.4.1, all via macports. If one wanted to downgrade to dovecot v2.2.0, would these versions of antispam and sieve still be okay to use? The reason for the question is I'm trying to diagnose a mailserver problem where after 2-6 days the machine goes deaf. Absolutely nothing of interest in any logfile
2014 Jan 31
2
Dovecot2 + Quota
Hello! I need to configure Quota on Roundcubemail with Dovecot2. So, I did: 90-quota.conf: # SQL backend: quota = dict:User quota::proxy::sqlquota quota_rule = *:storage=20M:messages=1000 } dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } OK, works! but, My webmail shows me 20M of quota. But on my Postfixadmin I configured 200M. How can I fix this? Att; *Lucas
2008 Sep 17
2
[LLVMdev] bc file only with llvm-gcc3?
Eli Friedman schrieb: > On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach > <michael_reichenbach at freenet.de> wrote: >> question about: >> http://llvm.org/docs/FAQ.html#translatec++ >> "With llvm-gcc3, this will generate program and program.bc." >> >> Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? > > Those
2010 Jun 22
1
imap acl write tb3 plugin dovecot2 vs XMAILBOXINFO
Hi Timo, i played a little bit with an experimental tb3 imap acl write extension https://addons.mozilla.org/de/thunderbird/addon/176736/ with dovecot2 got errors like XMAILBOXINFO: Unknown command any idea? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
2011 May 09
1
Post-login scripting with mail_drop_priv_before_exec in dovecot2
Hi, I'm in the process of upgrading from dovecot v1.1 to dovecot 2. We fetch uid/gid user information from a database and also use post-login scripting with mail_drop_priv_before_exec = yes which means the postlogin script is executed with the permissions of the user we have found in the database. According to the dovecot2 wiki page, to get this behaviour in version 2 we have to set the
2010 May 31
1
master users with dovecot2 braek down to allowed domain
Hi, i think ive asked it before perhaps this feature can be included in dovecot2 couldnt get it run with dovecot 1.2.x if i use the postfixadmin superuser,domainadmin,domainuser layout so there are domainadmins defined in a sql table it would be a nice feature to break it down to be master only at there related domains via sql lookup at recent i think there is only the chance to give master