From: Kieran Bingham <kieranbingham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] *Tons* of BR warnings like "package/Makefile.autotools.in:179: warning: overriding commands for target `/home/bjornfor/raid/forks/buildroot/output'"
Date: Fri, 11 Dec 2009 10:09:50 +0000 [thread overview]
Message-ID: <4B221A6E.3090105@gmail.com> (raw)
In-Reply-To: <5f2b60912101234r46ca2234w760ddd2a01032525@mail.gmail.com>
> But I find that strange as I'm pretty sure I've successfully used Buildroot
> revisions after this commit before.
>
> I think it must be something wrong with *my* setup since nobody else has
> noticed this (and the commit is from July), but I don't know what it may be.
> Any suggestions?
>
Actually I pulled Buildroot yesterday and also found this.
Perhaps its our environments ... I'm on ubuntu 9.10 Karmic ...
I don't think its a bash/dashism as I have /bin/sh -> /bin/bash ...
I hadn't got as far as looking at git bisect yet though ...
> Best regards,
> Bj?rn Forsman
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2009-12-11 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 20:34 [Buildroot] *Tons* of BR warnings like "package/Makefile.autotools.in:179: warning: overriding commands for target `/home/bjornfor/raid/forks/buildroot/output'" Bjørn Forsman
2009-12-11 10:09 ` Kieran Bingham [this message]
2009-12-11 10:36 ` Bjørn Forsman
2009-12-11 11:16 ` Peter Korsgaard
2009-12-11 13:14 ` Bjørn Forsman
2009-12-11 13:59 ` Peter Korsgaard
2009-12-11 14:53 ` Bjørn Forsman
2009-12-11 15:23 ` Peter Korsgaard
2009-12-13 20:51 ` Bjørn Forsman
2009-12-13 21:28 ` Peter Korsgaard
2009-12-14 9:25 ` Bjørn Forsman
2009-12-11 11:18 ` Thomas Petazzoni
2009-12-11 13:23 ` Bjørn Forsman
2009-12-11 13:35 ` Marc Egli
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=4B221A6E.3090105@gmail.com \
--to=kieranbingham@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.