Opened 9 years ago

Closed 9 years ago

#48712 closed defect (invalid)

ncurses @6.0: std::__1::cerr and others undefined

Reported by: paula.srs@… Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port: ncurses

Description (last modified by Ionic (Mihai Moldovan))

--->  Building ncurses
Error: org.macports.build for port ncurses returned: command execution failed
Please see the log file for port ncurses for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port ncurses failed

Attachments (2)

main.log (357.9 KB) - added by paula.srs@… 9 years ago.
main.log
main.2.log (11.6 KB) - added by paula.srs@… 9 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 9 years ago by Ionic (Mihai Moldovan)

Owner: changed from macports-tickets@… to jmr@…
Port: ncurses added
Summary: Cannot sudo port install ncursesncurses @6.0: std::__1::cerr and others undefined

Please remember to CC the maintainer(s), if any, next time. Also fill out the Port field.

This build log is incomplete.

Run sudo port clean ncurses and try updating again. Once it fails, re-upload the complete main.log file.

comment:2 Changed 9 years ago by Ionic (Mihai Moldovan)

Description: modified (diff)

comment:3 Changed 9 years ago by paula.srs@…

~ paula$ sudo port install ncurses ---> Fetching archive for ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ncurses ---> Fetching distfiles for ncurses ---> Verifying checksums for ncurses ---> Extracting ncurses ---> Applying patches to ncurses ---> Configuring ncurses ---> Building ncurses Error: org.macports.build for port ncurses returned: command execution failed Please see the log file for port ncurses for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/main.log

To report a bug, follow the instructions in the guide:

http://guide.macports.org/#project.tickets

Error: Processing of port ncurses failed

Changed 9 years ago by paula.srs@…

Attachment: main.log added

main.log

comment:4 Changed 9 years ago by jmroot (Joshua Root)

:info:configure checking version of /usr/bin/clang++... 2.1

That's much too old to be using on Mavericks, it should be at least 5.0 or so. Make sure your Xcode and command line tools are up to date.

comment:5 Changed 9 years ago by paula.srs@…

~ paula$ sudo port install clang-3.8 Password: ---> Building ncurses Error: org.macports.build for port ncurses returned: command execution failed Please see the log file for port ncurses for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/main.log

Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade cctools failed

Xcode and command line tools are up to date (versions 6.2)

Changed 9 years ago by paula.srs@…

Attachment: main.2.log added

comment:6 in reply to:  5 Changed 9 years ago by jmroot (Joshua Root)

Replying to paula.srs@…:

Xcode and command line tools are up to date (versions 6.2)

Then clang++ should be version 6.0. What is printed now if you run this command?

/usr/bin/clang++ -v

comment:7 Changed 9 years ago by paula.srs@…

paula$ /usr/bin/clang++ -v Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix

comment:8 Changed 9 years ago by jmroot (Joshua Root)

OK, so that is not the clang++ that comes with Xcode 6.2. If you did in fact install the correct command line tools before, they have somehow been overwritten (at least partially) and you probably need to reinstall them.

comment:9 Changed 9 years ago by jmroot (Joshua Root)

Resolution: invalid
Status: newclosed

Assuming this was due to old command line tools.

Note: See TracTickets for help on using tickets.