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 it is not
the case.

The error is within:
mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/v
p9_i
mpl.cc


seamonkey-
2.53.2/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codec
s/vp
9/vp9_impl.cc:858:17: error: ‘struct vpx_svc_ref_frame_config’ has
no
member named ‘frame_flags’
    858 |         sf_conf.frame_flags[layer_idx] = layer_flags;
        |               ^~~~~~~~~~~

field  frame_flags is not defined within /usr/include/vpx/vp8cx.h,
(structure vpx_svc_ref_frame_config)

seamonkey-2.49.4 is compiling fine... but routine where the
defective
code is located, is under/hiden by
#ifdef LIBVPX_SVC

This ifdef is not present in 2.53.2 code.

I noticed, seamonkey 2020-05-25 do not list libvpx
in recommended anymore (version 2.49.4 does include
libvpx as recommended)

Tried to removed libvpx, but 2.53.2 is requesting libvpx > 1.5.0

Obviously, I am missing something.

1) Could the someone in the list confirm he is successful
     to compile seamonkey within 2020-05-25 (gcc-10,
     libvpx-1.8.2,rustc-1.42.0, etc.)??
2) Why libvpx is not in the seamonkey "required".
3) is there a mozconfig parameter involved?
4) wild idea of your own? :-}}

Thanks for any help or suggestions, myself out of idea for
now..

--
You have seen "Linux from scratch" and looking for ISO files
www.osukiss.org

Hi Jean-Marc,

When I did the update to Seamonkey last, I didn't see any references
to
configure looking for libvpx in the configure output. In previous
versions of Seamonkey, problems were encountered when using system
libvpx (if I'm not mistaken, Mozilla / the Seamonkey developers are
using an older version within their source code). It looks like
libvpx
was built as part of the build procedure for seamonkey. I haven't
built
Seamonkey with a GCC-10 system though. Doing a 'grep libvpx' on my
build
log from May 3rd shows that it doesn't look for libvpx and builds
its
own version later on in the process.

--with-system-libvpx should be removed from mozconfig if you don't
have
that already. It looks like the last time I built it was May 3rd,
2020,
when I updated the book to Seamonkey-2.53.2.

An important thing to remember is that Seamonkey-2.49 was using
Firefox-36's codebase, and Seamonkey-2.53 uses Firefox 60's
codebase,
which now necessitates the usage of rust and potentially an internal
snapshot of libvpx

Can you post your mozconfig please? I'm curious as to whether you're
doing anything different than us. Here's my mozconfig:

        cat > mozconfig << "EOF"
mk_add_options MOZ_MAKE_FLAGS="-j4"
ac_add_options --enable-startup-notification
ac_add_options --enable-system-sqlite
ac_add_options --with-system-libevent
ac_add_options --with-system-nspr
ac_add_options --with-system-nss
ac_add_options --with-system-icu

ac_add_options --prefix=/usr
ac_add_options --enable-application=suite
ac_add_options --disable-crashreporter
ac_add_options --disable-updater
ac_add_options --disable-tests
ac_add_options --enable-optimize="-O2"
ac_add_options --enable-strip
ac_add_options --enable-install-strip
ac_add_options --enable-official-branding
ac_add_options --enable-system-ffi
ac_add_options --enable-system-cairo
ac_add_options --enable-system-pixman
ac_add_options --with-pthreads
ac_add_options --with-system-bz2
ac_add_options --with-system-jpeg
ac_add_options --with-system-png
ac_add_options --with-system-zlib
EOF

I've got the exact same flags as are in the book, with the exception
of
some things being disabled (I do have GConf, dbus-glib, wireless-
tools,
and startup-notification installed).
Double checked..
about libvpx, if I remove it (via rpm -e --nodeps), seamonkey
complain...

DEBUG: configure:10348: /usr/bin/gcc -std=gnu99 -c   -fno-strict-
aliasing -fno-math-errno -pthread   conftest.c 1>&5
DEBUG: configure:10468: checking if app-specific confvars.sh exists
DEBUG: configure:11601: checking for gtk+-3.0 >= 3.4.0 gtk+-unix-print-
3.0 glib-2.0 gobject-2.0 gio-unix-2.0
DEBUG: configure:11608: checking MOZ_GTK3_CFLAGS
DEBUG: configure:11613: checking MOZ_GTK3_LIBS
DEBUG: configure:11684: checking for gtk+-2.0 >= 2.18.0 gtk+-unix-
print-2.0 glib-2.0 >= 2.22 gobject-2.0 gio-unix-2.0 gdk-x11-2.0
DEBUG: configure:11691: checking MOZ_GTK2_CFLAGS
DEBUG: configure:11696: checking MOZ_GTK2_LIBS
DEBUG: configure:12848: /usr/bin/gcc -std=gnu99 -c   -fno-strict-
aliasing -fno-math-errno -pthread   conftest.c 1>&5
DEBUG: configure:13030: checking for vpx >= 1.5.0
DEBUG: configure: error: Library requirements (vpx >= 1.5.0) not met;
consider adjusting the PKG_CONFIG_PATH environment variable if your
libraries are in a nonstandard prefix so pkg-config can find them.


Please could you confirm,  libvpx is NOT installed
on your dev station? (include file missing)....?
Then how can I  double check rust is provinding libvpx?


About my mozconfig I am "aligned" with book
(see atachment)

I will use YOUR mozconfig to check if that make a
difference.

Many Thanks for your help...

I can confirm I did have libvpx installed:

Mon 24 Feb 2020 04:52:45 PM CST libvpx-1.8.2
Sun 03 May 2020 02:34:21 PM CDT seamonkey-2.53.2.source

In my update log, here are the lines surrounding the area where your libvpx detection was:

checking if app-specific confvars.sh exists... /sources/seamonkey-2.53.2.source/seamonkey-2.53.2/mozilla/../suite/confvars.sh checking for gtk+-3.0 >= 3.4.0 gtk+-unix-print-3.0 glib-2.0 gobject-2.0 gio-unix-2.0 ... yes checking MOZ_GTK3_CFLAGS... -pthread -I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking MOZ_GTK3_LIBS... -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 checking for gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gio-unix-2.0 gdk-x11-2.0... yes checking MOZ_GTK2_CFLAGS... -pthread -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 -I/usr/include/atk-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking MOZ_GTK2_LIBS... -lgtk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lfontconfig -lfreetype -lgio-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -lcairo -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
checking for libstartup-notification-1.0 >= 0.8... yes

Looking at your mozconfig file, it does look like you're specifying this:

# Comment out following options if you have not installed
# recommended dependencies:
ac_add_options --enable-system-sqlite
ac_add_options --with-system-libevent
ac_add_options --with-system-libvpx
ac_add_options --with-system-nspr


We don't have --with-system-libvpx in the book because of problems similar to this one, which also affected Firefox and Thunderbird previously. Mozilla has a specially patched version of libvpx included within the source tree that Seamonkey builds as part of it's process.

Can you remove "ac_add_options --with-system-libvpx" and try rebuilding Seamonkey? :)

--
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