sudo pip3 install pyopenjtalk エラー インストールできません

error

1sudo pip3 install pyopenjtalk 2Collecting pyopenjtalk 3 Using cached pyopenjtalk-0.3.3.tar.gz (1.6 MB) 4 Installing build dependencies ... done 5 Getting requirements to build wheel ... error 6 error: subprocess-exited-with-error 7 8 × Getting requirements to build wheel did not run successfully. 9 │ exit code: 1 10 ╰─> [21 lines of output] 11 Traceback (most recent call last): 12 File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module> 13 main() 14 File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main 15 json_out['return_val'] = hook(**hook_input['kwargs']) 16 File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel 17 return hook(config_settings) 18 File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 162, in get_requires_for_build_wheel 19 return self._get_build_requires( 20 File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 143, in _get_build_requires 21 self.run_setup() 22 File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 158, in run_setup 23 exec(compile(code, __file__, 'exec'), locals()) 24 File "setup.py", line 190, in <module> 25 File "/usr/lib/python3.10/subprocess.py", line 503, in run 26 with Popen(*popenargs, **kwargs) as process: 27 File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ 28 self._execute_child(args, executable, preexec_fn, close_fds, 29 File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child 30 raise child_exception_type(errno_num, err_msg, err_filename) 31 FileNotFoundError: [Errno 2] No such file or directory: 'cmake' 32 [end of output] 33 34 note: This error originates from a subprocess, and is likely not a problem with pip. 35error: subprocess-exited-with-error 36 37× Getting requirements to build wheel did not run successfully. 38│ exit code: 1 39╰─> See above for output. 40 41note: This error originates from a subprocess, and is likely not a problem with pip.