#71112 closed defect (duplicate)
hunspell: fatal error: 'cstdlib' file not found
Reported by: | gautham81928 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | sequoia arm64 | Cc: | |
Port: | hunspell |
Description
It installs some of the ports that are needed by codeblocks but it stops installing them after it reaches hunspell, and shows an error saying it failed to build hunspell
Attachments (1)
Change History (7)
comment:1 Changed 3 weeks ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sequoia arm64 added |
---|---|
Port: | hunspell added; codeblocks removed |
Priority: | High → Normal |
Summary: | codeblocks port doesnt work with sequoia arm64 → hunspell: Build failure |
comment:3 Changed 3 weeks ago by ryandesign (Ryan Carsten Schmidt)
When the build of hunspell failed, MacPorts would have printed a line showing you the path to the hunspell main.log file. If you don't have that output anymore, you can print it again by running port logfile hunspell
. If you're using a standard MacPorts installation, it would look something like this:
% port logfile hunspell /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_hunspell/hunspell/main.log
Copy this path to the pasteboard. You can do that by running port logfile hunspell | pbcopy
.
Now, on this Trac ticket's web page, under the ticket description, click the disclosure triangle to the left of where it says Attachments and click Attach file. On the next page, click Choose File. In the file chooser, press Command-Shift-G to go to another location. In the sheet that appears, press Command-V to paste the logfile path you copied earlier. If there is a space at the end of the path, press the Delete key once to delete the space. Then press Return to select that file in the file chooser. Then press Return or click Upload to transfer that selection into the form. Then click Add Attachment to upload it to the ticket.
Changed 3 weeks ago by gautham81928
comment:4 Changed 3 weeks ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Summary: | hunspell: Build failure → hunspell: fatal error: 'cstdlib' file not found |
Thanks. The error shown in the log is:
:info:build hashmgr.cxx:71:10: fatal error: 'cstdlib' file not found :info:build 71 | #include <cstdlib> :info:build | ^~~~~~~~~
See ProblemHotlist#clts16 for the solution. Duplicate of #70750.
comment:5 follow-up: 6 Changed 3 weeks ago by gautham81928
Am I ok to now install codeblocks using macports?
comment:6 Changed 3 weeks ago by kencu (Ken)
Replying to gautham81928:
Am I ok to now install codeblocks using macports?
sure, but codeblocks-devel is much better. it tracks the upcoming new release of codeblocks, and has years of newer code in it.
Please attach the main.log file.