[Hamlib-developer] Re: Packaging Hamlib for Debian

[Joop S. <pa...@de...>]

Jaime Robles wrote:

>Hello all,
>Some days ago i wrote an email to Terry, who is the Debian packager of HamLib 
>asking for tha package of the new version and i have not received any answer.
>
>As i am packaging KTrack i need hamlib 1.1.3 packaged so i have started to 
>package hamlib-1.1.3 too.
>I am not trying to "steal" the hamlib package, just packaging for myself as i 
>understand it's Terry's package.
>
>Ok, once i have done my disclaimer i would like to make a question as in the 
>packaging process i got this message in the compilation.
>It may be caused due to  the new gcc-3.2 as i have not any problem compiling 
>in Debian testing/stable and the problems are in a unstable (with gcc3.2).
>Any idea?
>
>Thanks!
>====================================================
>In file included from /usr/include/c++/3.2/backward/iostream.h:31,
>                 from ../include/hamlib/rigclass.h:225,
>                 from rigclass.cc:37:
>/usr/include/c++/3.2/backward/backward_warning.h:32:2: warning: #warning This 
>file includes at least one deprecated or antiquated header. Please consider 
>using one of the 32 headers found in section 17.4.1.2 of the C++ standard. 
>Examples include substituting the <X> header for the <X.h> header for C++ 
>includes, or <sstream> instead of the deprecated header <strstream.h>. To 
>disable this warning use -Wno-deprecated.
>rigclass.cc:366: default argument given for parameter 2 of `void
>   Rig::setRptrShift(rptr_shift_e, int = 0)'
>../include/hamlib/rigclass.h:99: after previous specification in `void
>   Rig::setRptrShift(rptr_shift_e, int = 0)'
>rigclass.cc:371: default argument given for parameter 1 of `rptr_shift_t
>   Rig::getRptrShift(int = 0)'
>../include/hamlib/rigclass.h:100: after previous specification in 
>`rptr_shift_t
>   Rig::getRptrShift(int = 0)'
>rigclass.cc:380: default argument given for parameter 2 of `void
>   Rig::setRptrOffs(long int, int = 0)'
>../include/hamlib/rigclass.h:101: after previous specification in `void
>   Rig::setRptrOffs(long int, int = 0)'
>rigclass.cc:385: default argument given for parameter 1 of `shortfreq_t
>   Rig::getRptrOffs(int = 0)'
>../include/hamlib/rigclass.h:102: after previous specification in `shortfreq_t
>   Rig::getRptrOffs(int = 0)'
>rigclass.cc:394: default argument given for parameter 2 of `void
>   Rig::setTs(long int, int = 0)'
>../include/hamlib/rigclass.h:103: after previous specification in `void
>   Rig::setTs(long int, int = 0)'
>rigclass.cc:399: default argument given for parameter 1 of `shortfreq_t
>   Rig::getTs(int = 0)'
>../include/hamlib/rigclass.h:104: after previous specification in `shortfreq_t
>   Rig::getTs(int = 0)'
>rigclass.cc:408: default argument given for parameter 2 of `void
>   Rig::setCTCSS(unsigned int, int = 0)'
>../include/hamlib/rigclass.h:106: after previous specification in `void
>   Rig::setCTCSS(unsigned int, int = 0)'
>rigclass.cc:413: default argument given for parameter 1 of `tone_t
>   Rig::getCTCSS(int = 0)'
>../include/hamlib/rigclass.h:107: after previous specification in `tone_t
>   Rig::getCTCSS(int = 0)'
>rigclass.cc:422: default argument given for parameter 2 of `void
>   Rig::setDCS(unsigned int, int = 0)'
>../include/hamlib/rigclass.h:108: after previous specification in `void
>   Rig::setDCS(unsigned int, int = 0)'
>rigclass.cc:427: default argument given for parameter 1 of `tone_t
>   Rig::getDCS(int = 0)'
>../include/hamlib/rigclass.h:109: after previous specification in `tone_t
>   Rig::getDCS(int = 0)'
>rigclass.cc:436: default argument given for parameter 2 of `void
>   Rig::setCTCSSsql(unsigned int, int = 0)'
>../include/hamlib/rigclass.h:111: after previous specification in `void
>   Rig::setCTCSSsql(unsigned int, int = 0)'
>rigclass.cc:441: default argument given for parameter 1 of `tone_t
>   Rig::getCTCSSsql(int = 0)'
>../include/hamlib/rigclass.h:112: after previous specification in `tone_t
>   Rig::getCTCSSsql(int = 0)'
>rigclass.cc:450: default argument given for parameter 2 of `void
>   Rig::setDCSsql(unsigned int, int = 0)'
>../include/hamlib/rigclass.h:113: after previous specification in `void
>   Rig::setDCSsql(unsigned int, int = 0)'
>rigclass.cc:455: default argument given for parameter 1 of `tone_t
>   Rig::getDCSsql(int = 0)'
>../include/hamlib/rigclass.h:114: after previous specification in `tone_t
>   Rig::getDCSsql(int = 0)'
>rigclass.cc:465: default argument given for parameter 3 of `void
>   Rig::setFunc(long long unsigned int, bool, int = 0)'
>../include/hamlib/rigclass.h:83: after previous specification in `void
>   Rig::setFunc(long long unsigned int, bool, int = 0)'
>rigclass.cc:470: default argument given for parameter 2 of `bool
>   Rig::getFunc(long long unsigned int, int = 0)'
>../include/hamlib/rigclass.h:84: after previous specification in `bool
>   Rig::getFunc(long long unsigned int, int = 0)'
>rigclass.cc:619: default argument given for parameter 2 of `void
>   Rig::setBank(int, int = 0)'
>../include/hamlib/rigclass.h:121: after previous specification in `void
>   Rig::setBank(int, int = 0)'
>rigclass.cc:624: default argument given for parameter 2 of `void
>   Rig::setMem(int, int = 0)'
>../include/hamlib/rigclass.h:122: after previous specification in `void
>   Rig::setMem(int, int = 0)'
>rigclass.cc:629: default argument given for parameter 1 of `int 
>Rig::getMem(int
>   = 0)'
>../include/hamlib/rigclass.h:123: after previous specification in `int
>   Rig::getMem(int = 0)'
>make[1]: *** [rigclass.lo] Error 1
>make[1]: Leaving directory `/paquetes/hamlib-1.1.3/c++'
>make: *** [all-recursive] Error 1
>kha:/paquetes/hamlib-1.1.3#
>====================================================
>

Use "./configure --without-cxx-binding". Hamlib-1.1.3 C++ bindings won't 
compile with gcc-3.2. So you can't build the C++ classes.

Hamlib-1.1.4 won't have this problem, it will arrive in a couple of 
weeks. So it might be worthwile waiting for the new release.

Terry, can we do an effort to resolve the current issues around the 
hamlib debian package? I am hereby offering my help. Maybe we can work 
out something like a dual maintainership, if this is OK with you. This 
way we can keep hamlib updated when you can't find the time to work on it.

>- -- 
>Un saludo,
>	Jaime Robles
>	ja...@kd...
>	Coordinador KDE-es - KDE Spanish Translation Team
>	http://www.kde.org/es  - http://es.i18n.kde.org
>  
>

Regards,
Joop