[CentOS] Compilation problem - CentOS 4.2 - x86_64

[Johnny Hughes]

On Wed, 2005-12-14 at 08:27 -0500, Jim Perrin wrote:
> On 12/14/05, kadafax <kadafax at gmail.com> wrote:
> > Hi list,
> > Here it is: I have compiled with no problem courier-imap-4.0.4 on this
> > arch (x86_64). Now I want to update my install with 4.0.6. I want to do
> > this because the server is not yet in a production state, so if a major
> > flaw affects courier-imap in the future, I could react more quickly. And
> > indeed I'm encountering problems with the make process (Since I initialy
> > build courier-imap from sources and that I dont want FAM, I'm not using
> > the rpmbuild process). I've stricly followed the INSTALL's instructions.
> >
> > I believe the problem comes from the mixed libraries living on
> > the system (x86_64 and, for compatibility purpose, i386) and I didn't
> > find a workaround on this. I'm near to switch to dovecot if it can
> > handle quite large amount of users (500-1000 accounts). That would be
> > bad because I think courier-imap is well doing its job. By the way,
> > someone tolds me that courier-imap and RHEL4 (and clones) is a bad idea,
> > someone can confirm?
> > So:
> >
> >
> > [user at host courier-imap-4.0.6]$ ./configure --with-redhat
> > ...
> >             // process goes ok, no warning no errors
> > configure: creating ./config.status
> > config.status: creating Makefile
> > config.status: creating imapd.dist
> > config.status: creating imapd-ssl.dist
> > config.status: creating pop3d.dist
> > config.status: creating pop3d-ssl.dist
> > config.status: creating testsuitefix.pl
> > config.status: creating mkimapdcert
> > config.status: creating mkpop3dcert
> > config.status: creating imapd.cnf
> > config.status: creating pop3d.cnf
> > config.status: creating config.h
> > config.status: executing depfiles commands
> >
> > [user at host courier-imap-4.0.6]$ make
> > ...
> >           // I'm just pasting the first errors, the others seems to come
> > from the first ones anyway:
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_tree.h:66,
> >                   from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/set:66,
> >                   from maildirkeywords.h:435,
> >                   from maildirkeywords4.cpp:9:
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algobase.h:64:28:
> > bits/c++config.h: No such file or directory
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algobase.h:70,
> >                   from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_tree.h:66,
> >                   from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/set:66,
> >                   from maildirkeywords.h:435,
> >                   from maildirkeywords4.cpp:9:
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/iosfwd:46:29:
> > bits/c++locale.h: No such file or directory
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/iosfwd:47:25:
> > bits/c++io.h: No such file or directory
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_tree.h:67,
> >                   from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/set:66,
> >                   from maildirkeywords.h:435,
> >                   from maildirkeywords4.cpp:9:
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/allocator.h:52:31:
> > bits/c++allocator.h: No such file or directory
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_tree.h:67,
> >                   from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/set:66,
> >                   from maildirkeywords.h:435,
> >                   from maildirkeywords4.cpp:9:
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/allocator.h:80:
> > error: expected template-name before '<' token
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/allocator.h:80:
> > error: expected `{' before '<' token
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/allocator.h:80:
> > error: expected unqualified-id before '<' token
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/allocator.h:80:
> > error: expected `;' before '<' token
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/set:67,
> >                   from maildirkeywords.h:435,
> >                   from maildirkeywords4.cpp:9:
> > ...
> 
> Courier comes with a spec file for producing an rpm. You should
> consider using this for building instead, as it will usually help
> solve dependency/build issues or explain them in a slightly better
> way. rpmbuild -tb courier-foo.tar.bz2
> 


I also highly recommend NOT building x86_64 stuff on a machine that has
x86 libraries installed on it.

You need a separate build machine (or chroot) that is only x86_64 items
and glibc.i686 and glibc-devel.i386 ... 

or you will have much trouble building items from source and have mixed
up library requirements ... if it builds at all.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.centos.org/pipermail/centos/attachments/20051214/2209ecda/attachment.sig>