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] ofono package
Date: Fri, 23 Mar 2012 10:11:00 +0100	[thread overview]
Message-ID: <20120323101100.5fa94c86@skate> (raw)
In-Reply-To: <CAGm1_ks7QkKyFS7wWPMi3ytu4d2QU=k=gVEcnq6ENoA-CM3sKQ@mail.gmail.com>

Le Fri, 23 Mar 2012 09:36:02 +0100,
Yegor Yefremov <yegorslists@googlemail.com> a ?crit :

> > +define OFONO_CONFIGURE_CMDS
> > + ? ? ? (cd $(@D) && ./bootstrap-configure $(OFONO_CONF_OPT))
> > +endef

This is not correct, and will fail to set the right path and pkg-config
environment variables. Why is such a special bootstrap-configure script
needed?

If this bootstrap stuff is used to regenerate the configure script and
Makefile.am, then use OFONO_AUTORECONF=YES.

Otherwise, if you really need to do this special configure command,
then do something like:

	(cd $(@D) && \
		$(TARGET_CONFIGURE_OPTS) \
		$(TARGET_CONFIGURE_ARGS) \
		$(OFONO_CONF_ENV) \
		./bootstrap-configure \
		$(OFONO_CONF_OPT))

But since you're not passing --host=something, I am quite skeptical
on how it can guess which cross-compiler should be used.

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

  parent reply	other threads:[~2012-03-23  9:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  0:54 [Buildroot] ofono package Belisko Marek
2012-03-23  8:36 ` Yegor Yefremov
2012-03-23  8:41   ` Belisko Marek
2012-03-23  8:45     ` Thomas Petazzoni
2012-03-23  8:57       ` Yegor Yefremov
2012-03-23  9:11   ` Thomas Petazzoni [this message]
2012-03-23  9:20     ` Thomas Petazzoni
2012-03-23  9:29       ` Yegor Yefremov
2012-03-23  9:32         ` Belisko Marek
2012-03-23  9:53           ` Yegor Yefremov
2012-03-23 11:44             ` Belisko Marek

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=20120323101100.5fa94c86@skate \
    --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