I think the given syntax will work but here is a simple working example that
includes ''case'' in the way you were looking for. this does the "ls"
command back to back followed by the switch statement followed by another
"ls" command:
time { ls && ls && case $(uname -m) in x86_64) echo "HELLO" ;
Simon Geard wrote:
> On Tue, 2010-10-26 at 15:54 -0500, Bruce Dubbs wrote:
>> If you are referring to the tar commands in section 5.5.1, what is not
>> clear? There is no chdir command before the tar commands. Section 5.3
>> clearly says:
>>
>> b. Change to the directory created when the packag
On Tue, 2010-10-26 at 15:54 -0500, Bruce Dubbs wrote:
> If you are referring to the tar commands in section 5.5.1, what is not
> clear? There is no chdir command before the tar commands. Section 5.3
> clearly says:
>
> b. Change to the directory created when the package was extracted.
> c. Fol
Brett Mahar wrote:
>> What we are doing is creating gmp/, mpfr/, mpc/ directories
>> _within_ the gcc directoriy. We do this because any host using a
>> version of gcc older than 4.5 will NOT have all of these required
>> programs, so we will build them in to the temporary gcc.
> This is where
Brett Mahar wrote these words on 10/26/10 19:04 CST:
> Section 5.3 contradicts 5.5.
> Hence confusion.
Only if you read too much into things. Think about it. The instructions
say to unpack the package tarball. If one cannot determine that the
package tarball means the package listed in the header
On 27 October 2010 06:54, Bruce Dubbs wrote:
> Brett Mahar wrote:
>
>> I read all sections of the book through twice before starting.
>> I did not skip any sections.
>> I have a fine command of the English language, it is the only language I
>> speak.
>> It is not clear.
>
> What is not clear? T
On Tue, Oct 26, 2010 at 5:22 PM, wrote:
> [Sorry for the top post, I'm on my blackberry...]
> It's sparse files being expanded. When using tar for making backups, you
> should use "--sparse" or "-S".
>
>
> --Original Message--
> From: xinglp
> Sender: lfs-support-boun...@linuxfromscratch
[Sorry for the top post, I'm on my blackberry...]
It's sparse files being expanded. When using tar for making backups, you should
use "--sparse" or "-S".
--Original Message--
From: xinglp
Sender: lfs-support-boun...@linuxfromscratch.org
To: lfs-support@linuxfromscratch.org
ReplyTo: LFS
Brett Mahar wrote:
> I read all sections of the book through twice before starting.
> I did not skip any sections.
> I have a fine command of the English language, it is the only language I
> speak.
> It is not clear.
What is not clear? The book? I'm willing to clarify text in the book,
but n
On Wed, Oct 27, 2010 at 05:33:58AM +1000, Brett Mahar wrote:
>
> If you disagree, do not bother replying.
Less of that attitude, please.
I'm *not* commenting on the discussion itself. These lists are
all about discussion. Often, the book gets better as a result -
but it can take a long time,
On 10/26/10 08:32, Neal Murphy wrote:
>
> Randy, you are correct. The information is all there. It probably works well
> for someone with a keen grasp of written English and someone who is already
> familiar with the build process.
>
> But the book is still wrong because it does not clearly and e
On 26 October 2010 23:37, Randy McMurchy wrote:
> On 10/26/2010 7:09 AM, Brett Mahar wrote:
>> I agree, there is no way that I could figure that out from reading the
>> book.
>
> Then you failed to read Section 5.3 "General Compilation Instructions".
> This has been discussed many times, and it ha
On 10/26/10 02:52, Simon Geard wrote:
> On Mon, 2010-10-25 at 22:14 -0700, lfs wrote:
>> So the question is, Should I create the gcc-build directory and *then*
>> untar gmp,mpfr, mpc, from that(gcc-build) directory
> No. Remember the rule - before starting on a particular page, extract
> it's tar
On Tue, Oct 26, 2010 at 11:31:54PM +0800, xinglp wrote:
> When I finished the lfs build, install some extra software, do some config.
>
> I use "tar -jcf ../lfs-someday.tar.bz2 *" to backup it. and then
> restore it to another part by "tar -xf ../lfs-someday.tar.bz2
> ../somewhere".
>
> Then I us
Neal Murphy wrote these words on 10/26/10 10:32 CST:
> I really don't understand the resistance to changing
> "GCC now requires the GMP, MPFR and MPC packages. As these packages
> may not be included in your host distribution, they will be built
> with GCC:"
> to something like
> "
On Tuesday 26 October 2010 09:37:01 Randy McMurchy wrote:
> On 10/26/2010 7:09 AM, Brett Mahar wrote:
> > I agree, there is no way that I could figure that out from reading the
> > book.
>
> Then you failed to read Section 5.3 "General Compilation Instructions".
> This has been discussed many times
When I finished the lfs build, install some extra software, do some config.
I use "tar -jcf ../lfs-someday.tar.bz2 *" to backup it. and then
restore it to another part by "tar -xf ../lfs-someday.tar.bz2
../somewhere".
Then I use df to check the size of them. The restored lfs is bigger
than where
On 10/26/2010 7:09 AM, Brett Mahar wrote:
> I agree, there is no way that I could figure that out from reading the
> book.
Then you failed to read Section 5.3 "General Compilation Instructions".
This has been discussed many times, and it has always been determined
that we expect readers to actuall
>
> Editors, can we perhaps add some extra text to the GCC Pass 1
> instructions (and perhaps a short reminder to Pass 2 as well)? Right
> now, all the book has to say is:
>
> "GCC now requires the GMP, MPFR and MPC packages. As these
> packages may not be included in your host distribution,
On Mon, 2010-10-25 at 22:14 -0700, lfs wrote:
> So the question is, Should I create the gcc-build directory and *then*
> untar gmp,mpfr, mpc, from that(gcc-build) directory
No. Remember the rule - before starting on a particular page, extract
it's tarball, and cd into the directory. So, when extr
20 matches
Mail list logo
