Re: [blfs-dev] seamonkey-2.53.2, 2020-05-25 libvpx, rationnal?

On Tue, 2020-05-26 at 12:50 -0500, Douglas R. Reno via blfs-dev wrote: > On 5/26/20 12:35 PM, Jean-Marc Pigeon via blfs-dev wrote: > > Hello, > > > > Trying to compile seamonkey-2.53.2 and beeing not successful. > > at first I was thinking about a gcc10 problem, but it is not > > the case. > > >

Re: [blfs-dev] seamonkey-2.53.2, 2020-05-25 libvpx, rationnal?

On 5/26/20 1:44 PM, Jean-Marc Pigeon wrote: On Tue, 2020-05-26 at 12:50 -0500, Douglas R. Reno via blfs-dev wrote: On 5/26/20 12:35 PM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Trying to compile seamonkey-2.53.2 and beeing not successful. at first I was thinking about a gcc10 problem, but

Re: [blfs-dev] seamonkey-2.53.2, 2020-05-25 libvpx, rationnal?

On Tue, 2020-05-26 at 12:50 -0500, Douglas R. Reno via blfs-dev wrote: > On 5/26/20 12:35 PM, Jean-Marc Pigeon via blfs-dev wrote: > > Hello, > > > > Trying to compile seamonkey-2.53.2 and beeing not successful. > > at first I was thinking about a gcc10 problem, but it is not > > the case. > > >

Re: [blfs-dev] seamonkey-2.53.2, 2020-05-25 libvpx, rationnal?

On 5/26/20 12:35 PM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Trying to compile seamonkey-2.53.2 and beeing not successful. at first I was thinking about a gcc10 problem, but it is not the case. The error is within: mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_i

[blfs-dev] seamonkey-2.53.2, 2020-05-25 libvpx, rationnal?

Hello, Trying to compile seamonkey-2.53.2 and beeing not successful. at first I was thinking about a gcc10 problem, but it is not the case. The error is within: mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_i mpl.cc seamonkey-

Re: [blfs-dev] seamonkey and html5, vimeo

On 08/06/2019 11:03 AM, Douglas R. Reno via blfs-dev wrote: On 8/6/19 9:52 AM, Jean-Marc Pigeon via blfs-dev wrote: On 08/06/2019 10:34 AM, Douglas R. Reno via blfs-dev wrote: On 8/6/19 9:15 AM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Could someone confirm he is able to display html5

Re: [blfs-dev] seamonkey and html5, vimeo

On 8/6/19 9:52 AM, Jean-Marc Pigeon via blfs-dev wrote: On 08/06/2019 10:34 AM, Douglas R. Reno via blfs-dev wrote: On 8/6/19 9:15 AM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Could someone confirm he is able to display html5 video using seamonkey (2.49.4)? Trying to display vimeo.com,

Re: [blfs-dev] seamonkey and html5, vimeo

On 08/06/2019 10:34 AM, Douglas R. Reno via blfs-dev wrote: On 8/6/19 9:15 AM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Could someone confirm he is able to display html5 video using seamonkey (2.49.4)? Trying to display vimeo.com, seamonkey say player error... (obviously there is not

Re: [blfs-dev] seamonkey and html5, vimeo

On 8/6/19 9:15 AM, Jean-Marc Pigeon via blfs-dev wrote: Hello, Could someone confirm he is able to display html5 video using seamonkey (2.49.4)? Trying to display vimeo.com, seamonkey say player error... (obviously there is not flashplayer within BLFS anymore). Notes: 1) using seamonkey I am

[blfs-dev] seamonkey and html5, vimeo

Hello, Could someone confirm he is able to display html5 video using seamonkey (2.49.4)? Trying to display vimeo.com, seamonkey say player error... (obviously there is not flashplayer within BLFS anymore). Notes: 1) using seamonkey I am able to watch youtube video. 2) using falkon (3.0.1) , I

Re: [blfs-dev] seamonkey-2.48

On Tue, Aug 01, 2017 at 06:50:00PM -0500, Bruce Dubbs wrote: > Bruce Dubbs wrote: > > I am having trouble with seamonkey-2.48. It builds, but does not display > > properly. The icons and menus do not display until the mouse cursor moves > > over them and then is still erratic. The menu items do

