Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] $(TARGET_CONFIGURE_OPTS) $(MAKE) vs $(MAKE)	$(TARGET_CONFIGURE_OPTS)
Date: Sun, 8 Jul 2007 00:49:20 +0200	[thread overview]
Message-ID: <05fb01c7c0e9$275c45a0$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20070707211606.GZ4096@aon.at

> On Sat, Jul 07, 2007 at 09:37:05PM +0200, Ulf Samuelsson wrote:
>>l?r 2007-07-07 klockan 19:29 +0200 skrev Bernhard Fischer:
>>> On Sat, Jul 07, 2007 at 06:06:23PM +0200, Ulf Samuelsson wrote:
>>> >> >I think someone got it wrong in the "package/mtd/mtd.mk" which says
>>> >> >
>>> >> >    $(TARGET_CONFIGURE_OPTS) $(MAKE) ...    - build using gcc
>>> >> >    
>>> >> >which should be:
>>> >> >
>>> >> >     $(MAKE) $(TARGET_CONFIGURE_OPTS) ...    - build using arm-linux-uclibc-gcc
>>> >> 
>>> >> yes, the latter is correct. Steven, please repair or elaborate.
>>> >> 
>>> >
>>> >Here are a set of patches to change the position of
>>> >TARGET_CONFIGURE_OPTS.
>>> >Please review and apply if you agree.
>>> >
>>> >
>>

Stephen, can you pls review the mtd part of this patch ASAP,
since this breaks the build for ARM (and possibly all non-x86).
Pls commit (or ack my commit) if OK.

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group        mailto:avr32 at atmel.com
http://www.avrfreaks.net/;            http://avr32linux.org/
http://www.at91.com/ ;                ftp://at91dist:distrib at 81.80.104.162/

  reply	other threads:[~2007-07-07 22:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 12:35 [Buildroot] What is the proper procedure to commit a patch? Ulf Samuelsson
2007-07-06 15:26 ` Bernhard Fischer
2007-07-06 15:36   ` Ulf Samuelsson
2007-07-07 10:12     ` Bernhard Fischer
2007-07-07 11:16       ` Ulf Samuelsson
2007-07-07 12:35         ` Bernhard Fischer
2007-07-07 13:46           ` Ulf Samuelsson
2007-07-06 15:55 ` Steven J. Hill
2007-07-06 21:10   ` Ulf Samuelsson
2007-07-07 10:06   ` [Buildroot] $(TARGET_CONFIGURE_OPTS) $(MAKE) vs $(MAKE) $(TARGET_CONFIGURE_OPTS) Ulf Samuelsson
2007-07-07 13:01     ` Bernhard Fischer
2007-07-07 16:06       ` Ulf Samuelsson
2007-07-07 17:29         ` Bernhard Fischer
2007-07-07 19:37           ` Ulf Samuelsson
2007-07-07 21:16             ` Bernhard Fischer
2007-07-07 22:49               ` Ulf Samuelsson [this message]
2007-07-09  8:25                 ` Bernhard Fischer
2007-07-09  9:21                   ` Bernhard Fischer
2007-07-09 12:20                     ` Steven J. Hill
2007-07-09 13:41                       ` Julien Letessier
2007-07-09 13:08                         ` Ulf Samuelsson
2007-07-09 16:33                         ` Bernhard Fischer
2007-07-10 11:51                           ` Julien Letessier
2007-07-10 18:24                             ` Bernhard Fischer
2007-07-07 10:21 ` [Buildroot] What is the proper procedure to commit a patch? Bernhard Fischer

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='05fb01c7c0e9$275c45a0$dcc4af0a@atmel.com' \
    --to=ulf@atmel.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