Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procrank_linux: new package
Date: Tue, 23 Feb 2016 17:36:14 -0300	[thread overview]
Message-ID: <56CCC2BE.6060901@free-electrons.com> (raw)
In-Reply-To: <56CCC087.9060506@mind.be>

On 23/02/16 17:26, Arnout Vandecappelle wrote:

>   You forgot to add a hash file.

Are github pull hashes stable? (i.e. not tagged)

>   Check. There's a Makefile licensed GPLv2+ but I guess that's not relevant.

I've used the same logic, in the end it's the code that matters.

>   What a horrible Makefile... There is no way to pass CFLAGS and LDFLAGS.
> Fortunately, with the toolchain wrapper, this shouldn't be a problem anymore.
> Well, except for LDFLAGS. This _is_ going to be a problem on e.g. Blackfin FLAT.
> I guess a patch adding CFLAGS and LDFLAGS to the Makefiles would be upstreamable?

Actually bfin flat builds fine, it's on my testing rotation for static 
builds when there's no need for mmu since it uses an old gcc and it's 
quick to catch "newer version required" scenarios (everything quite old 
and funky).
That being said i had a previous version that i wasn't quick enough to 
submit that had a patch which was removed since upstream was quick 
enough accepting the pull (musl build fix).
Regards.

  reply	other threads:[~2016-02-23 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 15:54 [Buildroot] [PATCH] procrank_linux: new package gustavo.zacarias at free-electrons.com
2016-02-23 20:26 ` Arnout Vandecappelle
2016-02-23 20:36   ` Gustavo Zacarias [this message]
2016-02-23 21:06     ` Thomas Petazzoni
2016-02-23 21:35     ` Arnout Vandecappelle
2016-03-06 15:13       ` Thomas Petazzoni
2016-03-06 15:13 ` Thomas Petazzoni

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=56CCC2BE.6060901@free-electrons.com \
    --to=gustavo.zacarias@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