Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Cross-compiling Cyrus in Buildroot
Date: Tue, 23 Aug 2011 15:30:01 +0200	[thread overview]
Message-ID: <4E53AB59.3020607@lucaceresoli.net> (raw)
In-Reply-To: <4E04828A.6030908@lucaceresoli.net>

Luca Ceresoli wrote:
> Hi Cyrus and Buildroot developers,
>
> I'm working to add cyrus-sasl and cyrus-imapd (http://www.cyrusimap.org/)
> to buildroot (http://www.buildroot.net/) for use on embedded systems.
>
> On my road I hit various problems with the cross-build process:
> configuration, compilation and installation.
> I could work around some, but not really fix them as they should.

After a couple cleanup cycles my work on cyrus-imapd and cyrus-sasl has
reached a pretty stable shape. It is not perfect, but it is working.

Here's the status w.r.t. the problems I previously reported.
There is not much news, since I received almost no feedback so far.

> Here's a list of the issues I found:
> - cyrus-sasl: apparent CFLAGS mismatch on saslauthd;

I applied my proposed patch to disable saslauthd.

> - cyrus-sasl: makemd5 is wrongly cross-compiled;

I applied my proposed patch which allows to correctly host-compile
makemd5.
I wonder if it should be applied upstream.

> - cyrus-sasl: installs files with "arm-linux-" prefix

Fixed with --program-prefix=''.

> - cyrus-imapd: imtest does not cross-compile correctly;

I applied my proposed patch to disable imtest.

> - cyrus-imapd: static binaries are huge, cannot build them shared;
> - cyrus-imapd: choose binaries to (build and) install;

Not solved. The good thing is that ????? ???????? Dilyan Palauzov
volounteered to update the cyrus-imapd buildsystem
(http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-devel&searchterm=automake&msg=3040),
which would fix these two issues, and possibly also the previous one
with imtest.

I'm going to send a patch series with the current status of my work.
I'd like to know from the buildroot developers whether it is good
enough to be applied or the mentioned problems are too big.

Luca

      parent reply	other threads:[~2011-08-23 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 12:26 [Buildroot] Cross-compiling Cyrus in Buildroot Luca Ceresoli
2011-06-24 12:38 ` [Buildroot] cyrus-sasl in buildroot: apparent CFLAGS mismatch on saslauthd Luca Ceresoli
2011-06-24 12:52 ` [Buildroot] cyrus-sasl in buildroot: makemd5 is wrongly cross-compiled Luca Ceresoli
2011-06-24 13:03 ` [Buildroot] cyrus-sasl in buildroot: installs files with "arm-linux-" prefix Luca Ceresoli
2011-08-23 13:06   ` Luca Ceresoli
2011-06-24 15:20 ` [Buildroot] cyrus-imapd in buildroot: imtest does not cross-compile correctly Luca Ceresoli
2011-06-24 16:27 ` [Buildroot] cyrus-imapd: static binaries are huge + choose binaries to install Luca Ceresoli
2011-08-23 13:30 ` Luca Ceresoli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E53AB59.3020607@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox