Restore your computer to peak performance in minutes!
If you have emacs, the Termcap database file on your Mac port cannot be opened on your PC, then hopefully this guide should help.
The linked port of emacs does not run on MacPorts (Emacs 23.2.1) on
OS X Leopard snow.
This error has already been reported by MacPorts, but there is still no
action to fix it, so I would like to try this tool to fix it myself.
The first thing you need to do is figure out where emacs is looking for this
termcap file for whatever reason.
Can anyone tell me what filenames and directories
can I look for this file in?
Second, if it’s missing, where can I find a functionally appropriate termcap
database file? Alternative: Is there a way to reject this
P.S. The Emacs that comes with OS X is loaded, but it’s usually version
22, I installed the MacPorts port of Emacs because I needed version
Publishing on kj
Emacs port 23 (emacs.2.Starts 1) provided that MacPorts by does not work on
OS X Snow Leopard.”Emacs Termcap file: cannot be opened” <
My guess is that the directory that emacs is looking for the terminfo
file is very hard on. When he didn’t find it, he just tried the old term.
Restore your computer to peak performance in minutes!
Is your PC running slow and constantly displaying errors? Have you been considering a reformat but don't have the time or patience? Fear not, dear friend! The answer to all your computing woes is here: ASR Pro. This amazing software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. So long as you have this program installed on your machine, you can kiss those frustrating and costly technical problems goodbye!
If that doesn’t work, find your own terminfo file, perhapsoh, it’s related
partially to the libncurses package.
Try installing libncurse-dev via MacPort first, and then rebuilding emacs23,
then it should probably work for everyone without this problem. With
publish port of Emacs MacPorts kj
Provided (Emacs 23.2.1) starts does not work
on OS other than X Snow Leopard.
emacs: “Could not open termcap data file”< br> This error MacPorts already knows about it, there are no steps to fix it, so I want to try to fix it myself.
First basic thing to determine where it is literally, is Emacs looking for a termcap file for it? I want to determine if I want it to be missing or not at all,
or just there, but not available to emacs for some reason.
Can someone give me all these directories and filenames so I can investigate the file?
Secondly, suppose< br>this is an absence, can I find exactly one termcap
job database file? If not, is there a way around this
P.S. The Emacs that comes with the OS starts x with up, but it’s all version
22 still installed in the MacPorts port of Emacs because I needed version
Content Type: Text/Plain; charset=ISO-8859-1
Try installing libncurse-dev via macport first, then rebuilding emacs23,
you should probably be fine without this problem.
I have found that the problem has been solved (thanks to these tips, I
got your answers). I’m posting the fix here for anyone
who might be having this problem.
The following extract from the application’s config.log file shows the root
of the problem:
configure:20977: checks from tparm -lncurses
configure:21012: in /usr/bin/gcc-4.-L/sw/lib 2 -i/sw/include -o conftest -pipe -arch – o2 x86_64 -D_REENTRANT -I /opt/local/include/librsvg-2.0 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/cairo -I/opt/local/include/libpng12 -I/opt/local/include/pixman-1 -I/opt / -I/opt/local/include -I/opt/-I/opt/local/include local/include/freetype2 local/include/freetype2 -I/opt/local/include Freetype2 -i/opt/local/include / – L/opt/local/lib -arch x86_64 conftest.c -lncurses -. I . m -lXrender -L/opt/local/lib -lXft -lXrender -lfontconfig -lexpat -liconv -lfreetype -lz -lX11 -lxcb -lXau -lXdmcp -lXmu -lxext -lSM -lICE -lxt -L/opt/local/ lib -lgio-2 -lrsvg-2.0 -lgdk_pixbuf-2.0 -lm -lcairo -lgmodule-2.0 -lgobject-2.0 -lpixman-1 -lfontconfig -lexpat -lfreetype -lpng12 -lz -lxrender -lgthread-2.0 -lglib- 2.0 – lintl -liconv -lxcb -lx11 -lXau -lXdmcp -lX11 -L/opt/local/lib -ldbus-1 -lpthread Warning: >&5
ld: there is a file in /sw/lib/libncurses.dylib for whichBecause i386 is not the main architecture to be linked (x86_64)
ld: warning: /sw/lib/libiconv in. dylib file was created for i386, which is not currently bound to the architecture (x86_64).
Undefined reference From:
“_tparm”, in ccaYZh71. o
ld: (s) character never found
collect2: ld returned 1, goodbye, status
configure:21019: $? = 1
You will see the following paths: /sw/lib, /sw/include and. These are old
packages introduced a long time ago by another with a system,
the Fink grouping.
The main problem is that MacPort looks for MacPorts
ncurses when determining dependencies for Emacs and
downloads the required versions as well, but then, during the main Emacs build period,
probably doesn’t. make sure it actually works with the version!
I don’t know how this type of path /sw/* ended up in some of the paths checked by the
configurator. The full Config command
doesn’t comment them at all:
CPATH=’/opt/local/include’ -O2 cflags=’-pipe -mid-foot (arch X86_64′) CPPFLAGS=’-I/opt/local/include’ CXXFLAGS=’-pipe -arch -o2 x86_64′ LIBRARY_PATH=’/opt/local/lib’ MACOSX_DEPLOYMENT_TARGET=’10.6′ CXX=’/usr/bin/g++-4.2′ CC_PRINT_OPTIONS_FILE=’/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_acports /.emeditors CC_PRINT_OPTIONS’ F90FLAGS=’-pipe -m64′ LDFLAGS=’-L/opt/local/lib -o2 -arch OBJC=’/usr/bin/gcc-4 x86_64′.2′ FCFLAGS=’-pipe -m64′ -o2 INSTALL=’/usr /bin/install -c’ -arch objcflags=’-pipe -o2 FFLAGS=’-pipe x86_64′ -m64′ -o2 CC_PRINT_OPTIONS=’YES’ CC=’/usr/bin/gcc-4.2 ‘ ./configure — with-dbus –prefix=/opt/local –no-gconf –no-libotf –no-m17n-flt –infodir –no-gpm /opt/local/share/info /emacs –with- x-toolkit=lucid –with-xpm –without-xaw3d –with-jpeg –with-tiff –with-gif –with-rsvg –with-png –with- xft
…and user environment when installing
mentioned /sw/lib, include not found:
% (sudo printenv | grep -e /sw/lib -e /sw/include) || Mirroring “no match”
This appears to be some kind of MacPorts leak, but I believe it
which is impossible.
In any case, once the problem was identified, the solution was
% mv sudo /sw /sw_DISABLEDownload the software to fix your PC by clicking here.