Re: [blfs-dev] seamonkey-2.48

Bruce Dubbs wrote: I am having trouble with seamonkey-2.48. It builds, but does not display properly. The icons and menus do not display until the mouse cursor moves over them and then is still erratic. The menu items do not work consistently. I used the same mozconfig that I used for

Re: [blfs-dev] seamonkey-2.48

Bruce Dubbs wrote: I am having trouble with seamonkey-2.48. It builds, but does not display properly. The icons and menus do not display until the mouse cursor moves over them and then is still erratic. The menu items do not work consistently. I used the same mozconfig that I used for

[blfs-dev] seamonkey-2.48

I am having trouble with seamonkey-2.48. It builds, but does not display properly. The icons and menus do not display until the mouse cursor moves over them and then is still erratic. The menu items do not work consistently. I used the same mozconfig that I used for seamonkey-2.46 which

Re: [blfs-dev] seamonkey-2.46 compile problems

On Wed, Feb 22, 2017 at 8:02 PM, Bruce Dubbs wrote: > Sami Tarazi wrote: >> >> seamonkey-2.46 fails to compile. >> >> I was able to compile it as follows: >> >> 1- change line 73 of mozilla/build/autoconf/icu.m4 from >> version=`sed -n 's/^[[:space:]] (long line)

[blfs-dev] seamonkey-2.46 compile problems

seamonkey-2.46 fails to compile. I was able to compile it as follows: 1- change line 73 of mozilla/build/autoconf/icu.m4 from version=`sed -n 's/^[[:space:]] (long line) to version=`sed -n 's/^[[[:space:]]] - 2- sed -e s/_EVENT_SIZEOF/EVENT__SIZEOF/ \ -i

Re: [blfs-dev] seamonkey

On 29/12/2016 06:15, Bruce Dubbs wrote: > After a lot of trials I've finally got seamonkey to run without a seg fault. > To do it, I had to disable system icu. I'm using icu-58.2. > > I seem to recall something about this at one time, but I can't find it right > now. > > There are a few

Re: [blfs-dev] seamonkey

On Wed, Dec 28, 2016 at 11:15 PM, Bruce Dubbs wrote: > After a lot of trials I've finally got seamonkey to run without a seg > fault. To do it, I had to disable system icu. I'm using icu-58.2. > > I seem to recall something about this at one time, but I can't find it >

Re: [blfs-dev] seamonkey

> From: Bruce Dubbs <bruce.du...@gmail.com> > Date: Wed, 28 Dec 2016 23:15:38 -0600 > Subject: [blfs-dev] seamonkey > > After a lot of trials I've finally got seamonkey to run without a seg > fault. To do it, I had to disable system icu. I'm using icu-58.2. > > I

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

