サーバー構築 – ページ 2 – ぷすぅ～ぷすぅ～

エラー内容

make 時に以下のエラー


cc -DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -m64 -c src/Mayaqua/Cfg.c -o tmp/objs/Mayaqua/Cfg.o
cc: error: unrecognized command line option ‘-m64’
Makefile:101: recipe for target 'tmp/objs/Mayaqua/Cfg.o' failed
make: *** [tmp/objs/Mayaqua/Cfg.o] Error 1

cc -DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -m64 -c src/Mayaqua/Cfg.c -o tmp/objs/Mayaqua/Cfg.o

cc: error: unrecognized command line option ‘-m64’

Makefile:101: recipe for target 'tmp/objs/Mayaqua/Cfg.o' failed

make: *** [tmp/objs/Mayaqua/Cfg.o] Error 1

-m64 は、インテルの64bit用の命令を使ってコンパイルする命令。今回は、ARM系のcpuなのでこのオプションは使えない。

./configure で作成された、Makefile ファイルを直接いじって-m64とい部分を全て削除か、
一番近そうなオプションで、cpuの種類を指定する。
NanoPI M4なら
-march=armv8-a+crypto+crc

Makefile は以下のように編集した
$ diff Makefile.org Makefile


65c65
< OPTIONS_COMPILE_DEBUG=-D_DEBUG -DDEBUG -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -g -fsigned-char -m64
---
> OPTIONS_COMPILE_DEBUG=-D_DEBUG -DDEBUG -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -g -fsigned-char -march=armv8-a+crypto+crc
67c67
< OPTIONS_LINK_DEBUG=-g -fsigned-char -m64 -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz
---
> OPTIONS_LINK_DEBUG=-g -fsigned-char -march=armv8-a+crypto+crc -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz
69c69
< OPTIONS_COMPILE_RELEASE=-DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -m64
---
> OPTIONS_COMPILE_RELEASE=-DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -march=armv8-a+crypto+crc
71c71
< OPTIONS_LINK_RELEASE=-O2 -fsigned-char -m64 -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz
---
> OPTIONS_LINK_RELEASE=-O2 -fsigned-char -march=armv8-a+crypto+crc -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz

65c65

< OPTIONS_COMPILE_DEBUG=-D_DEBUG -DDEBUG -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -g -fsigned-char -m64

---

> OPTIONS_COMPILE_DEBUG=-D_DEBUG -DDEBUG -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -g -fsigned-char -march=armv8-a+crypto+crc

67c67

< OPTIONS_LINK_DEBUG=-g -fsigned-char -m64 -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz

---

> OPTIONS_LINK_DEBUG=-g -fsigned-char -march=armv8-a+crypto+crc -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz

69c69

< OPTIONS_COMPILE_RELEASE=-DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -m64

---

> OPTIONS_COMPILE_RELEASE=-DNDEBUG -DVPN_SPEED -DUNIX -DUNIX_LINUX -DCPU_64 -D_REENTRANT -DREENTRANT -D_THREAD_SAFE -D_THREADSAFE -DTHREAD_SAFE -DTHREADSAFE -D_FILE_OFFSET_BITS=64 -I./src/ -I./src/Cedar/ -I./src/Mayaqua/ -O2 -fsigned-char -march=armv8-a+crypto+crc

71c71

< OPTIONS_LINK_RELEASE=-O2 -fsigned-char -m64 -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz

---

> OPTIONS_LINK_RELEASE=-O2 -fsigned-char -march=armv8-a+crypto+crc -lm -ldl -lrt -lpthread -lssl -lcrypto -lreadline -lncurses -lz

-m64 を、-march=armv8-a+crypto+crc に変更した。

tomcat が、catalina.sh からだと起動できて、daemon.sh からだと起動できない。
最初に、apache-tomcat-9.0.0.M22 w/ jdk1.8.0_131 でやったけどだめで、

