Synopsis

When compiling we run into an error where an a wireshark enum was conflicting with a system one.
To resolve that issue we modified the file: epan/dissectors/packet-gluster.h and at line 357 we removed the next enum:

It is safe to delete it as it exists in the exact same form and same values in the system header files.
Please note that in version 1.8.15 we found the following enum, which shows that it was decided later on to just change the enum fields.

Later during compilation we got the error that there was an undefined reference to g_memmove, we copied the definition of g_memmove (see below) from packaging/macosx/native-gtk/glibconfig.h at line 81 and pasted it on the first line of the files ui/gtk/export_object_smb.c and epan/dissectors/packet-ssl-utils.c.

Finally during documentation generation we had a problem with two authors that there were Non-ASCII characters in their names so we updated the file AUTHORS and replaced the names Peter Kovář with Peter Kovar and Роман Донченко with Roman Donchenko which are strings that only contain ASCII characters.

The Problems One by One

checking for pod2man... /usr/bin/pod2man
checking for pod2html... no
configure: error: I couldn't find pod2html; make sure it's installed and in your path

Solution: sudo dnf install perl-podlators perl-Pod-Html;

checking for GTK+ - version >= 2.12.0 and < 3.0... Package gtk+-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtk+-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtk+-2.0' found
no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: error: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be compiled

Solution: sudo dnf install gtk2-devel gtk3-devel;

checking for pcap-config... no
checking for extraneous pcap header directories... not found
checking pcap.h usability... no
checking pcap.h presence... no
checking for pcap.h... no
configure: error: Header file pcap.h not found; if you installed libpcap
from source, did you also do "make install-incl", and if you installed a
binary package of libpcap, is there also a developer's package of libpcap,
and did you also install that package?

Solution: Copy the definition of g_memmove (see below) from packaging/macosx/native-gtk/glibconfig.h at line 81 and paste it on the first line of the files ui/gtk/export_object_smb.c and epan/dissectors/packet-ssl-utils.c.

After attaching the card reader on the host machine, we executed lsusb to verify that we could see the card reader on the host machine.
Among the results we got the following line indicating that the card reader was available.

Are you graduating after the summer of 2018 from a university in Europe, the Middle East or Africa? Are you interested in learning what software engineering opportunities are available for you at Google? Have you ever wanted to visit a Google office and hear directly from Google engineers about the cutting edge products they are working on?

Google is excited to invite Computer Science students graduating after the summer of 2018 to apply to Google’s new Inside Look events, which will provide an inside view into working as a Software Engineer at Google. Inside Look is committed to supporting diversity at Google and the technology industry as a whole. Students who are members of a group that is historically underrepresented in the technology field are encouraged to apply!

This year Google is continuing the Inside Look series with their next featured location – London! The two day long program will focus on the products London based Googlers are developing, and will include a mix of tech talks, panels, hands-on workshops and – in true Google fashion – plenty of food and Google goodies. Google will cover the cost of travel and accommodation for all participants.

Applications are open until 18th of June 2017 and we will contact students with the selection results by July 14th – apply today!

We wanted to give access to the chrooted environment to a folder that was part of the host machine but not part of its virtual environment.

To do so, we mounted the host machine folder on a new folder inside the chrooted area by executing the following on the host machine

#/var/lib/mock/fedora-25-x86_64/root/ is the root of the chrooted environment
mkdir /var/lib/mock/fedora-25-x86_64/root/cool_stuff/;
#/home/george/KickStart/cool_stuff/ is the folder which we want the chrooted environment to have access to
sudo mount --bind /home/george/KickStart/cool_stuff/ /var/lib/mock/fedora-25-x86_64/root/cool_stuff/;