Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kmsxx: not available on m68k
Date: Tue, 14 Feb 2017 12:42:04 +0100	[thread overview]
Message-ID: <20170214114204.GD12810@waldemar-brodkorb.de> (raw)
In-Reply-To: <87fujhkrik.fsf@dell.be.48ers.dk>

Hi Peter,
Peter Korsgaard wrote,

> >>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
> 
> Hi,
> 
>  >> That's also fine by me if somebody wants to do that. I personally don't
>  >> know/care enough about m68k, and it has been failing since October
>  >> without anything happening, so I think we should disable it.
> 
>  > It is not that nothing happened.
>  > I think this would be solved by my following patch:
>  > http://buildroot-busybox.2317881.n4.nabble.com/PATCH-m68k-add-special-gcc-flag-to-avoid-ICE-for-coldfire-td151151.html
> 
> Sorry, I forgot about the relation between this build issue and the
> "magic" compiler flag.
> 
>  > Did you had a chance to discuss the required changes with Arnout in
>  > the last developer meeting?
> 
> I could only join from Monday evening, but I don't think so.
> 
> We are again past rc1, so I think the safest approach for 2017.02 is to
> not add it to the wrapper, but instead explicitly pass it in kmsxx.mk
> (and any other package with the same problem). From my IRC history this
> also seems to be what you discussed with Thomas yesterday.
> 
> Will you send patches to do this?

I can try. But now I am back to my original problem, how do I
overwrite CFLAGS/CXXFLAGS correctly for a single package build with
cmake?

Any examples in the tree?

I think that was the reason we tried to add it globally in the
wrapper :/

best regards
 Waldemar

  parent reply	other threads:[~2017-02-14 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  9:35 [Buildroot] [PATCH] kmsxx: not available on m68k Peter Korsgaard
2017-02-13 12:29 ` Thomas Petazzoni
2017-02-13 14:32   ` Peter Korsgaard
2017-02-13 21:37     ` Waldemar Brodkorb
2017-02-14 10:15       ` Peter Korsgaard
2017-02-14 10:18         ` Thomas Petazzoni
2017-02-14 11:42         ` Waldemar Brodkorb [this message]
2017-02-14 11:58           ` Thomas Petazzoni
2017-02-14 12:10           ` Peter Korsgaard

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=20170214114204.GD12810@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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