WIP, feature requests, comments, status reports etc. go here
libpri-1.4.0, zaptel-1.4.0, asterisk-1.4.0 ebuilds are in the voip overlay (-* masked!). current state: * all ebuilds bristuff support missing (waiting for updated upstream release) * asterisk-1.4.0: weak references patch not included; needs update (maybe not needed at all? did they replace the module loader? check first) hardened useflag renamed to pic (requested by solar) keepsrc implemented; installs sources into /usr/src/${PF} for custom patching (never really made it into the 1.2 series, well here it is... finally...(requested by SwK in #asterisk iirc)) pri useflag removed; zaptel useflag pulls in libpri and zaptel now. ASTERISK_MODULES (environment variable, -> make.conf) implemented, only build the modules listed in this variable, skips modules that have unresolved dependencies (e.g. chan_zap without zaptel installed, and no doing this in pkg_setup to die there will get messy...) scans the source for a list of available modules to verify user input. still WIP (note: this feature implies you know what you are doing... really easy to shoot yourself in the foot) TODO: updated update handling (hrhr) to support asterisk-1.0/1.2 -> 1.4 updates asterisk-updater script needs update, 1.2/1.4 API are incompatible (so if your shiny new asterisk-1.4 installation crashes right away, there's at least one old 1.2 module somewhere...) menuselect supports soundfiles in different languages and formats, the files are fetched during installation right now... TODO: avoid doing that and somehow support the different soundsets use econf now (wow, a configure script... openpbx.org influence showing here :> ) TODO: misdn... TODO: T.38 support(*cough*? spandsp?) probably add more useflags, drop ukcid(?) TODO: rewrite/fix wrapper init script(?) TODO: update / test tons of external modules (yay... fun :/ ) TODO: check dependencies, compile and run testing on several environments TODO: things i've forgotten now * zaptel-1.4.0: _not_ changed permissions on zaptel device nodes (they're still root:dialout 660) usb useflag added use econf now (well, menuselect just for a few tools is a little overkill, isn't it?) TODO: there's a new echo canceller somewhere in there... need to add that to the list... * libpri-1.4.0: nothing new here... * missing: TODO: asterisk-addons-1.4.0
Created attachment 105003 [details] My emerge output It had already compiled, so the emerge skipped and tried to install It's the install that fails anyways
* asterisk-1.4.0: added popt to dependencies for smsq
Created attachment 105004 [details] Failed emerge output The last part of the output was pasted in because it didn't end up in my output file for whatever reason
* asterisk-1.4.0: installation failes with MAKEOPTS="-jN" (and N>1), use -j1 in src_install()
For uclibc based systems I had to add: AST_LIBS+=-lpthread -ldl to main/Makefile to get it to compile. I didn't really have time to determine what checks were missing. Otherwise there were no compile problems so far.
Created attachment 105448 [details, diff] Fix for imap and qt USE flags configure tries to find uw-imap in really dumb manner. Also fixed compilation issue with qt USE flag.
The file asterisk-1.4.0-uclibc.patch is missing from trunk/net-misc/asterisk/files
The ebuild only lists ftp.digium.com as a download site, however this failed for me with a server error. ftp2.digium.com (downloaded and moved to distfiles manually) worked for me... Perhaps use both ftp1 and ftp2 as mirrors (these seem to be the "official" names now).
Had to use emerge --digest -av =net-misc/asterisk-1.4.0 to install as well as altering the ebuild keyword to add x86. Adding asterisk-1.4.0 to portage.keywords did not work on my system...probably related to portage rather than the ebuild itself. What is a bug is that digest verification failed: expected 10708 ...got 10709...perhaps just an ftp glitch. -jtp
is there any time table for getting a ebuild in the portage or is this BUG like dead ??? In case of the security hole it is very important to get a 1.4.1 ebuild !!!!! thx alex
(In reply to comment #10) >Adding asterisk-1.4.0 to portage.keywords did not work on my system...probably >related to portage rather than the ebuild itself. echo "net-misc/asterisk -*" >> /etc/portage/package.keywords (In reply to comment #11) >is there any time table for getting a ebuild in the portage or is this BUG >like dead ??? There is no roadmap, so the answer is "when it's ready". >In case of the security hole it is very important to get a 1.4.1 >ebuild !!!!! Not really, this is an experimental work-in-progress ebuild that has no keywords, it's not meant for production use. There won't be any support security-wise until it has been keyworded for general testing / stable. Anyway... version bumped, qa warning and useflag fixes.
The 1.4.1 ebuild references initd and confd scripts in the files directory, but the overlay doesn't appear to have these. I wouldn't be surprised if the scripts/files from portage would do fine. Gentoo users will expect to find init.d and conf.d files for asterisk when they install 1.4.x.
The 1.4.1 ebuild references initd and confd scripts in the files directory, but the overlay doesn't appear to have these. I wouldn't be surprised if the scripts/files from portage would do fine. Gentoo users will expect to find init.d and conf.d files for asterisk when they install 1.4.x. It also appears that /var/run/asterisk is not created by the ebuild.
(In reply to comment #12) > >In case of the security hole it is very important to get a 1.4.1 > >ebuild !!!!! > > Not really, this is an experimental work-in-progress ebuild that has no > keywords, it's not meant for production use. There won't be any > support security-wise until it has been keyworded for general testing / stable. Not really ?? Maybe you don't read the security hole in 1.4.0 (you can read this here http://www.asterisk.org/node/48320) ?? So Asterisk have an official release of 1.4.1 !!! Maybe it should better way to work with their direct tarballs because in Gentoo there nothing happens for newer versions like 1.2.15, 1.2.16 and never a 1.4.x version available in the portage tree. And surely a "overlay 1.4.0-beta3" isn't a success ;-) And to work on a 1.0.12-r1 (9 Mar 2007) is a little bit stupid way to support old versions before new bugfixed releases. Sorry for that criticism. bye alex
Hello, I get the following output from libchanh323.a: *************************************************************** ********** Re-run 'make' to pick up H.323 parameters ********** *************************************************************** The ebuild stops there. When I "make" and "make install" everything is built fine. USE-Flags: net-misc/asterisk-1.4.1 USE="curl freetds h323 jabber mmx newt pic snmp speex sqlite ssl vorbis zlib -alsa -debug -imap -kde -keepsrc -misdn -mysql -nosamples -odbc -oss -postgres -qt3 -radius -static -zaptel"
The 1.4.1 ebuild uses the following command for conf: ./configure --prefix=/usr --host=i386-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib --localstatedir=/var --with-gsm=internal --with-popt --without-qt --without-oss --with-ssl --with-asound --without-curl --without-h323 --without-imap --without-ssl --without-newt --without-odbc --without-snmp --with-z --without-misdn --with-mysql --without-pwlib --without-speex --without-iksemel --without-radius --without-sqlite --without-vorbis --without-ogg --without-zaptel --without-pri --without-tonezone --without-tds --without-postgres --build=i386-pc-linux-gnu Is this part wrong: --with-ssl ... --without-imap --without-ssl Seems like without imap but with ssl = without ssl?
I am working on a 1.4.2 ebuild with support for H323 and chan_cellphone. I'm still testing and I will post to the list when I'm finished. Anyone have any reconmendations for H323? I can build openh323 in conjunction with asterisk or I can re-run the asterisk build a second time once it's worked out the H323 configuration. Chan_cellphone doesn't like gentoo's up to date bluetooth libs. It will be great when I'm finished. The SLUG and openWRT people are beating us to the punch ;) Luke
Asterisk 1.4.2 is now available. The net-misc/asterisk-1.4.1 ebuild (in the voip overlay) worked to install asterisk 1.4.2 with just a version bump. Zap channels would not build in 1.4.2 though (needs zaptel version 1.4.1). I wrote an updated ebuild for net-misc/zaptel-1.4.1, see bug #174681. I now have a working installation of asterisk-1.4.2 with zap channels.
asterisk 1.4.2 is already in the voip overlay. I have changed the zaptel dep accordingly, thanks.
Could we get a status update on this? What's needed to get the ebuild into testing?
(In reply to comment #21) > What's needed to get the ebuild into testing? A developer to commit and support it. A plus would be if he would also actively ue the software. I do not actively use it and thus committing does not make sense. Besides see the unresolved issues in this bug :)
The init.d and conf.d files are missing from trunk/net-misc/asterisk/files.
For now get them from the 1.2.0 version, ie: # cp /usr/portage/net-misc/asterisk/files/1.2.0/asterisk.rc6 /etc/init.d/asterisk # cp /usr/portage/net-misc/asterisk/files/1.2.0/asterisk.confd /etc/conf.d/asterisk They work for me. I'll post a patch to the ebuild shortly.
Sorry, my apologies. I answered too soon. As you obviously realised they're referenced in the ebuild, but just missing from the overlay. Is there a reason why there are no keywords against asterisk-1.4.3? I can't find a way to unmask with package.keywords, and had to edit the ebuild. Can we add ~x86, and ~arch of anyone else who can at least get it to compile? Also, I propose the SRC_URI be changed from: SRC_URI="ftp://ftp.digium.com/pub/asterisk/${MY_P}.tar.gz" to: SRC_URI="ftp://ftp.digium.com/pub/asterisk/old-releases/${MY_P}.tar.gz" The old-releases directory *does* have the latest releases. The pub/asterisk directory only has the latest release, so the ebuild stops being able to fetch as soon as a new release is made. Just installed asterisk-1.4.4, and is working for me.
I've upgraded to 1.4.4 by copying the 1.4.3 ebuild to the new version and running a digest. All seems well. I've tried adding func_devstate by putting the file there, however all I get are a bunch of compile errors and I really don't have the time to look into it. zaptel-1.4.1 worked for me, the 1.4.2 version is missing a diff
I wonder if it's only me but where are the init scripts? Are they actually installed? Copying the ebuild to 1.4.4 worked for me also.
Created attachment 120258 [details] zaptel-1.4.2.1-r1.ebuild for testing, not working on Xen DumU Updated patches for bristuff (BRI_VERSION="0.4.0-test1") and florz FLORZ_VERSION="0.4.0-test1_florz-13") for testing. Compiled successfully on amd64. Test result for zaphfc: Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.4.2.1 Zaptel Echo Canceller: MG2 zaphfc: jitterbuffer size: 1 PCI: Enabling device 0000:00:00.0 (0000 -> 0003) zaphfc: CCD/Billion/Asuscom 2BD0 configured at mem 0x30c00 fifo 0xb240000(0x35e55000) IRQ 20 HZ 100 zaphfc: Card 0 configured for TE mode zaphfc: Card 0 configured for master mode zaphfc: hfc busy. zaphfc: 1 hfc-pci card(s) in this box. Registered tone zone 6 (Spain) Zaptel Transcoder support loaded -> not working. Can be a Xen 3.0.4 DomU problem.
Created attachment 120271 [details] asterisk-1.4.2-r1 with bristuff 0.4.0 for testing Compiled succesfully on amd64.
Created attachment 120272 [details] libpri with bristuff 0.4.0 for testing Compiled successfully on amd64.
just an fyi, i used the 1.4.4 ebuild, added this: if use h323 ; then #emake one time to get h323 to make.... yea not "clean" but works emake fi before the: emake || die "emake failed" and it builds with the h323 support i think.
(In reply to comment #25) > > Also, I propose the SRC_URI be changed from: > SRC_URI="ftp://ftp.digium.com/pub/asterisk/${MY_P}.tar.gz" > to: > SRC_URI="ftp://ftp.digium.com/pub/asterisk/old-releases/${MY_P}.tar.gz" > Done.
Added ebuild for 1.4.6 Added the "ugly" workaround for the h323 module: If the h323 useflag is set, emake is called twice (without cleaning the build directories) as suggested in http://bugs.gentoo.org/show_bug.cgi?id=159013#c31
Hmm. Seems like net-misc/asterisk-chan_capi doesn't compile with asterisk-1.4.6 Could someone try and verify?
For any updates to the ebuilds, please provide diffs against the current ebuilds. That's much easier to figure out what you want changed.
Created attachment 124810 [details] build.log of failed asterisk-1.4.7.1 with USE="h323" net-misc/asterisk-1.4.7.1 fails with USE="h323" here. net-misc/asterisk-1.4.7.1 works with USE="-h323" here. net-libs/openh323-1.18.0 is installed.
Created attachment 124811 [details] build.log of failed asterisk-chan_capi-0.7.1 after installing asterisk-1.4.7.1 with USE="-h323" net-misc/asterisk-chan_capi-0.7.1 still fails with net-misc/asterisk-1.4.7.1
Created attachment 124812 [details] build.log of failed asterisk-chan_capi-1.0.1 after installing asterisk-1.4.7.1 with USE="-h323" net-misc/asterisk-chan_capi-1.0.1 still fails with net-misc/asterisk-1.4.7.1
What was the last version of asterisk with which asterisk-chan_capi successfully compiled? Could we agree on leaving the last two or three ebuilds so that other helpers of the voip overlay can still use them (without having to fiddle with svn etc.) in order to find out what's wrong?
Renaming the asterisk-1.4.9.ebuild from the overlay to asterisk-1.4.10.1.ebuild and using the chan_capi-HEAD.tgz with the asterisk-chan_capi-1.0.1.ebuild worked for me for our DIVA card (drivers in #142634).
Created attachment 128192 [details] failed emerge of asterisk-1.4.10.ebuild Using layman to manage VOIP overlay. Update earlier today was at revision 577. The asterisk tarball for 1.4.10 seems to be 496 bytes?
1.4.10 is failing because the file has been moved on upstream ftp server. I bumped to 1.4.10.1 on my local machine and I got past this problem.
(In reply to comment #42) > 1.4.10 is failing because the file has been moved on upstream ftp server. I > bumped to 1.4.10.1 on my local machine and I got past this problem. > I hadn't thought of that :) I did notice the .1 relase on digium's site before I posted. I've bumped to 1.4.10.1 and works like a charm. Thanks!
Bad path to asterisk-1.4.10. Also bad digest for correct file (expects file size of 496 bytes) SRC_URI="http://ftp.digium.com/pub/asterisk/releases/${MY_P}.tar.gz"
I delete previous versions when it's a security issue. While the voip overlay is not security maintained, I am aiming for asterisk to hit the actual tree very shortly and that follows the policy of the security team.
Created attachment 131363 [details, diff] allow Asterisk to set high ToS bits as non-root on Linux By default asterisk on gentoo runs as user asterisk - this patch (from http://bugs.digium.com/view.php?id=7047) allows asterisk to retain CAP_NET_ADMIN capabilities and therefore set ToS bits when running as user asterisk. I've altered the patch to apply cleanly to asterisk-1.4.11. Any chance it can be included (use-enabled) in the ebuild?
(In reply to comment #46) > By default asterisk on gentoo runs as user asterisk - this patch (from > http://bugs.digium.com/view.php?id=7047) allows asterisk to retain > CAP_NET_ADMIN capabilities and therefore set ToS bits when running as user > asterisk. > > Any chance it can be included (use-enabled) in the ebuild? > Tim: Can you open the issue with upstream and see what they say about the possibility of backporting this to 1.4?
May i ask why there is no asterisk-addons ebuild for 1.4? regards t.
Nor asterisk-sounds...
Created attachment 136200 [details, diff] kernel >= 2.6.22 uncompat fix
Created attachment 136202 [details, diff] updated zaptel patch
Created attachment 136204 [details] updated ebuild to incude the kernel patch too
Created attachment 136205 [details, diff] updated libpri patch
Created attachment 136207 [details, diff] header fix
Created attachment 136209 [details] the modified libpri ebuild
i updated the zaptel and libpri packages for my own. What is not fixed is the zapnet function in the zaptel package, so dont use it with kernel >= 2.6.22! Both of them are not perfect, but usable and "just works". I use them in production environments, they are working very well (comlete ~amd64 system: 4.2.2 gcc, 2.7 glibc, 2.6.23 gentoo-sources kernel)
Is there no maintainer anymore? Asterisk 1.4.14 released a few days ago by the way. regards
U can install asterisk 1.4.14 easily: install layman, add the "voip" overlay, than use the ebuild, You should just rename it to asterisk-1.4.14.ebuild. But the new version will work just with my recent zaptel and libpri packages.
Hello. I am not able to compile app_rtxfax. This ist what i get: commander asterisk-app_rtxfax # emerge -v =asterisk-app_rtxfax-0.0.2_pre25-r1 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1 [0.0.2_pre25] 0 kB [1] Total: 1 package (1 upgrade), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/portage/local/layman/voip >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1 to / * asterisk-app_rtxfax-0.0.2_pre25.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking asterisk-app_rtxfax-0.0.2_pre25.tar.bz2 ;-) ... [ ok ] /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 134: /usr/bin/asterisk-config: No such file or directory * Asterisk version: /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 147: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 148: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 149: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 150: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 151: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 152: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 153: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 154: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 155: /usr/bin/asterisk-config: No such file or directory /usr/portage/local/layman/voip/eclass/asterisk-mod.eclass: line 159: /usr/bin/asterisk-config: No such file or directory >>> Unpacking source... >>> Unpacking asterisk-app_rtxfax-0.0.2_pre25.tar.bz2 to /var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/work/app_rtxfax-0.0.2_pre25 ... >>> Building app_rxfax... x86_64-pc-linux-gnu-gcc -g -Wall -D_REENTRANT -D_GNU_SOURCE -fPIC -march=k8 -O2 -pipe -c -o app_rxfax.o app_rxfax.c x86_64-pc-linux-gnu-gcc: app_rxfax.c: No such file or directory x86_64-pc-linux-gnu-gcc: no input files * * ERROR: net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1 failed. * Call stack: * ebuild.sh, line 46: Called src_compile * environment, line 2525: Called asterisk-mod_src_compile * environment, line 441: Called die * The specific snippet of code: * ast_do_compile ${AST_CC} ${AST_CFLAGS} ${CFLAGS} ${mod_cflags} -c -o ${obj} ${src} || diefunc "$FUNCNAME" "$LINENO" "$?" "Compiling ${x} failed!"; * The die message: * Compiling failed! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/temp/environment'. * * Messages for package net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1: * * ERROR: net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1 failed. * Call stack: * ebuild.sh, line 46: Called src_compile * environment, line 2525: Called asterisk-mod_src_compile * environment, line 441: Called die * The specific snippet of code: * ast_do_compile ${AST_CC} ${AST_CFLAGS} ${CFLAGS} ${mod_cflags} -c -o ${obj} ${src} || diefunc "$FUNCNAME" "$LINENO" "$?" "Compiling ${x} failed!"; * The die message: * Compiling failed! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/asterisk-app_rtxfax-0.0.2_pre25-r1/temp/environment'. * Any Solution to this? best regards t.
Yeah, take the 1.2 ebuild and use the /usr/bin/asterisk-config wrapper as base, modified to match your installed version, its only a bash script (not the best way to fix, but it works).
Could you be more specific Torsten? Do you run asterisk 1.4 with app_rtxfax successfully? cheers t.
I use this now. Works perfectly. http://www.voip-info.org/wiki/view/AGX+Extra+Addons+for+Asterisk t.
Created attachment 140019 [details] agx-ast-addons-1.4.3.ebuild It's working agx ebuild. Replace 1-2 packages. equery f net-misc/agx-ast-addons [ Searching for packages matching net-misc/agx-ast-addons... ] * Contents of net-misc/agx-ast-addons-1.4.3: /usr /usr/lib /usr/lib/asterisk /usr/lib/asterisk/modules /usr/lib/asterisk/modules/app_devstate.so /usr/lib/asterisk/modules/app_nv_backgrounddetect.so /usr/lib/asterisk/modules/app_nv_faxdetect.so /usr/lib/asterisk/modules/app_pickup2.so /usr/lib/asterisk/modules/app_rxfax.so /usr/lib/asterisk/modules/app_txfax.so /usr/lib/asterisk/modules/func_devstate.so
Created attachment 140021 [details] spandsp-0.0.4_pre15 Required for the agx-ast-addons.
Created attachment 140038 [details, diff] bristuff-0.4.0-test4-ksrc.patch makes bristuff use $(KSRC) rather than /usr/src/linux to respect KBUILD_OUTPUT and KERNEL_DIR variables.
Created attachment 140041 [details] zaptel-1.4.7.1.ebuild with bristuff support
Created attachment 140042 [details, diff] zaptel-1.4.7.1-gentoo.diff the zaptel-1.4.6-gentoo.diff patch adapted for 1.4.7.1
Created attachment 140043 [details, diff] diff between zaptel 1.4.6 and 1.4.7.1 ebuilds
When would this get to be inside the main portage tree?
Created attachment 143656 [details] Asterisk 1.4.18 ebuild (without bristuff) Made a simple asterisk 1.4.18 ebuild. Works fine with SIP only installation.
Created attachment 143658 [details, diff] configure patch
Created attachment 143660 [details, diff] rundir patch
Created attachment 143940 [details] Zaptel 1.4.9 ebuild with ztdummy-only Use Flag (without bristuff) Simple zaptel 1.4.9 ebuild with ztdummy-only use flag. This is all i need because i have no digium hardware.
Created attachment 143941 [details, diff] patch for zaptel 1.4.9
Created attachment 143942 [details, diff] options file for just create ztdummy
checking for sqlite_exec in -lsqlite... no configure: *** configure: *** The SQLite installation on this system appears to be broken. configure: *** Either correct the installation, or run configure configure: *** without explicitly specifying --with-sqlite !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-misc/asterisk-1.4.18/work/asterisk-1.4.18/config.log * * ERROR: net-misc/asterisk-1.4.18 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2504: Called econf 'src_compile' 'src_compile' '--libdir=/usr/lib' '--localstatedir=/var' '--with-gsm=internal' '--with-popt' '--with-z' '--without-qt' '--with-oss' '--with-ssl' '--with-asound' '--without-curl' '--with-h323=/usr/share/openh323' '--without-imap' '--without-newt' '--without-odbc' '--without-snmp' '--without-misdn' '--without-isdnnet' '--without-mysql' '--with-pwlib=/usr/share/pwlib' '--with-speex' '--with-iksemel' '--without-radius' '--with-sqlite' '--with-vorbis' '--with-ogg' '--without-zaptel' '--without-pri' '--without-tonezone' * ebuild.sh, line 513: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/asterisk-1.4.18/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/asterisk-1.4.18/temp/environment'. * This ebuild is from an overlay: '/home/luke-jr/src/gentoo/overlay/' *
I think you need sqlite-2.* to be installed.
(In reply to comment #77) > I think you need sqlite-2.* to be installed. That's what dependencies are for, isn't it? I wish sqlite <3 would get its own old-sqlite USE flag..
(In reply to comment #78) > (In reply to comment #77) > > I think you need sqlite-2.* to be installed. > > That's what dependencies are for, isn't it? > > I wish sqlite <3 would get its own old-sqlite USE flag.. Feel free to adjust the ebuild.
Created attachment 144324 [details] lame asterisk addons 1.4.6 ebuild :-) This is a ebuild for asterisk-addons-1.4.6 which was released yesterday (21.2.08). You have to create a file called /etc/asteriskaddons.makeopts which will take care of what module is being compiled and installed. I will upload such an example which will install format_mp3 only.
Created attachment 144326 [details] options file this belongs to /etc
Created attachment 147840 [details] zaptel-1.4.9.2.ebuild zaptel 1.4.9.2 with bristuff
Created attachment 147843 [details, diff] zaptel-1.4.9.2-bristuff-KSRC.patch
Created attachment 147845 [details, diff] zaptel-1.4.9.2-gentoo.diff
Created attachment 147851 [details, diff] zaptel-1.4.9.ebuild.diff diff between zaptel-1.4.9.ebuild and zaptel-1.4.9.2.ebuild I have tested the zaptel 1.4.9.2 ebuild with a Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02) ISDN card (bristuff) and Siemens HiPath 3750 and asterisk 1.6 beta using QSIG signaling.
I recommend the overlay maintainers mask Asterisk 1.4.19; new bugs make it unusable.
Hi guys, 1.4.19.1 works for me. A question though: Would it be possible to include the patch at http://www.b2bua.org/wiki/AsteriskCodecNegotiationPatch into the build (preferably with an optional USE flag)?
Hi guys, I just wanted to report what I think it's a bug with 1.4.20. I recently deployed a system on 1.4.19.1 and it was working fine until I upgraded to 1.4.20. Using a phone connected to a Grandstream HT-488 FXS port to call out through Asterisk through the same HT-488 FXO port doesn't work anymore. From other phones connected to Asterisk I can dial out through that FXO port just fine. Portage 2.1.4.4 (default-linux/x86/2007.0/server, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r3 i686) ================================================================= System uname: 2.6.24-gentoo-r3 i686 AMD Athlon(tm) X2 Dual Core Processor BE-2400 Timestamp of tree: Thu, 29 May 2008 10:15:02 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p33 dev-lang/python: 2.4.4-r13 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.61-r1 sys-devel/automake: 1.7.9-r1, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -pipe -fomit-frame-pointer -ffast-math -march=athlon64 -msse2 -m3dnow" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O3 -pipe -fomit-frame-pointer -ffast-math -march=athlon64 -msse2 -m3dnow" DISTDIR="/data/gentoo/distfiles" FEATURES="ccache distcc distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://gentoo.osuosl.org/ ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://gentoo.llarian.net/" LINGUAS="en en_US ro" MAKEOPTS="-j12" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/data/gentoo/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/voip /data/gentoo/overlay" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow 3dnowext X a52 apache2 bash-completion bzip2 cgi cli cpudetection cracklib crypt dri encode fasttrack flac gd gdbm gnutella gpm hdhomerun iconv isdnlog ivtv mbrola midi mmx mmx2 mmxext mp3 mysql ncurses nls nptl nptlonly offensive opengl openmp pam pcre perl posix pppd python readline reflection rtc samba sasl session slang spl sse sse2 ssl syslog threads truetype unicode usb vim-syntax x264 x86 xml xorg zaptel zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_US ro" USERLAND="GNU" VIDEO_CARDS="sis vesa" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
anybody got an ebuild for the asterisk-now gui?
bug has been fixed by upstream in 1.4.20.1
Using asterisk-1.4.21.1 with the 'imap' USE flag does not provide the app_voicemail_imap.so module in /usr/lib/asterisk/modules. I noticed this when emerge'ing: checking for UW IMAP Toolkit c-client library... yes So, it appears its finding the library, but does something else have to be enabled to make it build that module?
I just build asterisk by hand, and it didn't generate a app_voicemail_imap.so like I thought it would. I verified it does contain IMAP support by doing a quick 'strings app_voicemail.so | grep IMAP' and the one generated by the ebuild does not contain this. I see conflicting items; Some people they get a app_voicemail_imap.so, yet I didn't? Maybe these people are just renaming the module by hand? I supposed this conversation should probably be taken elsewhere now, but I still don't think the ebuild acually puts in IMAP support.
Created attachment 161232 [details, diff] patch to make agx-ast-addons work against newer spandsp
Created attachment 161233 [details] net-misc/agx-ast-addons-1.4.5
Reassigning back to herd since Stefan has been retired as a Gentoo Developer (#27693).
Would it be possible to add a separate 'pri' USE flag? It's enabled as part of the zaptel USE flag at the moment. Personally I need zaptel support and don't need pri support.
It would be nice to move asterisk-1.4 from overlay to official portage. I have been using 1.4 for over a year on amd64 without any major problems. In past half year I would even mark it as stable. Are there any issues preventing the move to portage?
Any news about adding 1.4 to main portage tree? Since 1.6 is hard masked only ancient 1.2 is in portage.
(In reply to comment #98) > Any news about adding 1.4 to main portage tree? > Since 1.6 is hard masked only ancient 1.2 is in portage. > I prefer not to happen, 1.6 is quite stable as i see. Maybe better to start stabilization (first mark as unstable).
After close to three years and 100 comments, I don't forsee it happening. I'd say close and start one for 1.6, wait 3 years, start one for 2.0, ... ad infinitum.
(In reply to comment #99) > I prefer not to happen, 1.6 is quite stable as i see. Maybe better to start > stabilization (first mark as unstable). 1.6 is indeed in the tree (branch 1.6.1) and I'm quite happy to unmask that for you. The main thing I would worry about is people falling into the 'dial plan' trap as the syntax, macro calling convention and supported command set have changed quite extensively.
(In reply to comment #100) > After close to three years and 100 comments, I don't forsee it happening. I'd > say close and start one for 1.6, wait 3 years, start one for 2.0, ... ad > infinitum. Your trust, both in me and in Gentoo as a whole warms me from the inside. Thank you. I agree with a small fragment of your message, which is "close and start one for 1.6". Csaba, would you mind doing that please? It will get assigned to me (because Asterisk is now maintained) if it has net-misc/asterisk in the subject; I would recommend something along the lines of "net-misc/asterisk-1.6: Recommend unmask and (unstable) keywording"
If you don't mind Tony, I think it will be better to close this bug when 1.6 will be a real alternative (ie. unmasked and keyworded). So, users will be able to found -easily- the bug related to 1.4 without being lost with a masked 1.6.
We will not be pushing Asterisk 1.4 for inclusion into the portage tree. 1.6.1.8-r1 is now available for you, with a hand-picked set of patches from the upstream bug tracker that they have failed to apply so far. I have this running in production and am confident that 1.6.1 is a better option for you than 1.4
Well, _I_ am still interested in 1.4 and, actually, I still have a bug assigned to me (rules be damned). I would advise anyone else who is interested to head over to bug 262101 where I have just posted a shiny new 1.4.37 ebuild.
