Barius Drubeck wrote:
> Shouldn't the toolchain and kernel always be compiled in the C locale?
No, see http://wiki.linuxfromscratch.org/lfs/ticket/1938
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See th
On Tuesday 30 January 2007 05:12, Ismael Luceno wrote:
> Bruce Dubbs escribió:
> > Dan Nicholson wrote:
> > How about:
> >
> > $ sed -r 's/.*(gcc version [01234567890\.]+).*/\1/' /proc/version
>
> This string depends on the locale in use when the kernel was
> compiled, so it will not work on all sy
Matthew Burgess wrote:
> Just for future reference, if you want to find out who made a change to a
> particular file, or part thereof, `svn blame' is your friend (personally, I
> don't like the connotations that 'blame' conjures up, but still, it's a
> useful tool):
'praise', 'annotate', and '
On Tuesday 30 January 2007 05:52, Dan Nicholson wrote:
> Oh, someone fixed it already (probably Matthew). Great. Someone should
> put it in the stable Errata on the website, too.
Just for future reference, if you want to find out who made a change to a
particular file, or part thereof, `svn blam
On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> http://www.linuxfromscratch.org/lfs/view/stable/prologue/hostreqs.html
>
> OK, done. I don't know if it builds automatically or not, bu tI think
> so. BTW, the text was already there.
Oh, someone fixed it already (probably Matthew). Great. Som
Dan Nicholson wrote:
> On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>> OK, I agree with Alex. Lets just do `cat /proc/version' and let it go.
>
> Bruce -
>
> While you're at it, could you fix a longstanding bug and put bison
> into the host requirements?
Do you mean in
http://www.linuxfr
On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> OK, I agree with Alex. Lets just do `cat /proc/version' and let it go.
Bruce -
While you're at it, could you fix a longstanding bug and put bison
into the host requirements? It's needed for the bash patch in Ch. 5. I
think pretty much any ve
Dan Nicholson wrote:
> On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>> Linux version 2.6.9-42.0.3.EL_lustre.1.5.97smp ([EMAIL PROTECTED]) (gcc
>> version 3.4.4 20050721 (Red Hat 3.4.4-2)) #1 SMP Fri Jan 12 17:22:43 MST
>> 2007
>>
>> And Alex:
>>
>> Linux version 2.6.18-3-686 (Debian 2.6.18-7)
Ismael Luceno wrote:
> This string depends on the locale in use when the kernel was compiled,
> so it will not work on all systems, it needs to be more generic:
>
> $ cat /proc/version
> Linux version 2.6.19.1 ([EMAIL PROTECTED]) (gcc versión 4.0.3) #1 Fri
> Dec 15 02:19:26 UYT 2006
>
> $ sed -r
On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> Linux version 2.6.9-42.0.3.EL_lustre.1.5.97smp ([EMAIL PROTECTED]) (gcc
> version 3.4.4 20050721 (Red Hat 3.4.4-2)) #1 SMP Fri Jan 12 17:22:43 MST
> 2007
>
> And Alex:
>
> Linux version 2.6.18-3-686 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruce Dubbs escribió:
> Dan Nicholson wrote:
>> On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>>> Dan Nicholson wrote:
On 1/28/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> Tushar Teredesai wrote:
>> cat /proc/version | head
Dan Nicholson wrote:
> On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>>> On 1/28/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
Tushar Teredesai wrote:
> cat /proc/version | head -n1 | cut -d" " -f1-3,5-7
>>> Pet peeve. Don't use cat to create input strea
On 1/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote:
> > On 1/28/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> >> Tushar Teredesai wrote:
> >>> cat /proc/version | head -n1 | cut -d" " -f1-3,5-7
> >
> > Pet peeve. Don't use cat to create input streams when the shell is
Dan Nicholson wrote:
> On 1/28/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
>> Tushar Teredesai wrote:
>>> cat /proc/version | head -n1 | cut -d" " -f1-3,5-7
>
> Pet peeve. Don't use cat to create input streams when the shell is
> perfectly capable on it's own with <.
vs
> sed -n 's/.*gc
Dan Nicholson wrote:
> This would seem to work (maybe the .* is too greedy).
>
> sed -n 's/.*gcc version \([^() ]*\)[() ].*/\1/p;q' < /proc/version
The intent is to show not only the gcc version, but the kernel version too.
Is there anything wrong with displaying the whole /proc/version file?
-
On 1/28/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> Tushar Teredesai wrote:
> > cat /proc/version | head -n1 | cut -d" " -f1-3,5-7
Pet peeve. Don't use cat to create input streams when the shell is
perfectly capable on it's own with <.
> On a recent Debian installation, this prints:
>
Tushar Teredesai wrote:
> cat /proc/version | head -n1 | cut -d" " -f1-3,5-7
On a recent Debian installation, this prints:
Linux version 2.6.18-3-686 2.6.18-7) ([EMAIL PROTECTED]) (gcc
This output doesn't allow one to tell if this kernel is compiled with
gcc-3.0 or later.
The full /proc/versio
Tushar Teredesai wrote:
> A bug report that I received.
> bash version-check.sh
This must work for non-executable scripts, too - so the chmod is definitely
not valid.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
U
A bug report that I received.
-- Forwarded message --
From: Vic Kovacs <[EMAIL PROTECTED]>
Date: Jan 28, 2007 6:20 AM
Subject: LFS Script suggestion
To: [EMAIL PROTECTED]
Could I advocate adding a chmod to the script in
http://www.linuxfromscratch.org/lfs/view/stable/prologue/hos
19 matches
Mail list logo
