From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Change Makefile into a crosscompile friendly version
Date: Sat, 21 Jun 2014 12:06:33 +0200 [thread overview]
Message-ID: <20140621100633.GA3501@free.fr> (raw)
In-Reply-To: <53A4B2C2.4070107@mind.be>
Arnout, Eric, All,
On 2014-06-21 00:16 +0200, Arnout Vandecappelle spake thusly:
> If this patch fixes a build issue, then it should be squashed with the previous
> patch. You can do that by doing 'git rebase -i origin/master' and then replacing
> the 'pick' of this patch with 'fixup'.
Yep, Eric said on IRC he made a mistake when sending the patches.
> On 20/06/14 00:00, Eric Limpens wrote:
> > Signed-off-by: Eric Limpens <limpens@gmail.com>
> > ---
> > ...ifmrds-000-Makefile-crosscompile-friendly.patch | 25 ++++++++++++++++++++++
> > 1 file changed, 25 insertions(+)
> > create mode 100644 package/pifmrds/pifmrds-000-Makefile-crosscompile-friendly.patch
> >
> > diff --git a/package/pifmrds/pifmrds-000-Makefile-crosscompile-friendly.patch b/package/pifmrds/pifmrds-000-Makefile-crosscompile-friendly.patch
> > new file mode 100644
> > index 0000000..8b8cd49
> > --- /dev/null
> > +++ b/package/pifmrds/pifmrds-000-Makefile-crosscompile-friendly.patch
> > @@ -0,0 +1,25 @@
>
> The patch should start with a description, like a normal commit message. This
> description should also contain your Signed-off-by tag (its meaning is different
> because it implies publication under the upstream's GPLv3 license, not under
> buildroot's GPLv2 license).
>
> Also, it would be good to upstream this patch.
>
>
> > +diff -purN PiFmRds-c67306ea9b8d827f45e0d90279d367e97119bcb1/src/Makefile pifmrds-c67306ea9b8d827f45e0d90279d367e97119bcb1/src/Makefile
> > +--- PiFmRds-c67306ea9b8d827f45e0d90279d367e97119bcb1/src/Makefile 2014-05-04 18:21:40.000000000 +0200
> > ++++ pifmrds-c67306ea9b8d827f45e0d90279d367e97119bcb1/src/Makefile 2014-06-19 21:21:14.220328601 +0200
> > +@@ -1,20 +1,8 @@
> > +-CC = gcc
> > +-STD_CFLAGS = -Wall -std=gnu99 -c -g -O3
> > +-
> > +-# Enable ARM-specific options only on ARM, and compilation of the app only on ARM
> > +-UNAME := $(shell uname -m)
> > +-
> > +-ifeq ($(UNAME), armv6l)
> > +- CFLAGS = $(STD_CFLAGS) -march=armv6 -mtune=arm1176jzf-s -mfloat-abi=hard -mfpu=vfp -ffast-math
> > ++all: app rds_wav
> > +
> > + app: rds.o waveforms.o pi_fm_rds.o fm_mpx.o control_pipe.o
> > + $(CC) -o pi_fm_rds rds.o waveforms.o pi_fm_rds.o fm_mpx.o control_pipe.o -lm -lsndfile
>
> Actually, moving this outside the condition and adding the 'all' target is all
> that is really necessary to make cross-compilation possible. The rest maybe
> makes it nicer, but is not really necessary. It also won't be acceptable
> upstream because it makes native compilation more difficult.
I think we do not want the Makefile to override the CFLAGS. Buildroot
already pases appropriate CFLAGS, and keeping the ones above would be
only confusing, especially since it forces the float ABI and use of the
VFP.
Maybe we should however carry the -ffast-math flag, however.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-06-21 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 22:00 [Buildroot] [PATCH 1/2] Add pifmrds package Eric Limpens
2014-06-19 22:00 ` [Buildroot] [PATCH 2/2] Change Makefile into a crosscompile friendly version Eric Limpens
2014-06-20 22:16 ` Arnout Vandecappelle
2014-06-21 10:06 ` Yann E. MORIN [this message]
2014-06-20 22:02 ` [Buildroot] [PATCH 1/2] Add pifmrds package Arnout Vandecappelle
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=20140621100633.GA3501@free.fr \
--to=yann.morin.1998@free.fr \
--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