google-perftools | Clone of google-perftools

I have had success with the perf tool, which lets me know which functions are taking the most time. On my Pynq board specifically, the executable is found in /usr/lib/linux-tools-4.15.0-20 which is not by default in PATH. I also used FlameGraph for excellent visualization of the call graph.

Yes. That's the result of running a build system implemented in scons expecting only python2.

If you're stuck here's what you can do to be able to compile until the gem project pushes their Python 3 + SCons changes.

In python 3, subprocess communicate is going to return a bytes-like object here: gem5 SConstruct which is what sets CXX_version (python bytes-like docs: PIPE and communicate)

That bytes-like object gets find called on it with a str argument, but it should be converted to bytes for finding in a bytes-like object. Probably the readCommand function that returned the communicate output should be the one to convert the output from bytes-like to str.

What version of python and SCons was this run with? My guess is python 3 was used and the SConstruct for that build is not compatible with python 3.

Probably try with python2.7 for now.

One way to do that is through virtualenv

I solve it by update my OS from Ubuntu 16.04 to 19.04. It just works fine.

The error is telling you that the function call:

The fix was committed soon afterwards at e70a2a53ebac09ba5aacf706066589510c624c13

I'had reported this at: https://www.mail-archive.com/gem5-dev@gem5.org/msg27897.html

The offending commit is 59e3585a84ef172eba57c9936680c0248f9a97db and the fix is likely to just add the missing function declaration to the header.

Always check the dev mailing list for build failures, and give more relevant details about your system when doing so: gem5 git SHA, your OS version, compiler version.

Google do provide the managed SSL solution using Let's Encrypt with auto-renewal.

https://cloud.google.com/load-balancing/docs/ssl-certificates#managed-certs

What was the reason that you have to manage this on your own?

Yes you need to include the headers because you need the declarations for the functions.

For your second question, I would suggest you read their documentation

It's effectively certain that your issue is caused by DOS newlines.

The giveaway is this error:

' is already registered with AC_CONFIG_FILES./usr/src/ports/autoconf2.5/autoconf2.5-2.69-3.noarch/src/autoconf-2.69/lib/autoconf/status.m4:288: AC_CONFIG_FILES is

The line beginning with ' is already registered with implies that the cursor was sent back to the beginning of the line partway through writing the line to the console -- the exact behavior of printing a string read from a DOS-format text file while it expecting it to be in UNIX format.