From: James J. Dines <jdines@jdines.net>
To: buildroot@busybox.net
Subject: [Buildroot] Make 3.82 does behave differently than make 3.81
Date: Mon, 30 Aug 2010 15:01:11 -0400 [thread overview]
Message-ID: <4C7BFFF7.6030501@jdines.net> (raw)
In-Reply-To: <20100830185017.GA12921@merkur.ravnborg.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/30/2010 02:50 PM, Sam Ravnborg wrote:
> On Mon, Aug 30, 2010 at 01:00:52PM -0400, James J. Dines wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/30/2010 12:31 PM, Sam Ravnborg wrote:
>>>>
>> <snip>
>>> And we use the "foo foo%" construct in the top-level Makefile of the kernel.
>>> The stable team have now backported a fix for this and it should apply
>>> to 2.6.26 too - or at least simple to do manually.
>>
>> It is a git tree. With a tarball, you can unpack it, patch it, repack
>> it and put it up on the web with the same name thereby having two
>> identically named tarballs with different contents (though this is a
>> horrible idea of course.)
>
> The mainstream kernel is the one that you are referring to.
>
> The stable kernel serie I refer to can be found here:
> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-allstable.git;a=summary
>
> The branch linux-2.6.27.y contains all the fixes backported to 2.6.27.
> This includes the following commit:
> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-allstable.git;a=commit;h=5981f194641d4bcbff7e80adf393035b113f5022
>
> The referred commit it the one that fixes the make incompatibility in the 2.6.27 kernel.
> The more specific name for this kernel release is: 2.6.27.53 as this is the 53th time
> the stable team released a new stable kernel in the 2.6.27 serie.
>
> PS. Did you drop the mailing list on purpose?
> If not then I do not mind if you forward this to the list
> as it may benefit others.
>
> Sam
I did send to you directly because I am new here and didn't want to
generate too much noise in case I was completely off base. I fear
people already think I am clueless complaining about make 3.82 as it is :-)
I was unaware if the linux-2.6-allstable tree and so I am replying to
the list because I agree that your feedback may well be helpful to
others. Thanks for your time and effort.
I am looking more deeply into this issue, but it is really starting to
look like make 2.82 has a bug, as I am seeing many errors as I feared.
It could also be some other issue of course, but I don't think so at
this point.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMe//tAAoJECSpOhdQESq62msIAIibNg7ude+Pf8X8pkwuKzO0
2a9FrLPolzZjboKeBJg5U097ikZ1ywJE/TB5ZMt13KuiyKL/BPngdvKAnyfzOu5G
uzQNXO8/v13rgzkzj1A5YtoNiPeyzVw57e65EOZrxOM75Fd0K1IxacyLpfiI+eAK
ES0xZwn+YsCIJsoFEMTnFW8So0RsEkp+HESOdrxXUybC7zrPpVOEoBhD+0SMauxE
Qkl4Nrgk4mx9mfAjwMmdSyMoW+3TOlUiopYCG02Q9OsnJteDD8bepJxbSXu9cQMm
2p/Ny2PV9WCZrFguvd4KbaY7+eP55w/J9dvA4D2mjfxSLAA/CrgK/FdHoBTHW9k=
=f6S2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-30 19:01 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 ` James J. Dines [this message]
2010-08-30 20:00 ` 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
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=4C7BFFF7.6030501@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