On Tue, 15 Jul 2003, Sergei Kolobov wrote: > On 2003-07-15 at 00:07 +0100, Adrian Urquhart wrote: > > Well, I did the obvious thing and grabbed the source tarball then fired > > up the compiler. All options left at default values. > > > > I end up with a bincimapd binary which is 31,134,575 bytes in size! Even > > after a strip it's 1,907,040 bytes. Surely this isn't right? I'm sure I > > didn't ask for a static build... > > Well, the Binc IMAP port, compiled under FreeBSD 5.1-CURRENT produce > files with the following sizes: > > -r-xr-xr-x root/wheel 812544 Jun 3 16:30 2003 bin/bincimapd > -r-xr-xr-x root/wheel 388948 Jun 3 16:30 2003 bin/bincimap-up > > I suggest you to try the port: > > # cd /usr/ports/mail/bincimap > # make install && make clean > > Sergei > I've got it fired up, albeit with executables twice the size you mention above. I generally don't use ports ar they're often one or two versions behind the current, and often intall things where I don't expect them to.
I did a reconfigure and set CXXGLAGS="-O2" but are there any other knobs I can turn? When using Pine as the client, I can only see the INBOX, and not any of the existing folders created by Courier (the same is true in KMail). How can I "upgrade" the folders to allow Binc to see them - is it Ok to just add them to the bincimap-subscribed file? Can I leave -uidvalidity and -cache missing? I need to do this programmatically, not helped by the system being 500 miles away... -Adrian
