tlf-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] Problem to compile TLF.


From: David Quental
Subject: Re: [Tlf-devel] Problem to compile TLF.
Date: Sun, 6 Dec 2015 17:56:20 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

Hi Thomas,

tks for your email.

Yes, it corrected the problem, tks a lot.

Best 73.

CT1DRB
David Quental

Às 17:04 de 06-12-2015, Thomas Beierlein escreveu:
Hi David and Nate,

I just checked in a OpenSUSE vm. There is no /usr/include/panel.h just
a /usr/include/ncurses/panel.h in OpenSUSE. As an additionla problem
there is also no *.pc file which you could consult.

So you need to tell 'configure' about that additional search path.
Please do it as follows:

CFLAGS=-I/usr/include/ncurses ./configure ....
make clean
make

That should fix the problem.

73, de Tom DL1JBE

  Am Sun, 6 Dec 2015 10:50:38
-0600 schrieb Nate Bargmann <address@hidden>:

* On 2015 06 Dec 10:05 -0600, David Quental wrote:
Hi Thomas,

tks for your email.

I removed the tlf directory, then installed it again.

In fact the 2 lines are here when I type './configure'. However, it
does not compile yet:

keyer.c:31:19: fatal error: panel.h: No such file or directory
  #include <panel.h>
                    ^
compilation terminated.
Makefile:547: recipe for target 'keyer.o' failed
make[2]: *** [keyer.o] Error 1
David, if you use the command:

locate panel.h

do you get anything?  I have the mlocate Debian package installed that
provides a handy database to find files quickly using the 'locate'
command.  Here is what I get:

$ locate panel.h
/usr/include/panel.h
/usr/include/ncursesw/panel.h
/usr/share/doc/python2.7/html/library/curses.panel.html
/usr/src/linux-headers-3.16.0-4-amd64/include/config/input/apanel.h
/usr/src/linux-headers-3.16.0-4-common/include/drm/drm_panel.h

The first two are the ones used by the C preprocessor.

Perhaps you need an additional package installed that provides
panel.h?

73, Nate







reply via email to

[Prev in Thread] Current Thread [Next in Thread]