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: [25880] trunk/buildroot/package: automake libtool pkgconfig
Date: Mon, 30 Mar 2009 09:22:50 +0200	[thread overview]
Message-ID: <871vsfcw51.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090330082442.34a53123@surf> (Thomas Petazzoni's message of "Mon\, 30 Mar 2009 08\:24\:42 +0200")

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

Hi,

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

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

That and all the .m4 files installed by the various
packages - E.G. from a build with X support:

ls build_arm/staging_dir/usr/share/aclocal
codeset.m4       intl.m4          longdouble.m4    ulonglong.m4
freetype2.m4     intmax.m4        longlong.m4      visibility.m4
gettext.m4       inttypes_h.m4    ltdl.m4          wchar_t.m4
glib-2.0.m4      inttypes-pri.m4  nls.m4           wint_t.m4
glibc21.m4       lcmessage.m4     pkg.m4           xaw.m4
glibc2.m4        lib-ld.m4        po.m4            xorg-macros.m4
glib-gettext.m4  lib-link.m4      printf-posix.m4  xorg-server.m4
gtk-2.0.m4       lib-prefix.m4    progtest.m4      xorgversion.m4
iconv.m4         libtool.m4       size_max.m4      xsize.m4
intdiv0.m4       libxml.m4        stdint_h.m4      xtrans.m4
intldir.m4       lock.m4          uintmax_t.m4

The point is to not mix up stuff (in this case .m4 files) between host
and target builds. Our staging dir used to be a big mix of stuff for
the host and the target, and this is part of a cleanup of it.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-03-30  7:22 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
2009-03-30  7:22   ` Peter Korsgaard [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=871vsfcw51.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