Hello,
Got a trouble compiling seamonkey-2.49.4 using glibc-2.30
;
/home/jmp/rpmbuild/BUILD/seamonkey-2.49.4/mozilla/tools/profiler/core/platform.h:68:21:
error: 'pid_t gettid()' was declared 'extern' and later
Hello,
Seems we have another kernel-5.2, sockio problem...
Building cups-2.2.11 with glibc-2.30+sockio adjustment
(as described in SVN-20190804) cause cups build to fail
at very very early stage...
;---
In file included from
On 8/6/19 10:46 AM, Jean-Marc Pigeon via blfs-dev wrote:
On 08/06/2019 11:36 AM, Bruce Dubbs via blfs-dev wrote:
On 8/6/19 10:24 AM, Pierre Labastie via blfs-dev wrote:
Actually, it is not easy to test that: at a point in nasm life, or
libvpx
life, a release allowed compiling libvpx against
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
On 08/06/2019 11:36 AM, Bruce Dubbs via blfs-dev wrote:
On 8/6/19 10:24 AM, Pierre Labastie via blfs-dev wrote:
Actually, it is not easy to test that: at a point in nasm life, or
libvpx
life, a release allowed compiling libvpx against nasm again, and
now you see
that. But owing to the heavy
On 8/6/19 10:24 AM, Pierre Labastie via blfs-dev wrote:
Actually, it is not easy to test that: at a point in nasm life, or libvpx
life, a release allowed compiling libvpx against nasm again, and now you see
that. But owing to the heavy work on updating the book, it is too time
consuming to test
On 06/08/2019 17:05, Bruce Dubbs via blfs-dev wrote:
> On 8/6/19 8:43 AM, Jean-Marc Pigeon via blfs-dev wrote:
>> On 08/06/2019 09:38 AM, Pierre Labastie via blfs-dev wrote:
>>> On 06/08/2019 15:03, Jean-Marc Pigeon via blfs-dev wrote:
Hello,
According web page about libvpx-1.8.1,
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,
On 8/6/19 8:43 AM, Jean-Marc Pigeon via blfs-dev wrote:
On 08/06/2019 09:38 AM, Pierre Labastie via blfs-dev wrote:
On 06/08/2019 15:03, Jean-Marc Pigeon via blfs-dev wrote:
Hello,
According web page about libvpx-1.8.1, using yasm is
mandatory because:
"compiling with NASM-2.14.02 is
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
On 06/08/2019 15:43, Jean-Marc Pigeon via blfs-dev wrote:
> On 08/06/2019 09:38 AM, Pierre Labastie via blfs-dev wrote:
>> On 06/08/2019 15:03, Jean-Marc Pigeon via blfs-dev wrote:
>>> Hello,
>>>
>>> According web page about libvpx-1.8.1, using yasm is
>>> mandatory because:
>>>
>>> "compiling
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
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
On 08/06/2019 09:38 AM, Pierre Labastie via blfs-dev wrote:
On 06/08/2019 15:03, Jean-Marc Pigeon via blfs-dev wrote:
Hello,
According web page about libvpx-1.8.1, using yasm is
mandatory because:
"compiling with NASM-2.14.02 is currently broken"
I have seen no difference (naked eyes)
On 06/08/2019 15:03, Jean-Marc Pigeon via blfs-dev wrote:
> Hello,
>
> According web page about libvpx-1.8.1, using yasm is
> mandatory because:
>
> "compiling with NASM-2.14.02 is currently broken"
>
> I have seen no difference (naked eyes) between
> using nasm-2.14.02 or yasm-1.3.0
> Both
Hello,
According web page about libvpx-1.8.1, using yasm is
mandatory because:
"compiling with NASM-2.14.02 is currently broken"
I have seen no difference (naked eyes) between
using nasm-2.14.02 or yasm-1.3.0
Both build appear to be successful.
Could someone elaborate about
"currently
16 matches
Mail list logo
