Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Set CFLAGS = $(TARGET_CFLAGS) for many packages
Date: Thu, 25 Jan 2007 01:02:49 +0100	[thread overview]
Message-ID: <02b901c74014$8da2aa80$01c4af0a@atmel.com> (raw)
In-Reply-To: 20070124232349.GF28221@aon.at

Bernhard Fischer wrote:
> On Wed, Jan 24, 2007 at 12:53:53AM +0100, Ulf Samuelsson wrote:
>> If you make Buildroot from scratch, CFLAGS gets set during the build,
>> but if you add packages later, then CFLAGS should be set in the
>> makefile fragment of the new package.
>
> I don't understand what you mean here. Please elaborate
>>

Some packages require kernel headers.
If you build from scratch, something sets CFLAGS to a good value.

If you come back the next day, reconfigure your system,
to include a new package, and recompile, many packages
will bomb out because they do not find the "asm-generic.h"

By adding this CFLAGS patch you can compile those packages.

Many packages have this already, many don't.
Can you explain when you have it and when you don't?

>> I believe that TARGET_CFLAGS needs to include the Linux Include
>> Directory or you will get compolie time errors.
>
> I don't have the linux include in my TARGET_CFLAGS AFAIK and do not
> get compile errors. What kernel-headers are you using? What errors
> are you seeing with what package?

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

  reply	other threads:[~2007-01-25  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 23:53 [Buildroot] [PATCH] Set CFLAGS = $(TARGET_CFLAGS) for many packages Ulf Samuelsson
2007-01-24 23:23 ` Bernhard Fischer
2007-01-25  0:02   ` Ulf Samuelsson [this message]
2007-01-25  9:18     ` Bernhard Fischer
2007-01-26 18:37       ` Ulf Samuelsson

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='02b901c74014$8da2aa80$01c4af0a@atmel.com' \
    --to=ulfs@dof.se \
    --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