From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/scripts
Date: Sat, 03 Jan 2009 09:50:52 +0100 [thread overview]
Message-ID: <1230972652.8886.52.camel@linux-yrgm.site> (raw)
In-Reply-To: <20090103070426.GA7300@cloud.net.au>
l?r 2009-01-03 klockan 18:04 +1100 skrev Hamish Moffatt:
> On Fri, Jan 02, 2009 at 03:44:22PM +0000, ulf at uclibc.org wrote:
> > Changeset:
> > Modified: trunk/buildroot/scripts/get_linux_config.sh
> > ===================================================================
> > --- trunk/buildroot/scripts/get_linux_config.sh 2009-01-02 12:01:49 UTC (rev 24647)
> > +++ trunk/buildroot/scripts/get_linux_config.sh 2009-01-02 15:44:18 UTC (rev 24648)
> [...]
> > +LINUX_MAJOR_VERSION=${LINUX26_DIR:10:2}
> > +LINUX_MINOR_VERSION=${LINUX26_DIR:13}
>
> This isn't very robust. Can we do better?
>
This is the reasoning behind the patch.
LINUX26_DIR is the basename of the directory containing linux
and this is currently always "linux-2.6.$(MAJOR).$(MINOR)"
MAJOR is always in the range of 20..30 at the moment
asn I believe it will be safe until linux-2.6.100.
If you believe otherwise we need to find another solution.
The script CAN be improved by only processing the
"*linux-2.6.*.config" files in the first loop.
Only if you do not get any .config file in the second
loop, you revert to the old behaviour.
I know, this requires that the linux config is "well behaved"
I.E: called "*linux-2.6.*"
If you do "make linux26-update" to generate it,
it should become "well-behaved".
The previous version would, if you selected kernel 2.6.25.3
and xxx-linux-2.6.25.1.config and xxx-linux-2.6.28 existed,
use the latter, while the former is more appropriate.
As I see it, the goal is to use the config version
which is as close to the real version, but not
of a higher version than the kernel.
Several board support packages does not implement
versioning, so you cannot do a lot about them
except hope for the second loop.
Feel free to improve as long as you meet the goal above.
>
> Hamish
next prev parent reply other threads:[~2009-01-03 8:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 15:44 [Buildroot] svn commit: trunk/buildroot/scripts ulf at uclibc.org
2009-01-03 7:04 ` Hamish Moffatt
2009-01-03 8:50 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 16:24 jacmet at uclibc.org
2009-02-02 7:19 ulf at uclibc.org
2009-02-02 7:18 ulf at uclibc.org
2009-01-25 23:09 ulf at uclibc.org
2009-01-22 23:10 ulf at uclibc.org
2009-01-22 23:05 ulf at uclibc.org
2009-01-16 22:45 ulf at uclibc.org
2009-01-15 23:17 ulf at uclibc.org
2009-01-13 18:43 ulf at uclibc.org
2009-01-12 7:45 ulf at uclibc.org
2009-01-12 7:43 ulf at uclibc.org
2009-01-11 20:37 ulf at uclibc.org
2009-01-10 0:26 ulf at uclibc.org
2009-01-11 13:23 ` Peter Korsgaard
2009-01-03 16:59 ulf at uclibc.org
2008-12-23 17:51 wberrier at uclibc.org
2008-10-22 5:19 jacmet at uclibc.org
2008-05-01 15:21 ninevoltz at uclibc.org
2008-04-06 10:01 ulf at uclibc.org
2008-04-01 9:53 jacmet at uclibc.org
2008-03-11 13:14 ninevoltz at uclibc.org
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=1230972652.8886.52.camel@linux-yrgm.site \
--to=ulf.samuelsson@atmel.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.