Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: [25880] trunk/buildroot/package: automake libtool pkgconfig
Date: Mon, 30 Mar 2009 08:24:42 +0200	[thread overview]
Message-ID: <20090330082442.34a53123@surf> (raw)
In-Reply-To: <20090329191026.8F79877487@busybox.osuosl.org>

Hi,

Le Sun, 29 Mar 2009 19:10:26 +0000 (UTC),
jacmet at uclibc.org a ?crit :

> Revert r25827 and instead copy over the host aclocal files of the
> stuff needed for auto* (libtool + pkgconfig). These logically belong
> with the target stuff, as they are used for the target auto*
> toolchain.
> 
> Long term we should probably consider using
> aclocal --acdir=$(STAGING_DIR)/usr/share/aclocal, so the host .m4
> files cannot interfere with the target build.

I must admit I'm far from being a auto* expert, and I'm quite confused
by the host vs. target auto* difference. So please excuse my silly
questions.

With your version, when a package sets FOO_AUTORECONF=YES, it will use
the autotools of the host (installed in $(HOST_DIR)), but these
autotools will be told to use the aclocal files in $(STAGING_DIR), and
therefore will only see the aclocal files for libtool and pkgconfig. Is
this what we want ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-03-30  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 19:10 [Buildroot] svn commit: [25880] trunk/buildroot/package: automake libtool pkgconfig jacmet at uclibc.org
2009-03-30  6:24 ` Thomas Petazzoni [this message]
2009-03-30  7:22   ` 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=20090330082442.34a53123@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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