[llvm-bugs] [Bug 38659] New: Compile issue on clang 6.0.0
via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Aug 21 06:13:43 PDT 2018
https://bugs.llvm.org/show_bug.cgi?id=38659
Bug ID: 38659
Summary: Compile issue on clang 6.0.0
Product: new-bugs
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: ndowens at yahoo.com
CC: llvm-bugs at lists.llvm.org
On i386 when building angelscript I get:
If building for amd64 I don’t. The workaround for i386 is to build using gcc
gmake[1]: Entering directory
'/wrkdirs/usr/ports/lang/angelscript/work/sdk/angelscript/projects/gnuc'
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_atomic.o -c ../../source/as_atomic.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_builder.o -c ../../source/as_builder.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_bytecode.o -c ../../source/as_bytecode.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc.o -c ../../source/as_callfunc.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_arm.o -c
../../source/as_callfunc_arm.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_mips.o -c
../../source/as_callfunc_mips.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_ppc.o -c
../../source/as_callfunc_ppc.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_ppc_64.o -c
../../source/as_callfunc_ppc_64.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_sh4.o -c
../../source/as_callfunc_sh4.cpp
c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -fPIC
-fno-strict-aliasing -o obj/as_callfunc_x86.o -c
../../source/as_callfunc_x86.cpp
fatal error: error in backend: No open frame
c++: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: i386-unknown-freebsd10.4
Thread model: posix
c++: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed
source, and associated run script.
c++: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/as_callfunc_x86-315a7c.cpp
c++: note: diagnostic msg: /tmp/as_callfunc_x86-315a7c.sh
c++: note: diagnostic msg:
********************
gmake[1]: *** [Makefile:157: obj/as_callfunc_x86.o] Error 70
gmake[1]: *** Waiting for unfinished jobs....
gmake[1]: Leaving directory
'/wrkdirs/usr/ports/lang/angelscript/work/sdk/angelscript/projects/gnuc'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make: stopped in /usr/ports/lang/angelscript
build of lang/angelscript | angelscript-2.32.0 ended at Thu Aug 16 10:19:44 CST
2018
build time: 00:00:15
!!! build failure encountered !!!
[00:01:51] Error: Build failed in phase: build
[00:01:51] Cleaning up
[00:01:52] Unmounting file systems
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180821/78ef0cb3/attachment-0001.html>
More information about the llvm-bugs
mailing list