Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
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 16:23:58 +0100	[thread overview]
Message-ID: <87vdgdttyp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <5f2b60912110653q3ad5824fpa86b07e38dab5a2@mail.gmail.com> ("Bjørn Forsman"'s message of "Fri, 11 Dec 2009 15:53:22 +0100")

>>>>> "Bj?rn" == Bj?rn Forsman <bjorn.forsman@gmail.com> writes:

 Bj?rn> I manually applied your patch (is there a better way of doing
 Bj?rn> it?)

git apply or patch

 Bj?rn> and when building a non-working configuration, there is no other
 Bj?rn> output than the warnings and then full stop. Make quits before
 Bj?rn> running the 'test' target! See the log:

Ahh yes, you never get that far with those warnings.

I think your BASE_DIR and/or BUILD_DIR variables somehow gets an extra
space appended/prepended.

Could you change the BASE_DIR := line in the toplevel makefile to simply
read:

BASE_DIR:=home/bjornfor/dev/buildroot/output

and try again?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-11 15:23 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
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 [this message]
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=87vdgdttyp.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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