On 08-11-2014 06:56, Fernando de Oliveira wrote:
> On 08-11-2014 00:39, Bruce Dubbs wrote:
>> Fernando de Oliveira wrote:
>>> On 07-11-2014 17:50, Fernando de Oliveira wrote:
>>>
>>>
>>>> In my LFS7.1 host (SVN-20120311)
>>>>
>>>>
>>>>> 2.  It took a long time to launch the first time, but I suppose that's
>>>>> OK.  It seems slower, e.g. reply to to this message is my first reply
>>>>> with SM, but that may resolve itself.
>>>>
>>>> This is the result of the non-optimization. Worse, it regularly makes
>>>> something taking 100% of one CPU for a dozen seconds.
>>>>
>>>> First launch is slow for the same reason. Latest 33.0.3 that I have just
>>>> updated builds correctly with enable-optimize and starts much faster.
>>>> Still have to build and test in this host.
>>>>
>>>> Probably, next SM version will be better in all that.
>>>
>>> Very disappointing.
>>>
>>> FF-33.0.3 *does* need disable-optimize here. Perhaps the difference is
>>> elsewhere, perhaps a new python version in the dev system, or other new
>>> package.
>>>
>>> ... boot the the dev system and start
>>> comparing.
>>
>> What are the issues when building with enable-optimize?
> 
> In a couple of ours, after having breakfast and other personal business,
> will start with BLFS business, and first thing will be trying to reply
> this. Thanks for the interest.

s/ours/hours/

Subject is seamonkey, but error is in *firefox-33.0.3*.

Parts of build log attached.

Left configuration and install parts.

Optimization error starts at line 571, key word is "Executing" at the
beginning of line (search ^Executing).

Your (Bruce, who asked, and anybody else, please) help is much appreciated.

I will start by comparing python versions in the two systems:

LFS7.1 host (SVN-20120311) (error occurs)

LFS7.6 (no error with enable-optimize

-- 
[]s,
Fernando

Attachment: firefox-33.0.3-enable-optimize-python-error-2014.11.07-18h20m37s.log.xz
Description: Binary data

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to