Opened 9 years ago
Closed 7 years ago
#48982 closed defect (worksforme)
Got problems with ncurses lib
Reported by: | vlatko@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: | ncurses |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hello!
After an upgrade of libraries in my project the ncurses lib didn't build/compile/install...
I get the following critical message near the end of the log file:
:info:build } :info:build } :info:build END { :info:build print "#endif /* NC_DEFINE_H */" :info:build } :info:build ' < $DEFS :info:build make[1]: *** [ncurses_def.h] Error 133 :info:build Trace/BPT trap: 5 :info:build dyld: Library not loaded: /opt/local/lib/libncurses.6.dylib :info:build Referenced from: /opt/local/lib/libreadline.6.dylib :info:build Reason: image not found :info:build Trace/BPT trap: 5 :info:build dyld: Library not loaded: /opt/local/lib/libncurses.6.dylib :info:build Referenced from: /opt/local/lib/libreadline.6.dylib :info:build Reason: image not found :info:build Trace/BPT trap: 5 :info:build dyld: Library not loaded: /opt/local/lib/libncurses.6.dylib :info:build Referenced from: /opt/local/lib/libreadline.6.dylib :info:build Reason: image not found :info:build Trace/BPT trap: 5 :info:build /bin/sh -c 'if test "cchar_t" = "cchar_t" ; then cat ./curses.wide >>curses.h ; fi' :info:build cat ./curses.tail >>curses.h :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/work/ncurses-6.0/include' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/work/ncurses-6.0' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/work/ncurses-6.0" && /usr/bin/make -j8 -w all :info:build Exit code: 2 :error:build org.macports.build for port ncurses returned: command execution failed :debug:build Error code: CHILDSTATUS 43704 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:build Warning: targets not executed for ncurses: org.macports.activate org.macports.build org.macports.destroot org.macports.install
Change History (3)
comment:1 follow-up: 2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Port: | ncurses added |
Priority: | High → Normal |
comment:2 Changed 9 years ago by vlatko@…
Hi,
I seems I have gawk installed (and autoconf that depends on gawk).
So now I follow your instructions and deactivate awk with
$ sudo port -fp deactivate gawk
I then check what ncurses libraries I have installed
$ sudo port installed|grep ncurses
ncurses @5.9_2 ncurses @5.9_2+universal ncurses @6.0_0 ncurses @6.0_0+universal
and clean the 6.0 version
$ sudo port clean ncurses@6.0_0 ncurses@6.0_0+universal ---> Cleaning ncurses ---> Cleaning nurses
Then I re-install the 6.0 version by running the port update
$ sudo port -n upgrade —force ncurses
and reactivate awk afterwards.
It worked, thanks four your help!
/ Vlatko
comment:3 Changed 7 years ago by l2dy (Zero King)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
The portion of the log you posted looks like the end of an awk program, so the error message that readline requires ncurses is probably coming from an awk program that you have installed. If you have any of the ports gawk, mawk or nawk installed, try deactivating them. Then clean ncurses and try again.
If that doesn't work, please attach the entire main.log file, which might give us more information.