[PATCH] kernel/linux: Allow user to manually enter Linux version

[ANDY KENNEDY]

> -----Original Message-----
> From: Yann E. MORIN [mailto:yann.morin.1998@gmail.com] On Behalf Of Yann E. MORIN
> Sent: Monday, January 07, 2013 3:28 PM
> To: crossgcc@sourceware.org
> Cc: ANDY KENNEDY
> Subject: Re: [PATCH] kernel/linux: Allow user to manually enter Linux version
> 
> Andy, All,
> 
> On Monday 07 January 2013 ANDY KENNEDY wrote:
> > Please forgive the ignorance, but was is a driver script?
> 
> Oh, sure! :-)
> A simple driver script could be something like:
> 
> ---8<---
> #!/bin/sh
> # Call this script something witty, eg.: my-ct-ng  ;-)
> set -e
> 
> KVER="X.Y.Z"
> KDIR="linux-${KVER}"
> KFILE="${KDIR}.tar.bz2"
> KURL="http://kernel.org/pub/..../${KFILE}"
> 
> if [ ! -f "${KDIR}" ]; then
>     if [ ! -f "${KFILE}" ]; then
>         curl "${KURL}" >"${KFILE}"
>     fi
>     tar xjf "${KFILE}"
> fi
> 
> exec ct-ng "${@}"
> ---8<---
> 
> Well, totally untested. You can refine to your case (eg. git clone +
> git checkout instead of curl...), but you get the idea.
> 
> In this case, you're using ct-ng as a "backend" for your real build system,
> which in this case is your very, very minimalist "my-ct-ng" script.
> 
> Hence, we call this script a "driver", because it "drives" a sub-process
> (here ct-ng), that is it prepares the environment, or some dirs/files...
> prior to running the actual program.
> 
> That's exactly what "gcc" (the command) is: it is a compiler driver, that
> parses its arguments to see how it was called, and what sub-process it
> should call: actuall C compiler (cc1), C++ compiler (cc1plus), linker (ld)
> and so on...
> 
> No, it's not in ct-ng's documentation, because it is not specific to
> ct-ng. It is a usually-accepted term (I guess). Sometime also referred
> to as a frontend, but it is does convey a different, although somewhat
> related. meaning.

I refer to that as a wrapper, myself, but I'll attempt to record your
terminology in the noggin' for later use.

So, I have the choice to:
	1) maintain my own patch
	2) generate and maintain my own Linux kernel downloader/unpacker/etc.

I guess I'll go with the patch technique.

Thanks again!

Andy

> 
> Regards,
> Yann E. MORIN.
> 
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'


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