From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] TARGET_CONFIGURE_OPTS
Date: Thu, 13 Nov 2008 14:07:00 +0100 [thread overview]
Message-ID: <20081113140700.67b6db3b@surf> (raw)
In-Reply-To: <ce76e3890811122014sbad333ai2101488d14ddb7f5@mail.gmail.com>
Le Thu, 13 Nov 2008 14:44:10 +1030,
"malcolm blaney" <mblaney@gmail.com> a ?crit :
> I'm trying to build dropbear, and have found that having
> $(TARGET_CONFIGURE_OPTS) in the command to build:
> $(DROPBEAR_DIR)/$(DROPBEAR_BINARY) in the file:
> package/dropbear/dropbear.mk breaks my build. With it present the
> value of CFLAGS in dropbear's makefile is not used and so some include
> paths go missing. It seems to build fine when removed, or when placed
> before $(MAKE) on the line.
What are the error messages ? What version of Buildroot are you using ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-13 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 4:14 [Buildroot] TARGET_CONFIGURE_OPTS malcolm blaney
2008-11-13 13:07 ` Thomas Petazzoni [this message]
2008-11-14 0:42 ` malcolm blaney
2008-11-14 0:53 ` Thiago A. Corrêa
2008-11-14 1:07 ` malcolm blaney
2008-11-14 14:34 ` Thiago A. Corrêa
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=20081113140700.67b6db3b@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