libtermcap (was: Re: Asterisk and termcap)

libtermcap (was: Re: Asterisk and termcap)

[Frans Meulenbroeks]

2010/9/6 Arigead <captain.deadly@gmail.com>:
> was trying to build Asterisk for the OpenMoko Free runner and it failed
> on a dependency on termcap so I tried to bitbake termcap first and that
> failed. The termcap compile stage is working but it's when it tries to
> install that the recipe seems to fail but I'm new to this.
>
> I'm off to read the openembedded documentation again but in the mean
> time if anybody can give me a hit that would be great.

Eric peeked into the termcap problem. I've tested his patch and it
works. He will probably push a patch later today.

The termcap problem from asterisk is not related. It cannot find
libtermcap. This one does not exist any more with ncurses 5.7.

People how should we fix this? I know it has been discussed before,
but I don't recall a solution.
I bumped into this for a different package too. There I fixed things
by adding a patch, but I am not sure if that is really the desired
solution.

Best regards, Frans

Re: libtermcap (was: Re: Asterisk and termcap)

[Arigead]

Frans Meulenbroeks wrote:
> 2010/9/6 Arigead <captain.deadly@gmail.com>:
>> was trying to build Asterisk for the OpenMoko Free runner and it failed
>> on a dependency on termcap so I tried to bitbake termcap first and that
>> failed. The termcap compile stage is working but it's when it tries to
>> install that the recipe seems to fail but I'm new to this.
>>
>> I'm off to read the openembedded documentation again but in the mean
>> time if anybody can give me a hit that would be great.
> 
> Eric peeked into the termcap problem. I've tested his patch and it
> works. He will probably push a patch later today.
> 
> The termcap problem from asterisk is not related. It cannot find
> libtermcap. This one does not exist any more with ncurses 5.7.
> 
> People how should we fix this? I know it has been discussed before,
> but I don't recall a solution.
> I bumped into this for a different package too. There I fixed things
> by adding a patch, but I am not sure if that is really the desired
> solution.
> 
> Best regards, Frans
> 

thanks a million for that Frans. I'll keep my ears on here and see if an
answer to this comes up.

Re: libtermcap (was: Re: Asterisk and termcap)

[Frans Meulenbroeks]

2010/9/6 Arigead <captain.deadly@gmail.com>:

>
> thanks a million for that Frans. I'll keep my ears on here and see if an
> answer to this comes up.
>

You're welcome.
Actually you should thank Eric, he did the work.
The patch will be there soon I assume.
I already saw and tested it (that is: verified that asterisk builds).
Leaving it to Eric to post the patch. He should get the credit for
this.

Have fun, Frans.

PS: I appreciate it if you could share your experiences with running th program.
Actually perhaps we should try to upgrade the program to 1.6.2.11 (or
maybe even 1.8 beta 4)

Re: libtermcap

[Enrico Scholz]

Frans Meulenbroeks <fransmeulenbroeks@gmail.com> writes:

> Eric peeked into the termcap problem. I've tested his patch and it
> works. He will probably push a patch later today.
>
> The termcap problem from asterisk is not related. It cannot find
> libtermcap. This one does not exist any more with ncurses 5.7.
>
> People how should we fix this? 

I added 9e58422868a03eeafa72781477174850d1c5abe7 some hours ago so that
'-ltermcap' should work again.  Patch does not break my builds but I do
not know whether it unbreaks the problematic ones ;)

Things are too different across the distributions (some have the
ncurses-config binconfig tools, other the .pc files, some have
libtinfo, some not) to find *the* correct solution.


Enrico

Re: libtermcap

[Tom Rini]

Enrico Scholz wrote:
> Frans Meulenbroeks <fransmeulenbroeks@gmail.com> writes:
> 
>> Eric peeked into the termcap problem. I've tested his patch and it
>> works. He will probably push a patch later today.
>>
>> The termcap problem from asterisk is not related. It cannot find
>> libtermcap. This one does not exist any more with ncurses 5.7.
>>
>> People how should we fix this? 
> 
> I added 9e58422868a03eeafa72781477174850d1c5abe7 some hours ago so that
> '-ltermcap' should work again.  Patch does not break my builds but I do
> not know whether it unbreaks the problematic ones ;)
> 
> Things are too different across the distributions (some have the
> ncurses-config binconfig tools, other the .pc files, some have
> libtinfo, some not) to find *the* correct solution.

Maybe I'm jumping in too late here.  Why is the correct solution not 
"make our ncurses-native build and install what's required by other 
recipes, fix broken recipes that look for the wrong thing" ?  IMHO, if 
you ASSUME_PROVIDED and things break, thats not our problem, its your 
problem (Doctor, it hurts when I do *this*.  Don't do *that* !)

-- 
Tom Rini
Mentor Graphics Corporation

Re: libtermcap

[Enrico Scholz]

Tom Rini <tom_rini@mentor.com> writes:

>> I added 9e58422868a03eeafa72781477174850d1c5abe7 some hours ago so
>> that '-ltermcap' should work again.  Patch does not break my builds
>> but I do not know whether it unbreaks the problematic ones ;)
>>
>> Things are too different across the distributions (some have the
>> ncurses-config binconfig tools, other the .pc files, some have
>> libtinfo, some not) to find *the* correct solution.
>
> Maybe I'm jumping in too late here.  Why is the correct solution not
> "make our ncurses-native build and install what's required by other
> recipes, fix broken recipes that look for the wrong thing" ?  

the "wrong" and "right" thing is difficultly to define for libtermcap.
Generally, patches should be in a manner that they can be accepted by
upstream.  That's not the case for 's!-ltermcap!-ltinfo!'


> IMHO, if you ASSUME_PROVIDED and things break, thats not our problem,
> its your problem (Doctor, it hurts when I do *this*.  Don't do *that*
> !)

OE has still the ncurses-5.4 receipt which will break packages depending
on hardcoded -ltinfo.



Enrico

Re: libtermcap

[Tom Rini]

Enrico Scholz wrote:
> Tom Rini <tom_rini@mentor.com> writes:
> 
>>> I added 9e58422868a03eeafa72781477174850d1c5abe7 some hours ago so
>>> that '-ltermcap' should work again.  Patch does not break my builds
>>> but I do not know whether it unbreaks the problematic ones ;)
>>>
>>> Things are too different across the distributions (some have the
>>> ncurses-config binconfig tools, other the .pc files, some have
>>> libtinfo, some not) to find *the* correct solution.
>> Maybe I'm jumping in too late here.  Why is the correct solution not
>> "make our ncurses-native build and install what's required by other
>> recipes, fix broken recipes that look for the wrong thing" ?  
> 
> the "wrong" and "right" thing is difficultly to define for libtermcap.
> Generally, patches should be in a manner that they can be accepted by
> upstream.  That's not the case for 's!-ltermcap!-ltinfo!'

Now that you've added a libtermcap + deprecated warning, that problem 
should be solved, yes?  What I'm saying is that we build ncurses 5.7 for 
the host system.  What we build there is what other programs we build 
should be looking for and using.  If they're looking for something we 
don't provide, that's a problem we should fix.  It should not ever 
matter what the host distribution provides as using it is wrong unless 
ASSUME_PROVIDED is set and in that case, it's user be aware.

>> IMHO, if you ASSUME_PROVIDED and things break, thats not our problem,
>> its your problem (Doctor, it hurts when I do *this*.  Don't do *that*
>> !)
> 
> OE has still the ncurses-5.4 receipt which will break packages depending
> on hardcoded -ltinfo.

Which should probably get dropped once everything is happy with 5.7.

-- 
Tom Rini
Mentor Graphics Corporation