Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: [25827] trunk/buildroot/package/automake
Date: Thu, 26 Mar 2009 21:45:36 +0100	[thread overview]
Message-ID: <87zlf8f1xr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090326213421.55dae490@surf> (Thomas Petazzoni's message of "Thu\, 26 Mar 2009 21\:34\:21 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 Thomas> At least, my (maybe incorrect) change fixes the issue I reported in
 Thomas> the mail titled "Bug while autoreconfiguring tslib", sent today. But
 Thomas> maybe the correct fix is something like

 Thomas> - AUTORECONF=$(HOST_CONFIGURE_OPTS) ACLOCAL="$(ACLOCAL)" $(HOST_DIR)/usr/bin/autoreconf -v -f -i -I "$(ACLOCAL_DIR)"
 Thomas> + AUTORECONF=$(HOST_CONFIGURE_OPTS) ACLOCAL="$(ACLOCAL)" $(HOST_DIR)/usr/bin/autoreconf -v -f -i -I "$(HOST_ACLOCAL_DIR)"

I think the best/simplest solution is to just copy the aclocal files
of the cross tools (pkgconfig +auto*) from HOST_DIR to STAGING_DIR and
point ACLOCAL_DIR to STAGING_DIR - I'll give it a test.

 Thomas> BTW, could you remind me why we need to compile all these tools for the
 Thomas> host (pkg-config, automake, autoconf). Couldn't they be dependencies of
 Thomas> Buildroot ?

pkg-config to make it look in staging_dir and not the host directory,
and the auto* stuff simply because of the exact version dependencies
(E.G. certain stuff works with 2.61 and not with 2.63 or the other
way, so it keeps us a bit more sane to know that everyone uses the
same version).

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-03-26 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 16:55 [Buildroot] svn commit: [25827] trunk/buildroot/package/automake tpetazzoni at uclibc.org
2009-03-26 17:02 ` Peter Korsgaard
2009-03-26 20:34   ` Thomas Petazzoni
2009-03-26 20:45     ` Peter Korsgaard [this message]
2009-03-29 19:18       ` Peter Korsgaard

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=87zlf8f1xr.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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