apache-tomcat-9.0.0.M9 w/ jdk1.8.0_91
apache-tomcat-9.0.0.M9 w/ jdk1.7.0_80
apache-tomcat-8.5.16 w/ jdk1.7.0_80

のパターンでもだめ。
osは、Linux version 2.6.32-696.6.3.el6.x86_64 (mockbuild@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Wed Jul 12

エラーは

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x00007fd0aa0eb461, pid=31954, tid=140534257276672
#
# JRE version:  (7.0_80-b15) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# j  java.lang.Object.<clinit>()V+0
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x0000000001fd8800):  JavaThread "Unknown thread" [_thread_in_Java, id=31954, stack(0x00007fff4d754000,0x00007fff4d854000)]

siginfo:si_signo=SIGBUS: si_errno=0, si_code=2 (BUS_ADRERR), si_addr=0x00007fff4d84bdf0

Registers:

......

RSP=0x00007fff4d850df0 is pointing into the stack for thread: 0x0000000001fd8800
RBP=0x00007fff4d850e30 is pointing into the stack for thread: 0x0000000001fd8800
RSI=0x00007fd0aa0eb360 is at code_begin+0 in an Interpreter codelet
method entry point (kind = zerolocals)  [0x00007fd0aa0eb360, 0x00007fd0aa0eb6a0]  832 bytes
RDI=0x00007fff4d850ee0 is pointing into the stack for thread: 0x0000000001fd8800
R8 =0x00007fd0aa0eb360 is at code_begin+0 in an Interpreter codelet
method entry point (kind = zerolocals)  [0x00007fd0aa0eb360, 0x00007fd0aa0eb6a0]  832 bytes
R9 =0x00007fff4d850fc8 is pointing into the stack for thread: 0x0000000001fd8800
R10=0x00007fd0aa0db45f is at begin+0 in a stub
StubRoutines::call_stub [0x00007fd0aa0db45f, 0x00007fd0aa0db547[ (232 bytes)
R11=0x00007fd0add35d40: <offset 0x601d40> in /opt/jdk1.7.0_80//jre/lib/amd64/server/libjvm.so at 0x00007fd0ad734000
R12=0x0000000000000000 is an unknown value
R13=0x0000000750c02b20 is pointing into object: 0x0000000750c02ae0
{constMethod} 
 - klass: {other class}
 - constants:       0x0000000750c01c78 constant pool [79] for 'java/lang/Object' cache=0x0000000750ca9ea8
bci_from(0x750c02b20) = 0; print_codes():
R14=0x00007fff4d850e38 is pointing into the stack for thread: 0x0000000001fd8800
R15=0x0000000001fd8800 is a thread


Stack: [0x00007fff4d754000,0x00007fff4d854000],  sp=0x00007fff4d850df0,  free space=1011k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
j  java.lang.Object.<clinit>()V+0
v  ~StubRoutines::call_stub
V  [libjvm.so+0x6020a5]  JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x365
V  [libjvm.so+0x600b08]  JavaCalls::call(JavaValue*, methodHandle, JavaCallArguments*, Thread*)+0x28
V  [libjvm.so+0x5c4f7a]  instanceKlass::call_class_initializer(Thread*)+0xca
V  [libjvm.so+0x5c51d4]  instanceKlass::initialize_impl(instanceKlassHandle, Thread*)+0x234
V  [libjvm.so+0x5c562a]  instanceKlass::initialize(Thread*)+0x6a
V  [libjvm.so+0x5c546b]  instanceKlass::initialize_impl(instanceKlassHandle, Thread*)+0x4cb
V  [libjvm.so+0x5c562a]  instanceKlass::initialize(Thread*)+0x6a
V  [libjvm.so+0x95dd62]  Threads::create_vm(JavaVMInitArgs*, bool*)+0x402
V  [libjvm.so+0x63b2e4]  JNI_CreateJavaVM+0x74

.......

# A fatal error has been detected by the Java Runtime Environment:

# SIGBUS (0x7) at pc=0x00007fd0aa0eb461, pid=31954, tid=140534257276672

# JRE version: (7.0_80-b15) (build )

# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# j java.lang.Object.<clinit>()V+0

# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

# If you would like to submit a bug report, please visit:

# http://bugreport.java.com/bugreport/crash.jsp

--------------- T H R E A D ---------------

Current thread (0x0000000001fd8800): JavaThread "Unknown thread" [_thread_in_Java, id=31954, stack(0x00007fff4d754000,0x00007fff4d854000)]

siginfo:si_signo=SIGBUS: si_errno=0, si_code=2 (BUS_ADRERR), si_addr=0x00007fff4d84bdf0

Registers:

......

RSP=0x00007fff4d850df0 is pointing into the stack for thread: 0x0000000001fd8800

RBP=0x00007fff4d850e30 is pointing into the stack for thread: 0x0000000001fd8800

RSI=0x00007fd0aa0eb360 is at code_begin+0 in an Interpreter codelet

method entry point (kind = zerolocals) [0x00007fd0aa0eb360, 0x00007fd0aa0eb6a0] 832 bytes

RDI=0x00007fff4d850ee0 is pointing into the stack for thread: 0x0000000001fd8800

R8 =0x00007fd0aa0eb360 is at code_begin+0 in an Interpreter codelet

method entry point (kind = zerolocals) [0x00007fd0aa0eb360, 0x00007fd0aa0eb6a0] 832 bytes

R9 =0x00007fff4d850fc8 is pointing into the stack for thread: 0x0000000001fd8800

R10=0x00007fd0aa0db45f is at begin+0 in a stub

StubRoutines::call_stub [0x00007fd0aa0db45f, 0x00007fd0aa0db547[ (232 bytes)

R11=0x00007fd0add35d40: <offset 0x601d40> in /opt/jdk1.7.0_80//jre/lib/amd64/server/libjvm.so at 0x00007fd0ad734000

R12=0x0000000000000000 is an unknown value

R13=0x0000000750c02b20 is pointing into object: 0x0000000750c02ae0

{constMethod}

- klass: {other class}

- constants: 0x0000000750c01c78 constant pool [79] for 'java/lang/Object' cache=0x0000000750ca9ea8

bci_from(0x750c02b20) = 0; print_codes():

R14=0x00007fff4d850e38 is pointing into the stack for thread: 0x0000000001fd8800

R15=0x0000000001fd8800 is a thread

Stack: [0x00007fff4d754000,0x00007fff4d854000], sp=0x00007fff4d850df0, free space=1011k

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

j java.lang.Object.<clinit>()V+0

v ~StubRoutines::call_stub

V [libjvm.so+0x6020a5] JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x365

V [libjvm.so+0x600b08] JavaCalls::call(JavaValue*, methodHandle, JavaCallArguments*, Thread*)+0x28

V [libjvm.so+0x5c4f7a] instanceKlass::call_class_initializer(Thread*)+0xca

V [libjvm.so+0x5c51d4] instanceKlass::initialize_impl(instanceKlassHandle, Thread*)+0x234

V [libjvm.so+0x5c562a] instanceKlass::initialize(Thread*)+0x6a

V [libjvm.so+0x5c546b] instanceKlass::initialize_impl(instanceKlassHandle, Thread*)+0x4cb

V [libjvm.so+0x5c562a] instanceKlass::initialize(Thread*)+0x6a

V [libjvm.so+0x95dd62] Threads::create_vm(JavaVMInitArgs*, bool*)+0x402

V [libjvm.so+0x63b2e4] JNI_CreateJavaVM+0x74

.......

のようなエラー

答えは、ここ

起動パラメタに”-Xss2m”を追加した

カテゴリー: サーバー構築

[softeher] ARM系のCPUのSoC搭載SBCで、ソースからsofteherをビルド

エラー内容

[tomcat] jsvc からだと起動できない