This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Allow user to specify Linux kernel version


Andy,

On Thu, Oct 8, 2015 at 12:20 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>
>
>> -----Original Message-----
>> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
>> Sent: Thursday, October 08, 2015 1:56 PM
>> To: ANDY KENNEDY
>> Cc: crossgcc@sourceware.org
>> Subject: Re: [PATCH] Allow user to specify Linux kernel version
>>
>> Andy,
>>
>> On Wed, Oct 7, 2015 at 3:48 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> > Ping.
>> >
>> >> -----Original Message-----
>> >> From: ANDY KENNEDY
>> >> Sent: Tuesday, June 30, 2015 4:35 PM
>> >> To: 'crossgcc@sourceware.org'
>> >> Subject: [PATCH] Allow user to specify Linux kernel version
>> >>
>> >> Allow user to specify the Linux kernel through a manual
>> >> string entry.
>> >>
>> >> Signed-off-by:  Andy Kennedy <andy.kennedy@adtran.com>
>> >> ---
>> >> diff -Naur a/config/kernel/linux.in b/config/kernel/linux.in
>> >> --- a/config/kernel/linux.in  2015-06-30 16:25:14.183781577 -0500
>> >> +++ b/config/kernel/linux.in  2015-06-29 17:46:45.621904211 -0500
>> >> @@ -63,6 +63,20 @@
>> >>      prompt "2.6.32.67"
>> >>      help
>> >>
>> >> +config KERNEL_MANUAL
>> >> +    bool
>> >> +    prompt "Manually provide the kernel version."
>> >> +    help
>> >> +      Specify the exact kernel version you wish to use.
>> >> +
>> >> +config KERNEL_MANUAL_VER
>> >> +    string
>> >> +    prompt "Enter the kernel version"
>> >> +    depends on KERNEL_MANUAL
>> >> +    help
>> >> +      The version should be entered as 2.6.33 or 2.6.36.2 etc.  Do not provide
>> >> +      linux- before or .tar.bz2 after.
>> >> +
>> >>  config KERNEL_LINUX_CUSTOM
>> >>      bool
>> >>      prompt "custom tarball or directory"
>> >> @@ -92,6 +106,7 @@
>> >>      default "3.4.108" if KERNEL_V_3_4
>> >>      default "3.2.69" if KERNEL_V_3_2
>> >>      default "2.6.32.67" if KERNEL_V_2_6_32
>> >> +    default KERNEL_MANUAL_VER if KERNEL_MANUAL
>> >>      default "custom" if KERNEL_LINUX_CUSTOM
>> >>
>> >>  endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
>>
>> Do you think the manual version should toggle the custom version?
>> (manual, implying custom?)
>>
>> -Bryan
>
> That is not the way I use it.  What I do with this is to allow myself to
> enter a kernel version which is then pulled by CT-NG from the local
> server I have supplied, unpack it, build the headers and install them
> into the toolchain.  The custom seems to be more of a "I have a kernel
> directory unpacked on my system at /path/to/my/kernel and want to use
> that" option.  I don't want to have to unpack my kernel into some
> location, then feed that into the config at build time.  I would have to
> build in some fetch and unpack targets into my create_toolchain package
> in which I wrapper CT-NG and BuildRoot (CT-NG for the base toolchain
> then a modified version of BuildRoot to pack the libraries into the
> base toolchain).
>
> The reason for the patch is so I don't have to drag this patch forward
> continuously.  It is a simple patch, which adds additional functionality
> to CT-NT (makes it a bit more flexible).  You could easily add in a
> comment that reports this is advanced magic and I hope you know what you
> are doing -- if you don't want to support it. The patch doesn't lend
> well to future versions of CT-NG as that is an area that stays in flux
> much of the time -- So, it ends up being a manual patch for me every
> time a pull a new version of CT-NG.
>
> Andy

Would it be better to just have git/svn/cvs/bzr/etc... support for all
components?

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]