Am 31.05.2018 um 00:35 schrieb Anthony D. Baye:
> Every time I think about checking for replies here, something else takes my
> attention.

Well, as a consequence your pastebin upload of the config.log has
expired, so you may need to poste that one again.

> Here is the entire make log:

Two things I've noticed so far:

(1) There is an extra `-D_GNU_SOURCE=1 -D_REENTRANT -pthread` sequence
in the compiler flags that doesn't look familiar; while I don't think
it's causing the trouble, I wonder why they're in there, and whether you
really need them.

(2) This one:

> ..../config.h:258:0: note: this is the location of the previous definition
>  #define PACKAGE_VERSION "3.8.0-alpha"

As mentioned in `./README.md`, please *DO NOT* build from the master
branch, but rather from tagged versions. That way, we can reconstruct
_exactly_ what version you downloaded and are now trying to build.

Tagged versions can be found here:

https://github.com/POV-Ray/povray/tags


To further diagnose your issue, please proceed as follows:

(1) Create a new directory, and download v3.8.0-alpha.9606898 there, so
that we know exactly what source code version you have, and that it is
unblemished pure original code.

(2) Try building again. Please make sure to store the output of all the
steps (prebuild, configure, make) somewhere for later reference.

If that still doesn't work, and results in the same error messages:

(3) In `source/backend/povray.cpp`, please insert new lines before and
after line 61 (`#ifdef POV_CPUINFO_H`), reading `#warning "testing
POV_CPUINFO_H in povray.cpp"` and  `#warning "POV_CPUINFO_H defined in
povray.cpp"`, respectively.

(4) In `platform/x86/cpuid.h`, please insert new lines before and after
line 37 (`#ifndef POVRAY_CPUID_H`), reading `#warning "testing for
first-time visit of cpuid.h"` and  `#warning "first-time visit of
cpuid.h"`, respectively.

(5) Run `make` again and post the output. Please also include the
(up-to-date) config.log again. Verbatim output of the configure step
would also be neat (while the very same info can be gleaned from
config.log, that's a bit tedious).


Also, you still didn't let us know the OS you're using (distro and
version, at the very least); I guess it /may/ also be inferred from
`config.log`, but I'd prefer not having to dig.

Post a reply to this message