#40961: ncurses: Undefined symbols ___sincos_stret ---------------------------+----------------------- Reporter: fabiocap93@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: mavericks Port: ncurses | ---------------------------+----------------------- Changes (by ryandesign@…): * keywords: => mavericks * owner: macports-tickets@… => jmr@… * port: => ncurses Old description:
When trying sudo port install ncurses it gets stuck here: ---> 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 Log file attached
New description: When trying `sudo port install ncurses` it gets stuck here: {{{ ---> 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 }}} Log file attached -- Comment: The log says: {{{ :info:build Undefined symbols for architecture x86_64: :info:build "___sincos_stret", referenced from: :info:build _main in tclock.o :info:build ld: symbol(s) not found for architecture x86_64 }}} This is new to me. It builds fine for me on Mavericks. Is it possible you have an old version of Xcode or its command line tools? A developer preview perhaps? Googling this error led me to this [http://stackoverflow.com/questions/19015780/sincos-stret-undefined- symbol-when-linking stack overflow post] which says uninstalling and reinstalling Xcode and the command line tools fixes this problem. -- Ticket URL: <https://trac.macports.org/ticket/40961#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X