On 09/08/2010 05:56 AM, Martin Zajíc wrote:
[putolin]
> So i've rewrite gcc pass2 with last svn and it's working.
>
> I have another question about testing error.
> I try to make LOG with '{} 2>&1 | tee $BUILD_DIR/LOG_$PROGRAM.log'
> but when I did it how can I test it for errors, becouse
On Wednesday 08 September 2010 05:56:23 Martin Zajíc wrote:
> I have another question about testing error.
> I try to make LOG with '{} 2>&1 | tee $BUILD_DIR/LOG_$PROGRAM.log'
> but when I did it how can I test it for errors, becouse '$?' not
> working even if the script inside ending with 'exi
2010/9/8 Martin Zajíc :
> So i've rewrite gcc pass2 with last svn and it's working.
>
> I have another question about testing error.
> I try to make LOG with '{} 2>&1 | tee $BUILD_DIR/LOG_$PROGRAM.log'
> but when I did it how can I test it for errors, becouse '$?' not
> working even if the sc
>> It's not 100% but for now all comands working I checked it. Only
>> problem is that GCC (all gcc binaries) is bad linked, but only GCC
>> nothink else.
>>
>
> So, since this is a school project, all *you* have to do is to work
> out what you did wrongly, or missed. Assuming your controlling
>
2010/9/7 Martin Zajíc :
>>
> It's not 100% but for now all comands working I checked it. Only
> problem is that GCC (all gcc binaries) is bad linked, but only GCC
> nothink else.
>
So, since this is a school project, all *you* have to do is to work
out what you did wrongly, or missed. Assuming
> On Sun, 2010-09-05 at 13:22 +0200, Martin Zajíc wrote:
>> And errors in configure, make, make install scripts detecting
>> automatically and stop build.
>
> Are you sure? Until recently, that's what I *thought* my scripts were
> doing, until one of the aforementioned "obscure problems" convinced
On Sun, 2010-09-05 at 13:22 +0200, Martin Zajíc wrote:
> And errors in configure, make, make install scripts detecting
> automatically and stop build.
Are you sure? Until recently, that's what I *thought* my scripts were
doing, until one of the aforementioned "obscure problems" convinced me
otherw
>> Sometimes people accidentally miss one of the packages,
>> or build it but fail to install it.
>
> Or more commonly with scripted builds, the script fails to recognise
> that a command has failed, and continues with the next step.
But think is I have everythink logged and doing packages one by
On Sat, 2010-09-04 at 20:05 +0100, Ken Moffat wrote:
> Sometimes people accidentally miss one of the packages,
> or build it but fail to install it.
Or more commonly with scripted builds, the script fails to recognise
that a command has failed, and continues with the next step.
Scripted builds *
> I can't comment on the *comments* in that script, but
> a quick look suggests you are doing the same things as
> I do. So, perhaps the problem is elsewhere.
>
> We can see that 'make' is apparently found and executable,
> but gcc is not. The first steps are: take a sample of packages
> from c
2010/9/4 Martin Zajíc :
> Hi, me again
> I have another issue. I'am sure it's my fault but I can't solve it.
> I'am building LFS as my school project and i'am trying write all of it
> in set of bash scripts.
>
> So I've write scripts for chapter 5 and in chapter 6 I found issue
> that I've do some
Hi, me again
I have another issue. I'am sure it's my fault but I can't solve it.
I'am building LFS as my school project and i'am trying write all of it
in set of bash scripts.
So I've write scripts for chapter 5 and in chapter 6 I found issue
that I've do something wrong probably in adjusting tool
12 matches
Mail list logo
