From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ruby: fix 'pcrel too far' build problem on SuperH architectures
Date: Sun, 13 Oct 2013 10:25:26 +0200 [thread overview]
Message-ID: <20131013102526.56152a76@skate> (raw)
In-Reply-To: <CAAXf6LXA-UK2EcGnmRvhfA8cT_+-GsZTQ1o2ubjbFGnGAL4k2w@mail.gmail.com>
Dear Thomas De Schampheleire,
On Sun, 13 Oct 2013 09:58:05 +0200, Thomas De Schampheleire wrote:
> > I don't think it's the right way of fixing the problem. This is going to
> > affect the CFLAGS of *all* packages. You shouldn't change
> > TARGET_CFLAGS, but instead do:
> >
> > RUBY_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -O2"
>
> Ah yes, you're right. The above was what I proposed initially, but I
> tried to be too smart.
> I was looking for a way to avoid duplicating TARGET_CFLAGS, because if
> someone needs to add a new cflag for ruby specifically, they now need
> to explicitly take the superh case into account.
>
> I'll send a new version.
The way we usually do this is:
RUBY_CFLAGS = $(TARGET_CFLAGS)
ifeq ($(BR2_sh)$(BR2_sh64),y)
RUBY_CFLAGS += -O2
endif
RUBY_CONF_ENV += CFLAGS="$(RUBY_CFLAGS)"
This way, someone else can easily add another RUBY_CFLAGS +=, and not
worry about the SuperH thing.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-13 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 7:44 [Buildroot] [PATCH] ruby: fix 'pcrel too far' build problem on SuperH architectures Thomas De Schampheleire
2013-10-13 7:51 ` Thomas Petazzoni
2013-10-13 7:58 ` Thomas De Schampheleire
2013-10-13 8:25 ` Thomas Petazzoni [this message]
2013-10-13 10:38 ` Thomas De Schampheleire
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=20131013102526.56152a76@skate \
--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