tlf-devel
[Top][All Lists]
Advanced

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

Re: [Tlf-devel] Bugs....cannot complete autoreconf


From: Ervin Hegedüs
Subject: Re: [Tlf-devel] Bugs....cannot complete autoreconf
Date: Thu, 26 Jan 2017 11:02:05 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

Hi Bob,

On Wed, Jan 25, 2017 at 08:09:51PM -0700, w9ya wrote:
> Hey all;
> 
> I *am* able to successfully compile and package v. 1.2.2 but cannot
> compile either 1.2.3 or 1.2.4.5. (I didn't try any of the releases
> between those two.)

interesting - there was an affected issue, which had been fixed
by Thomas:

https://github.com/Tlf/tlf/issues/72

related commit:
https://github.com/Tlf/tlf/commit/e4d9e86a8516de7d3416e9a190e9af229a1f6ecf

but this was on 13rd of Dec, 2016. 1.2.3 had released on 16th of
Jan, 2016.

> I am getting the code from the github repo in all cases
> 
> To wit, here's that last few lines of where the PKGBUILD ( the
> packaging "recipe" which is attached below).:
> 
> "
>  address@hidden tlf]$ tail tlf-1.2.3-1-x86_64-build.log
> checking pkg-config is at least version 0.16... yes
> checking for GLIB - version >= 2.0.0... yes (version 2.50.2)
> checking for NcursesW wide-character library... yes
> checking for working ncursesw/curses.h... no
> checking for working ncursesw.h... no
> checking for working ncurses.h... yes
> checking for Curses Panel library with ncursesw/panel.h... no
> configure: error: the Curses Panel library is required
> ==> ERROR: A failure occurred in build().
>     Aborting...
> address@hidden tlf]$
> "
> 
> *** Here's a few bits of additional info;
> 
> address@hidden tlf]$ pacman -Qo /usr/include/panel.h
> /usr/include/panel.h is owned by ncurses 6.0+20161224-1
> address@hidden tlf]$

probably you're using ArchLinux - may be it's a new bug.
 
> SO....*If* I am reading the Changelog correctly this "bug" was
> introduced on 15-dec-2015 .

may be you're close that the real problem. (the Changelog
contains 2015-12-19, not 15 - but it doesn't matter...)

> Anyways, The comments in the code indicate that this *should NOT* be a
> problem, so I am not exactly sure what is causing this. (Then again I
> am writing this email prior to doing anything much more than finding
> the problem.)

I'll try to install an ArchLinux to a VM, and try to reproduce
your problem - I need some time...


73, Ervin
HA2OS
 



reply via email to

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