Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture.
Date: Mon, 25 Mar 2013 08:11:24 +0100	[thread overview]
Message-ID: <514FF89C.3060408@mind.be> (raw)
In-Reply-To: <20130322152920.59b74891@skate>

On 22/03/13 15:29, Thomas Petazzoni wrote:
> Dear Sonic Zhang,
>
> On Fri, 22 Mar 2013 17:01:41 +0800, Sonic Zhang wrote:
[snip]
>> +ifneq ($(BR2_USE_MMU), y)
>> +TARGET_CFLAGS += -D__NOMMU__
>> +endif
>
> I'm still not entirely happy with that. This define is completely
> non-standard, I am not sure we want to have this at the global level.
> autotools-based packages should be fixed to check if fork() is
> available or not. For other packages, this special flag can be
> introduced on a per-package basis. But it's true that maybe a good
> number of packages will need that. Not sure here. What do others think?

  Since this is a non-standard flag, it would go together with some patch 
that adds the possibility of NOMMU builds. I would say that it's a good 
idea to have an explicit extra -DNOMMU in those .mk files.

  As to the large number of packages using it: it should anyway only be 
used for make-based packages (autotools and cmake should have different 
ways to detect NOMMU). So the number of packages using it wouldn't be 
that large.

  And finally, that do this that we have already (irda-utils and portmap) 
call it NO_FORK.

  Regards,
  Arnout

[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-03-25  7:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  9:01 [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Sonic Zhang
2013-03-22  9:01 ` [Buildroot] [PATCH v3 2/2] buildroot: target: Add Blackfin architecture support Sonic Zhang
2013-03-22 14:54   ` Thomas Petazzoni
2013-03-25 11:33     ` Sonic Zhang
2013-03-25 11:47       ` Thomas De Schampheleire
2013-03-26  8:16         ` Sonic Zhang
2013-03-26  8:41           ` Thomas Petazzoni
2013-03-26  9:36             ` Sonic Zhang
2013-03-26 10:08               ` Thomas Petazzoni
2013-03-26  7:25   ` Arnout Vandecappelle
2013-03-26  8:15     ` Thomas Petazzoni
2013-03-28  8:20       ` Sonic Zhang
2013-03-28  8:56         ` Thomas Petazzoni
2013-03-29  9:50           ` Sonic Zhang
2013-03-22 14:29 ` [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Thomas Petazzoni
2013-03-22 17:28   ` Thomas De Schampheleire
2013-03-25  7:11   ` Arnout Vandecappelle [this message]
2013-03-25  7:50   ` Sonic Zhang
2013-03-25  7:57     ` Sonic Zhang
2013-03-25  7:58     ` Thomas Petazzoni
2013-03-25  8:51       ` Sonic Zhang

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=514FF89C.3060408@mind.be \
    --to=arnout@mind.be \
    --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