similar to: compiling dahdi and exporting it to another system

pdf viewer with bookmarking facility?

Unfortunately, after http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=6cebc1c1fb12cc0661f3810ef47ad33206b2e398 I am unable to build DAHDI-Linux in a mock chroot for packaging purposes. I believe this is related to the Makefile calling install_firmware with only 2 args, where install_firmware is a shell script with DESTDIR set to $3, which is empty. In this case, the DESTDIR

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.8.0-rc5 DAHDI-Tools-v2.8.0-rc5 dahdi-linux-complete-2.8.0-rc5+2.8.0-rc5 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete *** THIS RC FIXES

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.8.0-rc5 DAHDI-Tools-v2.8.0-rc5 dahdi-linux-complete-2.8.0-rc5+2.8.0-rc5 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete *** THIS RC FIXES

Can someone make an rpm package for sane-backends-1.0.22.tar.gz Regards,

Hello list, I formatted a 64MB usb stick with this command 'mkfs.ext2 -b 1024 /dev/XXX1' , to copy a file of 9230653440, but when it reached 7921295360, it gave input/ output error and the file is not copied. How should this be done?

Is there a proper, documented way to cross compile DAHDI and Asterisk for a processor/system other than the one you're currently typing on? Now.. I have been doing this for some time, but it's been really frustrating every time I change/upgrade, etc. I've just tried to compile DAHDI for an AMD Geode system on my development system which is Intel Atom. Building the kernel is easy -

Hello, I nearly forgot about this mailing list! I accidentally bought a vonage enabled PAP2 to use on my asterisk, however it's locked and I have no access to the admin password. Anyone unlocked it before? Please send procedure. Make a cc to my address please. Thanks a million. Best regards, Twanny Azzopardi. Mob: ( 356 ) 79713618 Email: twanny@line.sytes.net Web: http://line.sytes.net

Hello, There are three small problems with the "slogin" and "slogin.1" symlinks created upon installation: 1. "./" is included in the target path unnecessarily. 2. Symlinks are assumed to be available, while only hardlinks could. 3. EXEEXT is not respected for slogin. Here is a fix for both problems -- the "./" is simply removed, EXEEXT is added, the

(This is the same change as 87c9ec881cb695724e01d9f6fc9df996d4c67cb6 in libguestfs.) --- ruby/Makefile.am | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/ruby/Makefile.am b/ruby/Makefile.am index e78ab59..7a5fe42 100644 --- a/ruby/Makefile.am +++ b/ruby/Makefile.am @@ -45,13 +45,17 @@ all: $(RAKE) build $(RAKE) rdoc -RUBY_SITELIB := $(shell $(RUBY)

Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: Matt Wilson <msw@amazon.com> --- Makefile | 2 +- Makefile.target | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 37c7066..594f0ef 100644 --- a/Makefile +++ b/Makefile @@ -243,7 +243,7 @@ endif install: all $(if $(BUILD_DOCS),install-doc) mkdir -p

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.1.1 dahdi-linux-complete-2.9.1.1+2.9.1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete Fix for bug preventing DAHDI from building in a chroot environment Issues closed in this release:

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.1.1 dahdi-linux-complete-2.9.1.1+2.9.1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete Fix for bug preventing DAHDI from building in a chroot environment Issues closed in this release:

Dear all I can not understand how to install the package lpsolve_1.1.9.zip I have read the FAQ and the help pages carefully, but it still not clear for me. I have tried the following (and obtained the respective error messages): >install.packages("c:/ProgramFiles/R/rw2011/library/lpSolve_1.1.9",destdir=" c:/ProgramFiles/R/rw2011/library/lpSolve") Mensagem de aviso:

Reid Spencer wrote: > Yes, but its a bit verbose. The variables that control this are all > defined in the Makefile.config file. The variables are: > > PROJ_prefix := /proj/llvm/install-1 > PROJ_bindir := /proj/llvm/install-1/bin > PROJ_libdir := /proj/llvm/install-1/lib > PROJ_datadir := /proj/llvm/install-1/share > PROJ_docsdir :=

Late to the show on this release, unfortunately. One of our production packages no longer builds under R-2.15.0 with the following message. ** testing if installed package can be loaded Error: Function found when exporting methods from the namespace 'SuperCurve' which is not S4 generic: 'image' Possibly relevant clues follow: ## From R/AllGenerics.R if

Hi I am evaluating some voice broadcasting solutions based on Asterisks for more than 1000 simultaneous calls. Connection to Asterisk all are based on SIP and SIP Trunks so no DAHDI hardware is required. According to some recommendations like http://osdial.org/howto/? "Internal timing is very critical with Asterisk when it is under load" and we must use DAHDI hardware or "USB Voice

Dear list, I'm experimenting with setting up custom 'lib' and 'destdir' directories for my R packages. It seems to me that 'library()' does handle a custom 'lib.loc' argument the way it should for an arbitrary package but NOT for its dependencies on other packages. The latter are looked for in the default lib path (~/R/R-2.x.x/library) and NOT in the custom

When files with pre-0.9.9 tool names exists in $(exec_prefix)/bin, "make DESTDIR=${staging_dir} install" tries to delete them, which may cause a failure for lack of permissions (quite likely to happen when building a package as a normal user), and is wrong anyway (nothing outside of DESTDIR should ever be changed by "make install"). With this patch, it will now cd to

My pc runs Scientific Linux release 6.8 (Carbon), Kernel 2.6.32-642.3.1.el6.i686, all patches applied. After unpacking, running ' -/configure ' (just that, no other params), then ' make; make install DESTDIR=`pwd`/DESTDIR ' and running sshd from there: the call ' DESTDIR/.../bin/ssh host102 ' succeeds ( authentication with id_rsa ; host 102 is localhost where the new sshd