質問編集履歴
4
エラーの内容を変更しました。
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -108,7 +108,7 @@
|
|
|
108
108
|
|
|
109
109
|
(venv) [hirayama@habomai AlphAction]$ python setup.py build develop
|
|
110
110
|
|
|
111
|
-
which: no hipcc in (/home/hirayama/test/AlphAction/venv/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/hirayama/.local/bin:/home/hirayama/bin)
|
|
111
|
+
which: no hipcc in (/opt/gcc/7.3.0/bin:/home/hirayama/test/AlphAction/venv/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/hirayama/.local/bin:/home/hirayama/bin)
|
|
112
112
|
|
|
113
113
|
running build
|
|
114
114
|
|
|
@@ -120,43 +120,77 @@
|
|
|
120
120
|
|
|
121
121
|
warnings.warn(msg.format('we could not find ninja.'))
|
|
122
122
|
|
|
123
|
-
/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/utils/cpp_extension.py:245: UserWarning:
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
!! WARNING !!
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
132
|
-
|
|
133
|
-
Your compiler (g++ 4.8.5) may be ABI-incompatible with PyTorch!
|
|
134
|
-
|
|
135
|
-
Please use a compiler that is ABI-compatible with GCC 5.0 and above.
|
|
136
|
-
|
|
137
|
-
See https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html.
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
See https://gist.github.com/goldsborough/d466f43e8ffc948ff92de7486c5216d6
|
|
142
|
-
|
|
143
|
-
for instructions on how to install GCC 5 or higher.
|
|
144
|
-
|
|
145
|
-
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
!! WARNING !!
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
warnings.warn(ABI_INCOMPATIBILITY_WARNING.format(compiler))
|
|
154
|
-
|
|
155
123
|
building 'detector.nms.nms_cuda' extension
|
|
156
124
|
|
|
157
125
|
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include -I/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/TH -I/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/THC -I/opt/cuda/10.2.89/include -I/home/hirayama/test/AlphAction/venv/include -I/opt/pyenv/versions/3.7.7/include/python3.7m -c detector/nms/src/nms_cuda.cpp -o build/temp.linux-x86_64-3.7/detector/nms/src/nms_cuda.o -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=nms_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
|
|
158
126
|
|
|
159
|
-
|
|
127
|
+
detector/nms/src/nms_cuda.cpp: 関数 ‘at::Tensor nms(const at::Tensor&, float)’ 内:
|
|
128
|
+
|
|
129
|
+
detector/nms/src/nms_cuda.cpp:4:39: 警告: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
|
|
130
|
+
|
|
131
|
+
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
|
|
132
|
+
|
|
133
|
+
^
|
|
134
|
+
|
|
135
|
+
detector/nms/src/nms_cuda.cpp:9:3: 備考: in expansion of macro ‘CHECK_CUDA’
|
|
136
|
+
|
|
137
|
+
CHECK_CUDA(dets);
|
|
138
|
+
|
|
139
|
+
^
|
|
140
|
+
|
|
141
|
+
In file included from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/ATen/Tensor.h:11:0,
|
|
142
|
+
|
|
143
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/ATen/Context.h:4,
|
|
144
|
+
|
|
145
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/ATen/ATen.h:5,
|
|
146
|
+
|
|
147
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
|
|
148
|
+
|
|
149
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
|
|
150
|
+
|
|
151
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
|
|
152
|
+
|
|
153
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
|
|
154
|
+
|
|
155
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
|
|
156
|
+
|
|
157
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
|
|
158
|
+
|
|
159
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/all.h:4,
|
|
160
|
+
|
|
161
|
+
from /home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/torch/extension.h:4,
|
|
162
|
+
|
|
163
|
+
from detector/nms/src/nms_cuda.cpp:2:
|
|
164
|
+
|
|
165
|
+
/home/hirayama/test/AlphAction/venv/lib/python3.7/site-packages/torch/include/ATen/core/TensorBody.h:262:30: 備考: ここで宣言されています
|
|
166
|
+
|
|
167
|
+
DeprecatedTypeProperties & type() const {
|
|
168
|
+
|
|
169
|
+
^~~~
|
|
170
|
+
|
|
171
|
+
detector/nms/src/nms_cuda.cpp:4:23: エラー: ‘AT_CHECK’ was not declared in this scope
|
|
172
|
+
|
|
173
|
+
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
|
|
174
|
+
|
|
175
|
+
^
|
|
176
|
+
|
|
177
|
+
detector/nms/src/nms_cuda.cpp:4:23: 備考: in definition of macro ‘CHECK_CUDA’
|
|
178
|
+
|
|
179
|
+
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
|
|
180
|
+
|
|
181
|
+
^~~~~~~~
|
|
182
|
+
|
|
183
|
+
detector/nms/src/nms_cuda.cpp:4:23: 備考: suggested alternative: ‘DCHECK’
|
|
184
|
+
|
|
185
|
+
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
|
|
186
|
+
|
|
187
|
+
^
|
|
188
|
+
|
|
189
|
+
detector/nms/src/nms_cuda.cpp:4:23: 備考: in definition of macro ‘CHECK_CUDA’
|
|
190
|
+
|
|
191
|
+
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
|
|
192
|
+
|
|
193
|
+
^~~~~~~~
|
|
160
194
|
|
|
161
195
|
error: command 'gcc' failed with exit status 1
|
|
162
196
|
|
3
エラーの内容を読み取りました。
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -162,6 +162,8 @@
|
|
|
162
162
|
|
|
163
163
|
```
|
|
164
164
|
|
|
165
|
+
ここではgccのversionが5以下なのが原因といっていますが、module loadなどで見るとgccのversionは７なのに対してなんでなんだろうと疑問です。
|
|
166
|
+
|
|
165
167
|
|
|
166
168
|
|
|
167
169
|
### その後ちょっと進んでしまってのエラー
|
2
gccについて検証しました。
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -164,7 +164,7 @@
|
|
|
164
164
|
|
|
165
165
|
|
|
166
166
|
|
|
167
|
-
### その後ちょっと進んでしまっ
|
|
167
|
+
### その後ちょっと進んでしまってのエラー
|
|
168
168
|
|
|
169
169
|
とはいえと思いそのままpreparationのファイルを特定のディレクトリにおいて
|
|
170
170
|
|
|
@@ -196,6 +196,40 @@
|
|
|
196
196
|
|
|
197
197
|
|
|
198
198
|
|
|
199
|
+
### 試したこと
|
|
200
|
+
|
|
201
|
+
gccの存在確認とバージョンを見てみる。
|
|
202
|
+
|
|
203
|
+
|
|
204
|
+
|
|
205
|
+
```
|
|
206
|
+
|
|
207
|
+
(venv) [hirayama@habomai demo]$ which gcc
|
|
208
|
+
|
|
209
|
+
/usr/bin/gcc
|
|
210
|
+
|
|
211
|
+
(venv) [hirayama@habomai demo]$ gcc -v
|
|
212
|
+
|
|
213
|
+
組み込み spec を使用しています。
|
|
214
|
+
|
|
215
|
+
COLLECT_GCC=gcc
|
|
216
|
+
|
|
217
|
+
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
|
|
218
|
+
|
|
219
|
+
ターゲット: x86_64-redhat-linux
|
|
220
|
+
|
|
221
|
+
configure 設定: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux
|
|
222
|
+
|
|
223
|
+
スレッドモデル: posix
|
|
224
|
+
|
|
225
|
+
gcc バージョン 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC)
|
|
226
|
+
|
|
227
|
+
```
|
|
228
|
+
|
|
229
|
+
|
|
230
|
+
|
|
231
|
+
|
|
232
|
+
|
|
199
233
|
### 解決してほしいこと
|
|
200
234
|
|
|
201
235
|
buildができるようにしてほしいです。
|
1
その他のエラーを追加しました。
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -162,6 +162,40 @@
|
|
|
162
162
|
|
|
163
163
|
```
|
|
164
164
|
|
|
165
|
+
|
|
166
|
+
|
|
167
|
+
### その後ちょっと進んでしまったところ
|
|
168
|
+
|
|
169
|
+
とはいえと思いそのままpreparationのファイルを特定のディレクトリにおいて
|
|
170
|
+
|
|
171
|
+
demo.py imput.mp4を実行しようとしました。
|
|
172
|
+
|
|
173
|
+
|
|
174
|
+
|
|
175
|
+
```
|
|
176
|
+
|
|
177
|
+
(venv) [hirayama@habomai demo]$ python demo.py input.mp4
|
|
178
|
+
|
|
179
|
+
Traceback (most recent call last):
|
|
180
|
+
|
|
181
|
+
File "demo.py", line 14, in <module>
|
|
182
|
+
|
|
183
|
+
from action_predictor import AVAPredictorWorker
|
|
184
|
+
|
|
185
|
+
File "/home/hirayama/test/AlphAction/demo/action_predictor.py", line 3, in <module>
|
|
186
|
+
|
|
187
|
+
from AlphAction.structures.bounding_box import BoxList
|
|
188
|
+
|
|
189
|
+
ModuleNotFoundError: No module named 'AlphAction'
|
|
190
|
+
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
すると以上のような結果になってしまって、buildでうまくいってないからかなとおもっています。
|
|
194
|
+
|
|
195
|
+
まずは、buildのエラーを解決したいです。
|
|
196
|
+
|
|
197
|
+
|
|
198
|
+
|
|
165
199
|
### 解決してほしいこと
|
|
166
200
|
|
|
167
201
|
buildができるようにしてほしいです。
|