Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] ccache issue with zlib dependency
Date: Sat, 11 Feb 2012 16:47:02 +0100	[thread overview]
Message-ID: <201202111647.03064.arnout@mind.be> (raw)
In-Reply-To: <CAMP44s3eoG9jOoG7Gv_CvyKtG5dPbf+mP-_S7=cB-1LcJBM2hQ@mail.gmail.com>

On Saturday 11 February 2012 00:36:04 Felipe Contreras wrote:
> Hi,
> 
> I have a newer version of zlib (1.2.6) on my host system than what
> buildroot is using (1.2.5), ultimately the build fails because I have
> enabled ccache, and it uses zlib, and when the older zlib is installed
> there are missing symbols (ZLIB_1.2.5.2), so ccache doesn't work any
> more, and everything else fails.
> 
> I tried to add the zlib dependency to ccache, but the build also fails
> because apparently host-zlib tries to use ccache.

 As a workaround, you can add CC="$(HOSTCC_NOCCACHE)" to the build
commands of host-zlib.  But I don't particularly like it.

 Another option is to force ccache to use its bundled zlib, by adding
ccache_cv_zlib_1_2_3=no to HOST_CCACHE_CONF_ENV.

 The best option would be to check in support/dependencies if the
system has a good zlib, and only build host-zlib if it doesn't.  But
that's major surgery in the build system again.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-02-11 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 23:36 [Buildroot] ccache issue with zlib dependency Felipe Contreras
2012-02-11 15:47 ` Arnout Vandecappelle [this message]
2012-02-12 20:41   ` Felipe Contreras

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=201202111647.03064.arnout@mind.be \
    --to=arnout@mind.be \
    --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