18. Nov 2016 08:49 by d...@linuxfromscratch.org: > > > On 11/17/2016 02:47 AM, > wil...@tuta.io> wrote: >> Some Chromium versions break with system libs but 54.0.284.100 works >> fine with the above system libs >> > Last time I looked, .90, all of these were broken in some way. libvpx >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 11/17/2016 02:47 AM, wil...@tuta.io wrote: Some Chromium versions break with system libs but 54.0.284.100 works fine with the above system libs Last time I looked, .90, all of these were broken in some way. libvpx required --enable-experimental (I forget what extended feature it actually

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

> The API whose change prevents libreoffice to build was announced. There is a > fix in the book. > > The segfaults with the mozilla apps is due to a regression. This kind of > things happen... There is a patch which allows firefox and thunderbird to run. > I have to build seamonkey (never done

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 16/11/2016 21:37, Ken Moffat wrote: On Wed, Nov 16, 2016 at 09:28:46PM +0100, Pierre Labastie wrote: So, I propose to revert back to 58.1 (with the patch of course). Would it be OK? Note that apps compiled with 57.1 seem to work with the 58.1 library, at least FF and TB. No need to recompile

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 16/11/2016 21:36, Douglas R. Reno wrote: On Wed, Nov 16, 2016 at 2:28 PM, Pierre Labastie > wrote: On 16/11/2016 09:31, wil...@tuta.io wrote: > 14. Nov 2016 20:35 by renodr2...@gmail.com

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

Pierre Labastie wrote: On 16/11/2016 09:31, wil...@tuta.io wrote: 14. Nov 2016 20:35 by renodr2...@gmail.com : On Sun, Nov 13, 2016 at 5:44 PM, Bruce Dubbs > wrote: Douglas R. Reno wrote:

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Wed, Nov 16, 2016 at 09:28:46PM +0100, Pierre Labastie wrote: > > So, I propose to revert back to 58.1 (with the patch of course). Would it be > OK? Note that apps compiled with 57.1 seem to work with the 58.1 library, at > least FF and TB. No need to recompile AFAICT. > Sounds good to me -

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Wed, Nov 16, 2016 at 2:28 PM, Pierre Labastie wrote: > On 16/11/2016 09:31, wil...@tuta.io wrote: > > 14. Nov 2016 20:35 by renodr2...@gmail.com >: > > > > > > > > On Sun, Nov 13, 2016 at 5:44 PM, Bruce Dubbs

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 16/11/2016 09:31, wil...@tuta.io wrote: > 14. Nov 2016 20:35 by renodr2...@gmail.com : > > > > On Sun, Nov 13, 2016 at 5:44 PM, Bruce Dubbs > wrote: > > Douglas R. Reno wrote: > >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

14. Nov 2016 20:35 by renodr2...@gmail.com: > > > On Sun, Nov 13, 2016 at 5:44 PM, Bruce Dubbs <> bruce.du...@gmail.com> > > wrote: > >> Douglas R. Reno wrote: >> >>> On Sun, Nov 13, 2016 at 4:07 PM, Ken Moffat <>>> zarniwh...@ntlworld.com>>> >>> > wrote: >>> On Sun, Nov 13, 2016 at

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 5:44 PM, Bruce Dubbs wrote: > Douglas R. Reno wrote: > >> On Sun, Nov 13, 2016 at 4:07 PM, Ken Moffat >> wrote: >> >>> On Sun, Nov 13, 2016 at 12:55:01PM -0600, DJ Lucas wrote: >>> On Sat, Nov 12, 2016 at 06:56:08PM

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

> Date: Mon, 14 Nov 2016 15:00:13 + > From: Ken Moffat <zarniwh...@ntlworld.com> > Subject: Re: [blfs-dev] Seamonkey, Firefox, > and Thunderbird all cause segfaults with the latest SVN build > > On Mon, Nov 14, 2016 at 09:23:11AM +, akhiezer wrote: > > >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Mon, Nov 14, 2016 at 09:23:11AM +, akhiezer wrote: > > Date: Sun, 13 Nov 2016 21:59:07 + > > From: Ken Moffat <zarniwh...@ntlworld.com> > > Subject: Re: [blfs-dev] Seamonkey, Firefox, > > and Thunderbird all cause segfaults with the latest SVN build >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

> Date: Sun, 13 Nov 2016 21:59:07 + > From: Ken Moffat <zarniwh...@ntlworld.com> > Subject: Re: [blfs-dev] Seamonkey, Firefox, > and Thunderbird all cause segfaults with the latest SVN build > . . > > I'm surprised that links cuts it at all

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

Douglas R. Reno wrote: On Sun, Nov 13, 2016 at 4:07 PM, Ken Moffat wrote: On Sun, Nov 13, 2016 at 12:55:01PM -0600, DJ Lucas wrote: On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: OK, I think I found the culprit: went back to ICU-57.1, compiled FF

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

If possible, I'd suggest using the in tree copy for now. --DJ On November 13, 2016 5:34:50 PM CST, "Douglas R. Reno" wrote: >On Sun, Nov 13, 2016 at 4:07 PM, Ken Moffat >wrote: > >> On Sun, Nov 13, 2016 at 12:55:01PM -0600, DJ Lucas wrote: >> >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 4:07 PM, Ken Moffat wrote: > On Sun, Nov 13, 2016 at 12:55:01PM -0600, DJ Lucas wrote: > > > > > > > On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: > > > > > > > > > > OK, I think I found the culprit: went back to ICU-57.1,

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Nov 13, 2016 4:05 PM, "Ken Moffat" wrote: > > On Sun, Nov 13, 2016 at 02:51:23PM -0600, Douglas R. Reno wrote: > > > > Any disadvantages if I downgrade to ICU-57.1? I have SO many updates out in > > BLFS land and one in LFS! Links won't cut it forever. > > AFAICS

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 12:55:01PM -0600, DJ Lucas wrote: > > > > > On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: > > > > > > > > OK, I think I found the culprit: went back to ICU-57.1, compiled FF > > against it, and no segfaults for about one hour... > > > > I'll try to

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 02:51:23PM -0600, Douglas R. Reno wrote: > > Any disadvantages if I downgrade to ICU-57.1? I have SO many updates out in > BLFS land and one in LFS! Links won't cut it forever. AFAICS (ignoring the "clean up" changes in 58.1 which have caused problems), the main other

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 03:29:14PM +0100, Pierre Labastie wrote: > On 13/11/2016 09:27, Pierre Labastie wrote: > > On 12/11/2016 23:33, Ken Moffat wrote: > > > On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: > > > > > Let me try to get back to GTK-3.20 (I'm happy I use porg, so

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Nov 13, 2016 2:47 PM, "Ken Moffat" wrote: > > On Sun, Nov 13, 2016 at 09:27:48AM +0100, Pierre Labastie wrote: > > > > Sorry for not being clear. I meant to "answer" the sentence "Let me try to get > > back to GTK-3.20. Then I'll try previous sqlite, previous NSS, and

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sat, Nov 12, 2016 at 09:22:15AM +0100, Pierre Labastie wrote: (replying to the earlier post) > > For the record, my DE/DM is LXDE/openbox. The engine for the search field is > google (the default). I tried to move to duckduckgo, but it opened the > duckduckgo page. I could search something,

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 11/13/2016 08:29 AM, Pierre Labastie wrote: On 13/11/2016 09:27, Pierre Labastie wrote: On 12/11/2016 23:33, Ken Moffat wrote: On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: Let me try to get back to GTK-3.20 (I'm happy I use porg, so that I can shuffle versions ;).

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sun, Nov 13, 2016 at 09:27:48AM +0100, Pierre Labastie wrote: > > Sorry for not being clear. I meant to "answer" the sentence "Let me try to get > back to GTK-3.20. Then I'll try previous sqlite, previous NSS, and previous > harfbuzz". > > I should have said something like "whatever the

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 13/11/2016 09:27, Pierre Labastie wrote: On 12/11/2016 23:33, Ken Moffat wrote: On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: Let me try to get back to GTK-3.20 (I'm happy I use porg, so that I can shuffle versions ;). Then I'll try previous sqlite, previous NSS, and

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 12/11/2016 23:33, Ken Moffat wrote: > On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: >> >>> >>> Let me try to get back to GTK-3.20 (I'm happy I use porg, so that I can >>> shuffle versions ;). Then I'll try previous sqlite, previous NSS, and >>> previous >>> harfbuzz. >>> >>

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Nov 12, 2016 3:42 PM, "Pierre Labastie" wrote: > > On 12/11/2016 09:22, Pierre Labastie wrote: > > On 12/11/2016 05:20, Ken Moffat wrote: > >> On Fri, Nov 11, 2016 at 10:59:28PM +0100, Pierre Labastie wrote: > >>> On 11/11/2016 20:01, Douglas R. Reno wrote: >

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 11/12/2016 11:56 AM, Pierre Labastie wrote: On 12/11/2016 09:22, Pierre Labastie wrote: On 12/11/2016 05:20, Ken Moffat wrote: On Fri, Nov 11, 2016 at 10:59:28PM +0100, Pierre Labastie wrote: On 11/11/2016 20:01, Douglas R. Reno wrote: Greetings, I am unable to get Seamonkey, Firefox,

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Sat, Nov 12, 2016 at 06:56:08PM +0100, Pierre Labastie wrote: > > > > > Let me try to get back to GTK-3.20 (I'm happy I use porg, so that I can > > shuffle versions ;). Then I'll try previous sqlite, previous NSS, and > > previous > > harfbuzz. > > > Nothing worked... > Could it have

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 12/11/2016 09:22, Pierre Labastie wrote: > On 12/11/2016 05:20, Ken Moffat wrote: >> On Fri, Nov 11, 2016 at 10:59:28PM +0100, Pierre Labastie wrote: >>> On 11/11/2016 20:01, Douglas R. Reno wrote: Greetings, I am unable to get Seamonkey, Firefox, or Thunderbird to work properly

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 12/11/2016 05:20, Ken Moffat wrote: > On Fri, Nov 11, 2016 at 10:59:28PM +0100, Pierre Labastie wrote: >> On 11/11/2016 20:01, Douglas R. Reno wrote: >>> Greetings, >>> >>> I am unable to get Seamonkey, Firefox, or Thunderbird to work properly with >>> the latest SVN of BLFS. >>> >>> They all

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On Fri, Nov 11, 2016 at 10:59:28PM +0100, Pierre Labastie wrote: > On 11/11/2016 20:01, Douglas R. Reno wrote: > > Greetings, > > > > I am unable to get Seamonkey, Firefox, or Thunderbird to work properly with > > the latest SVN of BLFS. > > > > They all segfault with references to libpthread

Re: [blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

On 11/11/2016 20:01, Douglas R. Reno wrote: > Greetings, > > I am unable to get Seamonkey, Firefox, or Thunderbird to work properly with > the latest SVN of BLFS. > > They all segfault with references to libpthread (expected), libnspr4, libnss, > and libxul. > > I've recompiled the entire NSS

[blfs-dev] Seamonkey, Firefox, and Thunderbird all cause segfaults with the latest SVN build

Greetings, I am unable to get Seamonkey, Firefox, or Thunderbird to work properly with the latest SVN of BLFS. They all segfault with references to libpthread (expected), libnspr4, libnss, and libxul. I've recompiled the entire NSS stack (p11-kit -> sqlite -> nspr -> nss), and when I get home,

Re: [blfs-dev] seamonkey

On 07-11-2014 22:41, Bruce Dubbs wrote: Fernando de Oliveira wrote: 5. The book says: This package does not come with a test suite. However, if X is running it can be launched from the build directory before installing with the command line: moz-build-dir/mozilla/dist/seamonkey/seamonkey

Re: [blfs-dev] seamonkey

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

Re: [blfs-dev] seamonkey

On Fri, Nov 07, 2014 at 12:53:33AM -0600, Bruce Dubbs wrote: I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5 hours, the build crashed with messages like: jsapi.cpp:(.text+0x1db8): undefined reference to `u_init_52' but there are a

Re: [blfs-dev] seamonkey

Ken Moffat wrote: On Fri, Nov 07, 2014 at 12:53:33AM -0600, Bruce Dubbs wrote: I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5 hours, the build crashed with messages like: jsapi.cpp:(.text+0x1db8): undefined reference to `u_init_52' but

Re: [blfs-dev] seamonkey

On Fri, Nov 07, 2014 at 10:35:04AM -0600, Bruce Dubbs wrote: It was late last night, but I had seen that reference. I rebuilt SM with 'ac_add_options --without-intl-api' because I really didn't want to take the time to build icu and I don't need any i18n on that system. This morning it had

Re: [blfs-dev] seamonkey

On 07-11-2014 13:35, Bruce Dubbs wrote: Ken Moffat wrote: On Fri, Nov 07, 2014 at 12:53:33AM -0600, Bruce Dubbs wrote: I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5 hours, the build crashed with messages like:

Re: [blfs-dev] seamonkey

Fernando de Oliveira wrote: On 07-11-2014 13:35, Bruce Dubbs wrote: Ken Moffat wrote: On Fri, Nov 07, 2014 at 12:53:33AM -0600, Bruce Dubbs wrote: I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5 hours, the build crashed with messages

Re: [blfs-dev] seamonkey

On 07-11-2014 14:37, Bruce Dubbs wrote: Fernando de Oliveira wrote: On 07-11-2014 13:35, Bruce Dubbs wrote: Ken Moffat wrote: On Fri, Nov 07, 2014 at 12:53:33AM -0600, Bruce Dubbs wrote: I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5

Re: [blfs-dev] seamonkey

Fernando de Oliveira wrote: 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

Re: [blfs-dev] seamonkey

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.

[blfs-dev] seamonkey

I'm trying to build seamonkey-2.30 on an older 686 running a 2 year old version of LFS. After about 3.5 hours, the build crashed with messages like: jsapi.cpp:(.text+0x1db8): undefined reference to `u_init_52' but there are a tone of these with the suffix _52. I do have the option set: