Pedro Ortigão pmo at
Wed Feb 27 15:01:37 PST 2002

Sorry about my english in the last post. I'll try to remember to read my 
posts before hiting the send button :-)

Anyway I just thought the problem might be due to optimisation settings 
because I compile (almost) everything with -O3 -march=i686. Anyway, nALFS 
and expat were both compiled with those settings and that might be one 
possible reason.

I haven't been able to reproduce untill now - so it's probably not 

Pedro Ortigão

Neven Has wrote:

> On Wed, Feb 27, 2002 at 04:54:13PM +0000, Pedro Ortigão wrote:
>> I'm not sure I'll be albe to reproduce that behaviour. It has happenned a
>> couple of times. What happens is that somewhere alogin the way the
>> running status mark ('>') is updated any longer, ie, keeps pointing to
>> the same part of the profile, even though it is already executing the
>> next parts. In the end you get some parts of the profile marked has
>> completed ('#') and some like they haven't been marked to run... and the
>> parent "process" marked has ('@'). In any case all the profile was
>> correctly built.
> I see.
>> Hope this helps. I'll try to reproduce the behaviour. Maybe the profile
>> is too long, it follows the same design of your LFS3.1 the parent XML is
>> goes like this:
> <snip>
> I don't know how the size of the profile can make a difference,
> but who knows, it might.
> It'll be tricky to find a problem if it can't be reproduced (and I have
> built _a_lot_ of different profiles without noticing something like this),
> but I'll look into it.
> Thanks again,
> Neven

Unsubscribe: send email to listar at
and put 'unsubscribe alfs-discuss' in the subject header of the message

More information about the alfs-discuss mailing list