I did some initial testing on hppa, sparc and amd64, but since i'm not part of those arch teams i won't touch the keywords: * Dependencies of asterisk-1.2.0_beta: net-libs/osptoolkit-3.3.1: needs testing on alpha, amd64, hppa, ppc, sparc Modified versions of dev-libs/pwlib-1.8.4 and net-libs/openh323-1.15.3 (see attachments), both need testing on: alpha, amd64, hppa, ppc, sparc * Asterisk-1.2.0_beta1, asterisk-addons-1.2.0_beta1, libpri-1.2.0_beta1, zaptel-1.2.0_beta1: These need testing on: alpha, hppa
Created attachment 67114 [details] Modified pwlib-1.8.4 ebuild modified to work on sparc and hppa (and others)
Created attachment 67115 [details] Modified openh323-1.15.3 ebuild modified to work on sparc and hppa
some information on the pwlib changes: this one has been cleaned up to finally remove the additional stuff in /usr/share/pwlib (copies of pwlib headers in include and symlinks to /usr/lib/libpt* in lib). The modified version has been tested with openh323-1.15.3 and all packages in portage that depend on pwlib and openh323. (See the attached log and diffs for more information). Both ebuilds are going to replace the current version in portage.
Created attachment 67118 [details] log of pwlib testing
Created attachment 67119 [details, diff] diff between current and modified pwlib-1.8.4 ebuild
Created attachment 67120 [details, diff] same for openh323-1.15.3 ebuild
test instructions for zaptel: modprobe ztdummy zttest (you can press ctrl+c after some seconds) sample output: tsukasa asterisk-1.2.0-beta1 # zttest Opened pseudo zap interface, measuring accuracy... 99.963379% 99.975586% 99.975586% 99.975586% 99.975586% 99.987793% 99.975586% --- Results after 7 passes --- Best: 99.987793 -- Worst: 99.963379 -- Average: 99.975586 ztdummy provides a timing interface for music-on-hold and conferences people need(!) this if they don't have a real card as a clock source (sound is distorted w/o one...).
Your pwlib changes reference a package which doesn't yet exist in that location in portage (libdc1394) which essentially prevents pwlib from being tested.
yeah, that should be media-libs/libdc1394, no idea why it's media-plugins in the ebuild
Created attachment 67607 [details] corrected pwlib-1.8.4 ebuild
pwlib fails to link at the end because of a missing /usr/lib/libesd.a file. It specifically calls it out in the linking process at the end of the compile and I cannot find a file in /usr/lib that appears to be referencing it.
Created attachment 67665 [details] pwlib-1.8.4 ebuild w/ libesd fix (needs pwlib-1.6.3-dyn-esd.patch)
So with the given fix, pwlib now fails to compile against media-libs/libdc1394-2.0.0_pre4 with the following; g++ -DP_USE_PRAGMA -D_REENTRANT -fno-exceptions -Wall -fPIC -DUSE_ESD=1 -I/var/tmp/portage/pwlib-1.8.4/work/pwlib-1.8.4/include \ -lraw1394 -ldv -ldc1394_control \ -I. -shared video4dc1394.cxx -o ../pwlib/device/videoinput/dc_pwplugin.so In file included from video4dc1394.cxx:195: videoio1394dc.h:235: error: 'dc1394_cameracapture' is used as a type, but is not defined as a type. video4dc1394.cxx: In member function `virtual BOOL PVideoInput1394DcDevice::Open(const PString&, int)': video4dc1394.cxx:289: error: `dc1394_create_handle' undeclared (first use this function) video4dc1394.cxx:289: error: (Each undeclared identifier is reported only once for each function it appears in.) video4dc1394.cxx:301: error: `dc1394_get_camera_nodes' undeclared (first use this function) video4dc1394.cxx:305: error: `dc1394_destroy_handle' undeclared (first use this function) video4dc1394.cxx: In member function `virtual BOOL PVideoInput1394DcDevice::Close()': video4dc1394.cxx:381: error: `dc1394_destroy_handle' undeclared (first use this function) video4dc1394.cxx: In member function `virtual BOOL PVideoInput1394DcDevice::Start()': video4dc1394.cxx:394: error: `MODE_320x240_YUV422' undeclared (first use this function) video4dc1394.cxx:396: error: `MODE_160x120_YUV444' undeclared (first use this function) video4dc1394.cxx:406: error: `FORMAT_VGA_NONCOMPRESSED' undeclared (first use this function) video4dc1394.cxx:407: error: `dc1394_query_supported_framerates' undeclared (first use this function) video4dc1394.cxx:416: error: `FRAMERATE_60' undeclared (first use this function) video4dc1394.cxx:418: error: `FRAMERATE_30' undeclared (first use this function) video4dc1394.cxx:420: error: `FRAMERATE_15' undeclared (first use this function) video4dc1394.cxx:422: error: `FRAMERATE_7_5' undeclared (first use this function) video4dc1394.cxx:424: error: `FRAMERATE_3_75' undeclared (first use this function) video4dc1394.cxx:426: error: `FRAMERATE_1_875' undeclared (first use this function) video4dc1394.cxx:437: error: `SPEED_400' undeclared (first use this function) video4dc1394.cxx:443: error: `camera' undeclared (first use this function) video4dc1394.cxx:443: error: cannot convert `raw1394_handle*' to ` dc1394camera_t*' for argument `1' to `dc1394error_t dc1394_dma_setup_capture(dc1394camera_t*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, const char*, dc1394capture_t*)' video4dc1394.cxx:450: error: cannot convert `raw1394_handle*' to ` dc1394camera_t*' for argument `1' to `dc1394error_t dc1394_setup_capture(dc1394camera_t*, unsigned int, unsigned int, unsigned int, unsigned int, dc1394capture_t*)' video4dc1394.cxx:462: error: `dc1394_start_iso_transmission' undeclared (first use this function) video4dc1394.cxx:467: error: `dc1394_dma_release_camera' undeclared (first use this function) video4dc1394.cxx:469: error: `dc1394_release_camera' undeclared (first use this function) video4dc1394.cxx: In member function `virtual BOOL PVideoInput1394DcDevice::Stop()': video4dc1394.cxx:485: error: `dc1394_stop_iso_transmission' undeclared (first use this function) video4dc1394.cxx:487: error: cannot convert `raw1394_handle*' to ` dc1394capture_t*' for argument `1' to `dc1394error_t dc1394_dma_unlisten(dc1394capture_t*)' video4dc1394.cxx:488: error: `dc1394_dma_release_camera' undeclared (first use this function) video4dc1394.cxx:490: error: `dc1394_release_camera' undeclared (first use this function) video4dc1394.cxx: In member function `virtual BOOL PVideoInput1394DcDevice::GetFrameDataNoDelay(BYTE*, PINDEX*)': video4dc1394.cxx:668: error: `dc1394_dma_single_capture' undeclared (first use this function) video4dc1394.cxx:669: error: `dc1394_single_capture' undeclared (first use this function) make[2]: *** [../pwlib/device/videoinput/dc_pwplugin.so] Error 1 make[2]: Leaving directory `/var/tmp/portage/pwlib-1.8.4/work/pwlib-1.8.4/plugins/vidinput_dc' make[1]: *** [opt] Error 2 make[1]: Leaving directory `/var/tmp/portage/pwlib-1.8.4/work/pwlib-1.8.4/plugins' make: *** [opt] Error 2 !!! ERROR: dev-libs/pwlib-1.8.4 failed. !!! Function src_compile, Line 109, Exitcode 2 !!! make failed !!! If you need support, post the topmost build error, NOT this status message.
pwlib doesn't support the new libdc1394 api at the moment (checked pwlib-1.9.1 and upstream CVS), i've cleaned up and changed parts of the 1.8.4 ebuild in portage so disabling of ieee1394 and other plugins works now. Depends have been changed to: - media-libs/libdc1394 ) + <media-libs/libdc1394-1.9.9 + !>=media-libs/libdc1394-2.0.0_pre0 ) The major changes will be moved into the (upcoming) pwlib-1.8.7 ebuild.
we're currently testing a new alias system, sorry for the bugspam
Since some of these ebuilds are not the latest in greatest in portage, do you still want us to test against them or will updated ebuilds be provided?
this bug got a bit messy :/ also, i'd like to ask the same question as Jason.. could you possibly tell us again which version of which packages you want us to test? thx in advance
anybody home?
(In reply to comment #18) > anybody home? apparently not. please re-add amd64 when you let us know which version should get tested
Removing ppc, please re-add us once the versions to be tested are known.
Let us know when someone feels like answering the questions on this bug
(In reply to comment #19) > please re-add amd64 when you let us know which version should get tested (In reply to comment #20) > Removing ppc, please re-add us once the versions to be tested are known. I, like a lot of others am a bit confused about what needed/needs to be tested. agriffis marked 1.2.0_beta1 ~alpha on 11-Sep-2005 and I think that was the goal of this bug. If you need anything else, please re-add us.
@voip: Reopen this bug and CC the arches when you've cleaned up and decided what should be tested, thanks. :)
