From: James J. Dines <jdines@jdines.net>
To: buildroot@busybox.net
Subject: [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but ...
Date: Mon, 30 Aug 2010 17:10:00 -0400 [thread overview]
Message-ID: <4C7C1E28.1060806@jdines.net> (raw)
In-Reply-To: <87y6bnx1h8.fsf@macbook.be.48ers.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/30/2010 04:57 PM, Peter Korsgaard wrote:
>>>>>> "James" == James J Dines <jdines@jdines.net> writes:
>
> Hi,
>
> James> I am really interested to hear your results, because I just
> James> bought this new 8 core machine and set it up this weekend. So
> James> far everything has worked great, but there is always this
> James> nagging worry that I have something set up wrong and I will have
> James> to post back to the list stating that I was an idiot and missed
> James> something :-)
>
> James> In any case, untarring buildroot-2010.05, doing a make defconfig
> James> followed by a make clean seems like a set of steps that should
> James> go off without a hitch (it certainly does on my other machine)
> James> but it fails with make 3.82 for me anyway :-(
>
> James> [jdines at hydra buildroot-2010.05 ] make clean
> James> package/atk/atk.mk:43: *** recipe commences before first target. Stop.
>
> Yeah, that's the bug in atk.mk Yann fixed earlier today. Could you give
> git a try instead (either git clone or wait for tomorrows snapshot
> tarball).
>
I went for a third option (applying Yann's patch) and it indeed allows
the 'make clean' to work. I remain confused why we did not need this
patch to do a complete build with make 3.81 however. I just tried it
again, and I do not get the error message on my other machine with 3.81
even without the patch.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMfB4eAAoJECSpOhdQESq6WcYH/j1xrDLXel5j4J71Rqsv6gFr
5zy99A62YqgRjh4VrEZM07SnjZxAAimpEp5eUQCGGGbbxM3q0qFfZmGc6xPo+0lA
+bUP9fMdwjQiSJYZ42fmbSSNz3fvoQ6RhP85J3H5KvZEBD91H5jGtrNV7RK7Z+oI
PHy4aZroBlUP+TyQNRPB9Zd8ylC/sWghUya3cWs67h1rROGJKtOLeSaOWTSeRuKI
B7Lj7l3MDPB4rt1rC++vE7Sn17hiX1MCDoBijxuyR8jCmCwGUuiG/C+yUL+5oY2v
10uoQq0/wZ7P1uNiutWsoviLv8/KStQuOYg86ONUsJEVgDubHgLNF9rMXlQTopg=
=b3Zf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-30 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 11:45 [Buildroot] package/atk/atk.mk:43: *** recipe commences before first target. Stop James J. Dines
2010-08-30 13:05 ` Yann E. MORIN
2010-08-30 13:37 ` Peter Korsgaard
2010-08-30 14:46 ` James J. Dines
2010-08-30 15:01 ` Yann E. MORIN
2010-08-30 15:44 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but James J. Dines
2010-08-30 16:31 ` Sam Ravnborg
[not found] ` <4C7BE3C4.1060706@jdines.net>
[not found] ` <20100830185017.GA12921@merkur.ravnborg.org>
2010-08-30 19:01 ` [Buildroot] Make 3.82 does behave differently than make 3.81 James J. Dines
2010-08-30 20:00 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but Peter Korsgaard
2010-08-30 20:21 ` James J. Dines
2010-08-30 20:57 ` Peter Korsgaard
2010-08-30 21:10 ` James J. Dines [this message]
2010-08-30 21:36 ` Peter Korsgaard
2010-08-30 23:28 ` James J. Dines
2010-08-31 22:17 ` [Buildroot] Make 3.82 testing progress update James J. Dines
2010-08-30 22:15 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but Malte Starostik
2010-08-31 12:38 ` James J. Dines
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=4C7C1E28.1060806@jdines.net \
--to=jdines@jdines.net \
--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