Gcc11 failed to build #369
Comments
|
I don't know why I use C + + 17. I can't compile with C + + 14 and can't detect V8 |
|
You should build with c++11. |
|
@jcoffland If I build with c++11, an error like the following occurs and I can't even get it to detect properly |
|
Yes, you have to either rebuild cbang with |
|
I have used the official fork version of v8 to compile and install, and compile cbang, still useless |
|
Are you sure C! compiled with v8? During the config phase you should see: Possibly with out On Debian I install the |
|
OK, can you confirm your version number of V8? I have to compile and install because I am Gentoo |
|
Debian installs version 7.8 build 279 patch 23. Any version 7.8 will probably work. |
|
I've just pushed a change that fixes the |
|
@jcoffland I'm currently trying to build a cbang under v8 7.8.285, since the two components are linked, I don't think it's necessary to open a separate issue, I'm getting the following error: |
|
When I try to build this project itself, the error is reported: |
|
I pushed a commit that should fix the above c! build problem. The link errors maybe related. |
|
@jcoffland Now there are still link errors. Let me check whether there is a problem with the system. It is strange that I use Qt5 on Gentoo and will report such link errors. |
|
I still have this error, I have Qt and icu installed, there shouldn't be a problem, I'm running KDE what does camsim do? Can I disable it ? Or disable V8 while the system is present? |
|
@jcoffland It seems that I have found the root cause of the link error. During the link, the ICU version used by V8 is different from the ICU version installed in the system, which leads me to overwrite the ICU version of the system by mistake (when I use CP). The possible solution may be to adopt static link, or use the system ICU (but I can't find this method), or disable the ICU of V8 |
|
Last solution: disable v8 |
|
@jack9603301 Here is a link to an Arch Linux PKGBUILD file that might help you figure out how to build v8 with the system icu. You need to use c++17 for cbang and camotics to recognize the latest v8 (10.5.84). There was 1 minor change I needed to make to camotics to get it to build with c++17. See this pull request |
freebsd-git
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
Jul 22, 2022
C! builds with the latest v8, but it is not usable by CAMotics. It must be build with c++17 standard. Obtained from: CauldronDevelopmentLLC/CAMotics#369 Fixes: 0db7465
freebsd-git
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
Jul 22, 2022
After the latest upgrade of v8, C! and CAMotics must be built with c++17 standard. Obtained from: CauldronDevelopmentLLC/CAMotics#369 Fixes: 0db7465 Reported by: pkg-fallout
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I finally tried to build this project, scons reported the following error:
Does anyone know how to solve it? I use Gentoo source code Linux distribution!
The text was updated successfully, but these errors were encountered: