More on RedHat 8.0, Cyrus compile problems

Luke Johnson luke-list at rushmore.com
Thu Oct 3 13:54:36 EDT 2002


So... How about some free advice then... :)

In the List's opinion... starting from scratch, which is better (for a 
production server)...

RH8.0/gcc3.x and CVS cyrus packages
or
RH7.3/gcc2.x and stable cyrus-imapd-2.1.9/cyrus-sasl-2.1.7

Will gcc3.x be the 'new, have to have thing' and handy for possible 
future cyrus upgrades, or for a production server is predictabilty of 
gcc2.x and the stable packages more important?

Also, this dove-tails into the start of this thread about known RH7.3 
versus a x.0 release, with the difference of this is a new setup, no 
prexisting machine to consider.  My new box will be a mail only box, so 
probably little chance of running into many buggy packages.  So would 
8.0 be worth a try, since it contains lots of new stuff (sendmail, 
berkley, etc), or stick to patched up RH7.3?  (BTW, Our shop is all 
Redhat, so no flames about changing that..out of my hands)


Thanks again, (esp. to Ken for my first answer!)
LukeJ.

Ken Murchison wrote:
> No released version of Cyrus and SASL will work with gcc3.  You'll have
> to grab both from CVS.
> 
> 
> Luke Johnson wrote:
> 
>>Hey there, having a little compile problem, think it might be gcc3.2 ...
>>
>>I'm wondering if anybody has a real simple solution that I'm missing, or
>>maybe even similar experiences?  Well, here's the story:
>>
>>Just put together a cyrus-imapd-2.1.9/cyrus-sasl-2.1.7 box last week on
>>RH7.3 with the following configurations, and had zero problems -
>>
>>[root at newmail cyrus-sasl-2.1.7]# ./configure --sysconfdir=/usr/local/etc
>>--disable-krb4 --with-dbpath=/usr/local/etc/sasldb
>>--includedir=/usr/local/include  --enable-plain --enable-login
>>--disable-java --disable-gssapi --with-mysql=/usr/lib/mysql
>>--without-pam --with-rc4=openssl --with-saslauthd
>>--with-bdb-incdir=/usr/local/include/db4
>>--with-bdb-libdir=/usr/local/lib --includedir=/usr/include/mysql
>>
>>[root at newmail cyrus-imapd-2.1.9]# ./configure
>>--with-cyrus-prefix=/usr/cyrus --with-dbdir=/usr/local
>>--with-cyrus-group=mail --with-auth=unix --without-zephyr
>>--with-com-err --with-auth=unix --with-ucdsnmp=/usr/lib
>>--with-sasl=/usr/local/include
>>
>>Decided to redo the same setup this week on RH8.0, same packages, same
>>configures.  Things blew up...
>>
>>[root at newmail cyrus-sasl-2.1.7]# make
>>make  all-recursive
>>make[1]: Entering directory `/home/luke/cyrus-sasl-2.1.7'
>>Making all in include
>>make[2]: Entering directory `/home/luke/cyrus-sasl-2.1.7/include'
>>make[2]: Nothing to be done for `all'.
>>make[2]: Leaving directory `/home/luke/cyrus-sasl-2.1.7/include'
>>Making all in sasldb
>>make[2]: Entering directory `/home/luke/cyrus-sasl-2.1.7/sasldb'
>>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include   -I/usr/local/include
>>-I/usr/lib/mysql  -Wall -W -g -O2 -c ../sasldb/db_none.c
>>cc1: warning: changing search order for system directory
>>"/usr/local/include"
>>cc1: warning:   as it has already been specified as a non-system directory
>>In file included from /usr/include/sys/uio.h:29,
>>                  from /usr/include/sys/socket.h:27,
>>                  from ../config.h:352,
>>                  from ../sasldb/db_none.c:46:
>>/usr/include/bits/uio.h:43: redefinition of `struct iovec'
>>make[2]: *** [../sasldb/db_none.o] Error 1
>>make[2]: Leaving directory `/home/luke/cyrus-sasl-2.1.7/sasldb'
>>make[1]: *** [all-recursive] Error 1
>>make[1]: Leaving directory `/home/luke/cyrus-sasl-2.1.7'
>>make: *** [all-recursive-am] Error 2
>>[root at newmail cyrus-sasl-2.1.7]#
>>
>>Initially I fixed this error by commenting out some stuff in uio.h, but
>>I just ran into more library errors (lots of warnings, and eventually a
>>missing function definition) after that, decided to stop and email the
>>list before I spent all day massaging libraries and configs...
>>
>>Anybody see a simple error on my part (that would be nice), or know if
>>there is a issue at large with the Cyrus/Redhat distributions?
>>
>>Thanks,
>>LukeJ.
> 
> 






More information about the Info-cyrus mailing list