Needs updating. Haven't tried it myself yet. mumble.pro changed to main.pro (additionally compiles the server, too).
*** Bug 185429 has been marked as a duplicate of this bug. ***
Mumble 1.0.0 is out.
Created attachment 125174 [details] Mumble 1.0.0 client ebuild and patches Mumble 1.0.0 Client only ebuild and patches. Provides "audiowizard" USE flag for people with qt < 4.3 who don't want to upgrade to qt-4.3 or above and can live without the newly implemented Audio Assistant function.
Created attachment 125175 [details] Murmur 1.0.0 ebuild and patches This one is a very rudimentary port from the 0.9.4 ebuild, maybe needs some more customization (f.e. installation/ configuration of the murmur registration perlscripts). Should run quite well, though.
Thx for the ebuild. I got this for the client: $ mumble QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: Database: Failed initialization I've not used "audiowizard" and here is my sqlite infos: * dev-db/sqlite Available versions: 2.8.16-r4 3.3.12:3 3.3.17:3 Installed: 2.8.16-r1 3.3.5-r1 Homepage: http://www.sqlite.org/ Description: an SQL Database Engine in a C Library Upgrading to 3.3.17 doesn't do the trick. I saw nothing about sqlite in the README provided except for server side.
(In reply to comment #5) could you please give some additional information on your qt-installation (incl. useflags) ? thx
(In reply to comment #5) I'm having exactly the same error: duclare@hikari ~ $ mumble QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: Database: Failed initialization I did not use the audiowizard flag either. Here's what I can dig about my Qt installation: x11-libs/qt-4.2.3-r1 USE="cups doc gif jpeg opengl png sqlite zlib -accessibility -dbus -debug -examples (-firebird) -glib -mng -mysql -nas -nis -odbc -pch -postgres -qt3support -sqlite3 -xinerama" INPUT_DEVICES="-wacom" Any ideas?
Created attachment 126175 [details] mumble 1.0.0 ebuild (bugs fixed) the sqlite bug should be fixed now (the ebuild didn't check if qt was merged with sqlite3 use flag which is needed); another bug making push-to-talk not work should also be gone (xevie-patch).
(In reply to comment #8) > Created an attachment (id=126175) [edit] > mumble 1.0.0 ebuild (bugs fixed) > > the sqlite bug should be fixed now (the ebuild didn't check if qt was merged > with sqlite3 use flag which is needed); > another bug making push-to-talk not work should also be gone (xevie-patch). > Hi, i think that ebuild lack media-libs/speex dependences that are present in previus ebuilds... Bye to all ;)
The murmur (=server) ebuild will fail while compiling if Qt is not built with the dbus useflag: murmur_pch.h:8:18: error: QtDBus: No such file or directory make[2]: *** [release/murmur.gch/c++] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.0.0/work/mumble-1.0.0/src/murmur' make[1]: *** [release] Error 2 make[1]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.0.0/work/mumble-1.0.0/src/murmur' make: *** [sub-src_murmur-make_default] Error 2 !!! ERROR: media-sound/murmur-1.0.0 failed. Call stack: ebuild.sh, line 1621: Called dyn_compile ebuild.sh, line 973: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile murmur-1.0.0.ebuild, line 47: Called die As for the client, the last patched ebuild seemed to work so far. :) Indeed it looks like it should depend on speex though.
yes mumble should depend on speex but there's a problem: it seems to depend on a speex version higher than 1.1.12 (which is the newest in portage) but it has its own speex-sources which obviously work (speex-1.2beta2 also work for me). the problem is that the current ebuild overwrites /usr/lib/libspeex.a if it already existed (sorry for that). anyone an idea what to do except for waiting for a newer speex in portage ?
(In reply to comment #11) > yes mumble should depend on speex but there's a problem: > it seems to depend on a speex version higher than 1.1.12 (which is the newest > in portage) but it has its own speex-sources which obviously work > (speex-1.2beta2 also work for me). > the problem is that the current ebuild overwrites /usr/lib/libspeex.a if it > already existed (sorry for that). > anyone an idea what to do except for waiting for a newer speex in portage ? > Hi, yes, i see that speex source are already in mumble package, but i report it cause, like you have discover, it can do some problem with existing speex installation. I don't know when speex will be updated, but i send in cc this bug to Patrick McLean <chutzpah@gentoo.org> and Diego Pettenò <flameeyes@gentoo.org>, that are manteiners for speex ebuild, so they tell us about that. I had tried to talk with Timothy Redaelli <drizzt@gentoo.org>, about this bug, but i haven't received answer yet, i'll post other news soon. Bye Bye
Never CC me randomly.
(In reply to comment #13) > Never CC me randomly. > Sorry, my lord. I don't cc you randomly, i see in changelog of speex ebuild that you are one of most active in maintenance. So i think that you have more information than other to answer ThomasG's question about next release of speex ebuild or possible conflict with it and mumble... Next time i ask your royal permission to cc you. Sorry again my lord. Lovely, a little peasant.
speex 1.2_beta2 is in portage, is it now possible to remove the speex sourcecode from mumble and compile against speex in portage?
If I am not mistaken, there is a rule demanding not to attach ebuilds as tarballs.
1.1.0 is out
Considering I don't give a rat ass about this ebuild, I don't want to be in CC for it.
Created attachment 134048 [details] Ebuild for Mumble 1.1.0
please change the mime type of the file for: application/octet-stream :)
Policy says to post the .ebuild and .patch as separated files and NOT to post a .tar file
Created attachment 134125 [details] Ebuild for Mumble 1.1.0
Created attachment 134126 [details, diff] Client_only patch for mumble 1.1.0
Ok, I just tried Ductor's ebuild. To give you a little feedback: - The clientonly.patch doesn't work. If you look at the contents, things are referring to version 1.0.0 and not 1.1.0. I tried changing all 1.0.0 occurences to 1.1.0, but that didn't help. Obviously the contents aren't the same anymore either ;). So I edited the ebuild and commented out the patching completely for now. - Mumble requires Qt to be built with sqlite support. In the original mumble-0.9.4 ebuild it was ok to have it built with either the "sqlite" useflag or the "sqlite3" useflag. However, your 1.1.0 ebuild accepts sqlite3 _only_. As I have my Qt4 built with the sqlite flag, the ebuild would fail. I edited the ebuild to also accept sqlite (just add that flag before or after the original sqlite3 flag, space seperated in the ebuild). Compiling worked like a charm and a first test run was successful, too. So I'm not the expert, I don't know if it _must_ be the sqlite3 flag. If not, adding the sqlite flag as OK would be nice. Recompiling the whole Qt4 package just for a flag which does not do much difference is kind of tedious :) - Besides these two things, your ebuild seems to work great. No problems, yet. I'd vouch to accept your ebuild into the portage tree as soon as these two issues are resolved (and probably some more people reported success).
Created attachment 137254 [details] murmur-1.1.0.ebuild I am using murmur 1.1.0 with the attached ebuild on a server without any problems since a while. The serveronly patch will be attached in a sec. (You just need to reverse it (exclude only src/murmur) to get the clientonly patch.)
Created attachment 137256 [details, diff] mumble-1.1.0-serveronly.patch
Created attachment 137285 [details, diff] fixed mumble-1.1.0-clientonly.patch Thanks for delivering your files. Based on your serveronly patch I created the attached, fixed patch for clientonly. I just changed the line src/murmur into src/mumble. That one works for me now. However, I tried your murmur ebuild along with your mumble-serveronly patch and that one (for whatever reason) does not work. After unpacking, portage exits with this error: >>> Unpacking mumble-1.1.0.tar.bz2 to /var/tmp/portage/media-sound/murmur-1.1.0/work * Applying mumble-1.1.0-serveronly.patch ... * Failed Patch: mumble-1.1.0-serveronly.patch ! * ( /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveronly.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/media-sound/murmur-1.1.0/temp/mumble-1.1.0-serveronly.patch-14308.out * * ERROR: media-sound/murmur-1.1.0 failed. * Call stack: * ebuild.sh, line 35: Called src_unpack * environment, line 2041: Called epatch 'src_unpack' * environment, line 1090: Called die * The specific snippet of code: * diefunc "$FUNCNAME" "$LINENO" "$?" "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: mumble-1.1.0-serveronly.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:murmur-1.1.0:20071128-235125.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/murmur-1.1.0/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/' * The mentioned logfile contains this (/var/tmp/portage/media-sound/murmur-1.1.0/temp/mumble-1.1.0-serveronly.patch-14308.out): ***** mumble-1.1.0-serveronly.patch ***** ========================================= PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveron$ ========================================= patching file main.pro Hunk #1 FAILED at 2. 1 out of 1 hunk FAILED -- saving rejects to file main.pro.rej ========================================= PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveron$ ========================================= missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- main.pro.old 2007-10-21 12:56:49.000000000 +0200 |+++ main.pro 2007-10-21 12:57:10.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ========================================= PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveron$ ========================================= missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- main.pro.old 2007-10-21 12:56:49.000000000 +0200 |+++ main.pro 2007-10-21 12:57:10.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ========================================= PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveron$ ========================================= missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- main.pro.old 2007-10-21 12:56:49.000000000 +0200 |+++ main.pro 2007-10-21 12:57:10.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ========================================= PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/media-sound/murmur/files/mumble-1.1.0-serveron$ ========================================= missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- main.pro.old 2007-10-21 12:56:49.000000000 +0200 |+++ main.pro 2007-10-21 12:57:10.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored
That indeed sounds weird... Especially since your clientonly variant apparently works... Are you sure you have to correct patch in the correct directory? I am currently syncing with my server so I can try and reproduce this... May take a while, so don't expect any replies soon.
(In reply to comment #28) Yeah, I checked it again, everything is in place (in fact, from the error message you do see that it even tries to apply the patch, it just doesn't like something with it. I commented the patching part out of the ebuild for now, but then it still fails with some make error... i686-pc-linux-gnu-g++ -o ../../release/mumble release/BanEditor.o release/ACLEditor.o release/Log.o release/AudioConfigDialog.o release/AudioStats.o release/AudioInput.o release/AudioOutput.o release/main.o release/MainWindow.o release/ServerHandler.o release/About.o release/ConnectDialog.o release/Settings.o release/Database.o release/VersionCheck.o release/Global.o release/PlayerModel.o release/Audio.o release/ConfigDialog.o release/Plugins.o release/LookConfig.o release/Overlay.o release/AudioWizard.o release/ViewCert.o release/Messages.o release/DBus.o release/TextMessage.o release/ACL.o release/Group.o release/Channel.o release/Message.o release/Connection.o release/Player.o release/Timer.o release/CryptState.o release/ALSAAudio.o release/GlobalShortcut_unix.o release/TextToSpeech_unix.o release/Overlay_unix.o release/OSS.o release/moc_BanEditor.o release/moc_ACLEditor.o release/moc_Log.o release/moc_AudioConfigDialog.o release/moc_AudioStats.o release/moc_AudioInput.o release/moc_AudioOutput.o release/moc_MainWindow.o release/moc_ServerHandler.o release/moc_About.o release/moc_ConnectDialog.o release/moc_GlobalShortcut.o release/moc_TextToSpeech.o release/moc_Database.o release/moc_VersionCheck.o release/moc_PlayerModel.o release/moc_ConfigDialog.o release/moc_Plugins.o release/moc_LookConfig.o release/moc_Overlay.o release/moc_AudioWizard.o release/moc_ViewCert.o release/moc_DBus.o release/moc_TextMessage.o release/moc_ACL.o release/moc_Channel.o release/moc_Connection.o release/moc_Player.o release/moc_ALSAAudio.o release/moc_GlobalShortcut_unix.o release/moc_OSS.o release/qrc_mumble.o -L/usr/lib/qt4 -L/usr/lib -Llib -L. -lspeex -lssl -lcrypto -lXevie -lasound -lQtDBus -L/usr/lib/mysql -L/usr/lib/qt4 -ldbus-1 -lQtSql -lQtXml -lQtOpenGL -L/usr/lib -lQtGui -lpng -lSM -lICE -lXrender -lXrandr -lXfixes -lXcursor -lXinerama -lfreetype -lfontconfig -lXext -lX11 -lQtNetwork -lQtCore -lz -lm -lrt -lpthread -ldl -lGLU -lGL make[2]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.1.0/work/mumble-1.1.0/src/mumble' make[1]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.1.0/work/mumble-1.1.0/src/mumble' * * ERROR: media-sound/murmur-1.1.0 failed. * Call stack: * ebuild.sh, line 35: Called src_compile * environment, line 2010: Called die * The specific snippet of code: * emake CC="$(tc-getCC) ${CFLAGS}" CXX="$(tc-getCXX) ${CXXFLAGS}" LINK="$(tc-getCXX)" LFLAGS="${LDFLAGS}" || diefunc "$FUNCNAME" "$LINENO" "$?" "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:murmur-1.1.0:20071129-164022.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/murmur-1.1.0/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/'
The error seems missing in your snippet...
(In reply to comment #30) Hmm right, I scrolled up the compile log a bit but couldn't find any error, so i just pasted the last few lines. By going back to about half of the compile process, there is this error appearing: rm -f libmumble.so.1.1.0 libmumble.so libmumble.so.1 libmumble.so.1.1 i686-pc-linux-gnu-g++ -o libmumble.so.1.1.0 release/overlay.o -lrt -ldl /usr/lib/gcc/i686-pc-linux-gnu/4.2.2/../../../crt1.o: In function `_start': (.text+0x18): undefined reference to `main' release/overlay.o: In function `glXSwapBuffers': overlay.c:(.text+0x452): undefined reference to `glXGetCurrentContext' overlay.c:(.text+0x50f): undefined reference to `glXQueryContext' overlay.c:(.text+0x54d): undefined reference to `glXQueryContext' overlay.c:(.text+0x5a8): undefined reference to `glXChooseFBConfig' overlay.c:(.text+0x5ed): undefined reference to `glXCreateNewContext' overlay.c:(.text+0x683): undefined reference to `glXMakeCurrent' overlay.c:(.text+0x6d4): undefined reference to `glGenTextures' overlay.c:(.text+0x6e0): undefined reference to `glDisable' overlay.c:(.text+0x6ec): undefined reference to `glDisable' overlay.c:(.text+0x6f8): undefined reference to `glEnable' overlay.c:(.text+0x704): undefined reference to `glDisable' overlay.c:(.text+0x710): undefined reference to `glEnable' overlay.c:(.text+0x71c): undefined reference to `glDisable' overlay.c:(.text+0x728): undefined reference to `glDisable' overlay.c:(.text+0x734): undefined reference to `glDisable' overlay.c:(.text+0x740): undefined reference to `glDisable' overlay.c:(.text+0x74c): undefined reference to `glDisable' release/overlay.o:overlay.c:(.text+0x758): more undefined references to `glDisable' follow release/overlay.o: In function `glXSwapBuffers': overlay.c:(.text+0x7c4): undefined reference to `glEnable' overlay.c:(.text+0x7d0): undefined reference to `glDisable' overlay.c:(.text+0x7dc): undefined reference to `glDisable' overlay.c:(.text+0x7e8): undefined reference to `glDisable' overlay.c:(.text+0x7f4): undefined reference to `glDisable' overlay.c:(.text+0x809): undefined reference to `glBlendFunc' overlay.c:(.text+0x81e): undefined reference to `glColorMaterial' overlay.c:(.text+0x844): undefined reference to `glXMakeCurrent' overlay.c:(.text+0x86d): undefined reference to `glXQueryDrawable' overlay.c:(.text+0x898): undefined reference to `glXQueryDrawable' overlay.c:(.text+0x96b): undefined reference to `glXMakeCurrent' overlay.c:(.text+0x9a6): undefined reference to `glViewport' overlay.c:(.text+0x9b2): undefined reference to `glMatrixMode' overlay.c:(.text+0x9b7): undefined reference to `glLoadIdentity' overlay.c:(.text+0xa13): undefined reference to `glOrtho' overlay.c:(.text+0xa1f): undefined reference to `glMatrixMode' overlay.c:(.text+0xb0d): undefined reference to `glBindTexture' overlay.c:(.text+0xb2b): undefined reference to `glTexParameteri' overlay.c:(.text+0xb49): undefined reference to `glTexParameteri' overlay.c:(.text+0xb67): undefined reference to `glTexParameteri' overlay.c:(.text+0xb85): undefined reference to `glTexParameteri' overlay.c:(.text+0xbdd): undefined reference to `glTexImage2D' overlay.c:(.text+0xd5e): undefined reference to `glBindTexture' overlay.c:(.text+0xd63): undefined reference to `glPushMatrix' overlay.c:(.text+0xd68): undefined reference to `glLoadIdentity' overlay.c:(.text+0xd9b): undefined reference to `glColor4ub' overlay.c:(.text+0xdbd): undefined reference to `glTranslatef' overlay.c:(.text+0xdc9): undefined reference to `glBegin' overlay.c:(.text+0xddd): undefined reference to `glTexCoord2f' overlay.c:(.text+0xdf4): undefined reference to `glVertex2f' overlay.c:(.text+0xe08): undefined reference to `glTexCoord2f' overlay.c:(.text+0xe1c): undefined reference to `glVertex2f' overlay.c:(.text+0xe45): undefined reference to `glTexCoord2f' overlay.c:(.text+0xe60): undefined reference to `glVertex2f' overlay.c:(.text+0xe78): undefined reference to `glTexCoord2f' overlay.c:(.text+0xe8f): undefined reference to `glVertex2f' overlay.c:(.text+0xe94): undefined reference to `glEnd' overlay.c:(.text+0xe99): undefined reference to `glPopMatrix' collect2: ld returned 1 exit status make[2]: *** [../release/libmumble.so.1.1.0] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.1.0/work/mumble-1.1.0/overlay_gl' make[1]: *** [release] Error 2 make[1]: Leaving directory `/var/tmp/portage/media-sound/murmur-1.1.0/work/mumble-1.1.0/overlay_gl' make: *** [sub-overlay_gl-make_default] Error 2 make: *** Waiting for unfinished jobs.... /usr/bin/moc -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus -I.. -Irelease -I. Server.h -o release/moc_Server.cpp
Comment on attachment 137285 [details, diff] fixed mumble-1.1.0-clientonly.patch Ooops, nevermind my uploaded patch. I still had the patching commented out in the ebuild, that's why it seemed to work. So I'm back at the beginning again. Emerging mumble with the 1.1.0 ebuild works if I remove the patch; doesn't work with the patch. Murmur doesn't compile at all.
Created attachment 137549 [details] mumble-1.1.1 w/ PulseAudio support (edit mumble.pro to remove pulseaudio and compile errors) mumble 1.1.1 has been released. I altered the ebuild, so it's able to install it. However, with this version mumble has PulseAudio support. If you don't have PulseAudio installed, the compilation will fail. As of now, pulseaudio can't be excluded via make, so you manually have to edit src/mumble/mumble.pro (line 60) and turn "CONFIG += oss pulseaudio" into "CONFIG += oss". Mumble won't build against pulseaudio then and will successfully compile. This ebuild does NOT contain the client/server only patch and someone would have to write a patch for the pulseaudio thingy. Somehow, I'm unlucky with patches so I leave that for somebody else :P
Created attachment 137674 [details] supports now: client/server only builds, makes pulseaudio optional + release,debug build this ebuild also needs 3 other files to work: -rw-r--r-- 1 root root 355 Dec 3 19:50 mumble-1.1.1-clientonly.patch -rw-r--r-- 1 root root 535 Dec 3 20:39 mumble-1.1.1-disablePulsaudioBuild.patch -rw-r--r-- 1 root root 473 Dec 3 21:13 mumble-1.1.1-serveronly.patch use flags are: pulseaudio disable-client-build disable-server-build by default: client and server is built without pulseaudio support + modified dependencies + added pkg_postinst information
Created attachment 137676 [details] mumble-1.1.1-clientonly.patch
Created attachment 137678 [details] mumble-1.1.1-serveronly.patch
Created attachment 137680 [details] mumble-1.1.1-disablePulsaudioBuild.patch
(In reply to comment #33) > Created an attachment (id=137549) [edit] > mumble-1.1.1 w/ PulseAudio support (edit mumble.pro to remove pulseaudio and > compile errors) > > mumble 1.1.1 has been released. I altered the ebuild, so it's able to install > it. However, with this version mumble has PulseAudio support. If you don't have > PulseAudio installed, the compilation will fail. As of now, pulseaudio can't be > excluded via make, so you manually have to edit src/mumble/mumble.pro (line 60) > and turn "CONFIG += oss pulseaudio" into "CONFIG += oss". Mumble won't build > against pulseaudio then and will successfully compile. > > This ebuild does NOT contain the client/server only patch and someone would > have to write a patch for the pulseaudio thingy. Somehow, I'm unlucky with > patches so I leave that for somebody else :P generating patches is very easy, if you got the right documentation. i usually use this one from masterdriverz which is located here: http://dev.gentoo.org/~masterdriverz/patch.xml
Comment on attachment 137549 [details] mumble-1.1.1 w/ PulseAudio support (edit mumble.pro to remove pulseaudio and compile errors) Very well done, js. I just tried out your ebuild and patches and so far I only built a client+server+no pulse audio build and it worked fine. So, again, applauding to the portage maintainers: I'd vote to get that package in the tree ;)
(In reply to comment #39) > (From update of attachment 137549 [details] [edit]) > Very well done, js. I just tried out your ebuild and patches and so far I only > built a client+server+no pulse audio build and it worked fine. > > So, again, applauding to the portage maintainers: I'd vote to get that package > in the tree ;) > the only thing i've not tested was the 'release' build. the main.pro states to build release_and_debug but in my case only debug was built all the time. a fix here might be needed. the rest is 'well' tested from my side.
(In reply to comment #40) > (In reply to comment #39) > > (From update of attachment 137549 [details] [edit] [edit]) > > Very well done, js. I just tried out your ebuild and patches and so far I only > > built a client+server+no pulse audio build and it worked fine. > > > > So, again, applauding to the portage maintainers: I'd vote to get that package > > in the tree ;) > > > > the only thing i've not tested was the 'release' build. the main.pro states to > build release_and_debug but in my case only debug was built all the time. a fix > here might be needed. the rest is 'well' tested from my side. > 12:56 <@ColdWind> qknight: there's a lot to improve in your mumble ebuild 12:58 <@ColdWind> qknight: all the disable-client-build and disable-server-build should be changed a bit 12:58 <@ColdWind> you may have IUSE="client server" and build both if both are disabled 13:01 <@ColdWind> also, you could ask authors of mumble to make the client/server build configurable, so you don't have to apply those patches in the future 13:02 < qknight> ColdWind: thanks very much for that helpful comments 13:02 < qknight> i'll change that this evenen while i will also write the mumble developers 13:02 <@ColdWind> nice :) 13:03 <@ColdWind> also... look at this: disable-client-build? ( pulseaudio? (media-sound/pulseaudio) ) 13:04 <@ColdWind> I'd write: !server? ( pulseaudio? ( media-sound/pulseaudio ) ) 13:04 <@ColdWind> that's a bit tricky too, but works 13:04 <@ColdWind> (and pay attention to the spaces I added) 13:04 < qknight> but if USE="server client" it won't work anymore 13:04 < qknight> so the dependencies are wrong 13:05 < qknight> however i will try to thake that into account i will have a look at those issues from above but i will also check the debug_and_release issue from last post this evening. stay tuned ;-)
(In reply to comment #41) Btw, automatic PulseAudio detection is already added in mumble's SVN version. Same for automatic SSE recognition (so far all builds were without SSE). But making server/client choosable without patching would be desirable, yup.
Created attachment 137913 [details] mumble-1.1.1.ebuild ColdWind from #gentoo-sunrise on freenode fixed the ebuild which is added to this post. all should be taken into account now and the package is hopefully ready for portage. thanks coldwind! changes are: ++ useflags are called: "server", "client" now instead of "disable-client-build", "disable-server-build" ++ code reduction because of "dir=debug|release" variable ++ default: install client+server without pulseaudio the automatic detection of pulseaudio in mumble svn is nice but the pulseaudio useflag also pulls in pulseaudio dependency if set. however it will make the disablePulsaudioBuild.patch obsolete ;-)
I just tried it and have some remarks: >>> Install mumble-1.1.1 into /var/tmp/portage/media-sound/mumble-1.1.1/image/ category media-sound /var/tmp/portage/media-sound/mumble-1.1.1/temp/environment: line 2509: build_server: command not found >>> /usr/lib64/libmumble.so -> libmumble.so.1.1.1 But libmumble.so.1.1.1 is never installed. >>> /usr/lib64/libspeex.a Shouldn't happen, since it might collide with the system libspeex.
PS: [ebuild R ] media-sound/mumble-1.1.1 USE="client -pulseaudio -server" 0 kB [1]
(In reply to comment #44) > >>> /usr/lib64/libspeex.a > Shouldn't happen, since it might collide with the system libspeex. > Yeah, that issue has been addressed a few times already. The thing is, mumble ships (and most likely always will) with its own speex source/build. Right now, mumble is using a yet unreleased version of speex (1.2_beta3) and really requires all the features in there. So there will most likely be some breakages with the usually installed 1.2_beta2. This should be sorted out somehow, as it's critical. I've got no idea how, leaving that to the portage experts :P (I guess it involves renaming the lib file to some different name, and adjusting the whole mumble/murmur sources to use that changed name).
What is installed is a static lib. Means Mumble already contains everything that is necessary and the lib is now unnecessary. So simply not installing it (or deleting it afterwards) should work.
the 1.1.1 ebuild should be added to portage at least in masked status , it works well here on amd64
Works great for me as well (amd64) got the V1.1.1 murmur working on a remote server as well quite happily REquesting adding to main tree. The mumble in the tree (V0.9...) does NOT compile for AMD64
I just tried it again and the exact same issues persist! It should NOT go into the tree like this. If you need more info to debug this, please ask. Quoting it again: ------ >>> Source compiled. >>> Test phase [not enabled]: media-sound/mumble-1.1.1 >>> Install mumble-1.1.1 into /var/tmp/portage/media-sound/mumble-1.1.1/image/ category media-sound /var/tmp/portage/media-sound/mumble-1.1.1/temp/environment: line 2540: build_server: command not found >>> Completed installing mumble-1.1.1 into /var/tmp/portage/media-sound/mumble-1.1.1/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/bin/mumble usr/lib64/libspeex.a * checking 8 files for package collisions >>> Merging media-sound/mumble-1.1.1 to / --- /usr/ --- /usr/bin/ >>> /usr/bin/mumble >>> /usr/bin/mumble-overlay --- /usr/lib64/ >>> /usr/lib64/libspeex.a --- /usr/share/ --- /usr/share/doc/ >>> /usr/share/doc/mumble-1.1.1/ >>> /usr/share/doc/mumble-1.1.1/README.bz2 >>> /usr/share/doc/mumble-1.1.1/CHANGES.bz2 --- /usr/share/applications/ >>> /usr/share/applications/mumble-mumble.desktop --- /usr/share/pixmaps/ >>> /usr/share/pixmaps/mumble.png >>> /usr/lib64/libmumble.so -> libmumble.so.1.1.1 * * Visit http://mumble.sourceforge.net/Audio_Tuning for futher configuration * type mumble to run the client * you might want to add this to your xorg.conf to get shortcut support * Section "Extensions" * Option "XEVIE" "Enable" * EndSection /var/tmp/portage/media-sound/mumble-1.1.1/temp/environment: line 2248: build_server: command not found * Both mumble/murmurd support dbus for configuration & misc >>> Regenerating /etc/ld.so.cache... >>> media-sound/mumble-1.1.1 merged. ------
Created attachment 139141 [details] patch-log Oh, it also gets better if you either add both USE=client and server or remove both: >>> Unpacking source... >>> Unpacking mumble-1.1.1.tar.gz to /var/tmp/portage/media-sound/mumble-1.1.1/work * Applying mumble-1.1.1-disablePulsaudioBuild.patch ... [ ok ] /var/tmp/portage/media-sound/mumble-1.1.1/temp/environment: line 2567: build_server: command not found * building client only. murmur server building will be disabled * Applying mumble-1.1.1-clientonly.patch ... [ ok ] * building murmur server only. mumble client building will be disabled * Applying mumble-1.1.1-serveronly.patch ... * Failed Patch: mumble-1.1.1-serveronly.patch ! Something seems to be utterly wrong here...
to be fair you wouldn't want to disable server AND client ;) I'm not saying you are wrong the ebuild does need sorting out. The problem seems it was just bumped and tweaked while mumbles build process had changed a fair bit Having one ebuild todo server & client is wrong if you ask me, esp since two separate programs I have an ebuild that does murmur-1.1.1 and that is valid (will post soon) I will go through and tidy this ebuild up
Dennis, I see the problem in #51, but where's the problem in #50? jon r-b, yeah it would indeed be better to have two seperate ebuilds. the thing is just that there is only one source tarball, including both server and client.
Well I got two ebuilds now, submitting
Created attachment 139183 [details] media-sound/mumble-1.1.1.ebuild ebuild for mumble-1.1.1.ebuild Requires the mumble-1.1.1-clientonly.patch and mumble-1.1.1-disablePulsaudioBuild.patch
I know the one tarball contains both client and server, doesn't mean we need one ebuild tho? also there is a means to just build the server, no need for the patch I have attacked the ebuild for murmur + rc and conf file. If you or a dev wants one ebuild then they can be murged back again
Created attachment 139185 [details] media-sound/murmur-1.1.1.ebuild ebuild to just build the mumble (murmur) server
Created attachment 139186 [details] murmur RC file
Created attachment 139187 [details] murmur conf file
Jon: To be honest I didn't want to disable both... (And if I understood the description correctly, USE='client server' should be the same as USE='-client -server'.) They are positive useflags, so I wanted to enable both... If those are disable-this useflags, they should be named noclient and noserver, which afaik the Guide forbids. Sascha: The problem in comment #50 is the exact same as in comment #44 (as I wanted to express with "the exact same issues persist").
Dennis, thats why I have an induvidual ebuild for mumble AND murmur. Only USE flag is PulseAudio
23 Dec 2007; Timothy Redaelli <drizzt@gentoo.org> +files/mumble-1.1.1-path.patch, +mumble-1.1.1.ebuild: Add new media-sound/mumble for testing wrt bug #183781. Sadly doesn't work, loads of: release/AudioInput.o: In function `AudioInput::~AudioInput()': AudioInput.cpp:(.text+0x27a): undefined reference to `spx_fft_destroy' AudioInput.cpp:(.text+0x288): undefined reference to `speex_preprocess_state_destroy' AudioInput.cpp:(.text+0x296): undefined reference to `speex_echo_state_destroy' Maybe because it is missing its own Speex?
very odd... cause I used that ebuild that doesn't merge in its speex and mumble-1.1.1 is working fine with a murmur-1.1.1 server (both based upon these ebuilds) Fluid jrb # emerge mumble speex -vp These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] media-libs/speex-1.2_beta3 USE="ogg sse" 0 kB [ebuild R ] media-sound/mumble-1.1.1 USE="-pulseaudio" 0 kB [1] Fluid jrb # equery belongs /usr/lib64/libspeex.a [ Searching for file(s) /usr/lib64/libspeex.a in *... ] media-libs/speex-1.2_beta3 (/usr/lib64/libspeex.a) might need >=media-libs/speex-1.2 to function then
I've got that, too: [ebuild R ] media-libs/speex-1.2_beta3 USE="ogg sse" 0 kB [ebuild U ] media-sound/mumble-1.1.1 [1.1.0] USE="-pulseaudio% -vanilla%" 0 kB [1=>0]
Hm, as I expected: [ Searching for file(s) /usr/lib64/libspeex.a in *... ] media-libs/speex-1.2_beta3 (/usr/lib64/libspeex.a) media-sound/mumble-1.1.0 (/usr/lib64/libspeex.a) Wonder why collision-protect didn't prevent that... Testing to reemerge both...
Nope, same error. I assume you linked against an old libspeex.a from mumble and not from speex...
VERY odd I unmerged both mumble-1.1.1 and speex-1.2-beta3 and ensured there was no libspeex.a anywhere on the system (even updatedb && locate libspeex.a) emerged both and mumble working fine here
Dennis, w.r.t. [ebuild U ] media-sound/mumble-1.1.1 [1.1.0] USE="-pulseaudio% -vanilla% why have you got a "vanilla" USE flag? are you trying that ebuild I submitted or a modified one?
Strange issue mumble with the latest ebuild seems to build the client correctly with no errors. Mumble even appears to work properly and doesn't throw any errors. My problem is that the second I alt-tab to another desktop the mumble window disappears and the process itself is still running and connected to the murmur server I called. Anyone having a similar problem? I'm on amd64.Tried running it through gdb but since there is no crash I can't get a bt. I also tried to strace the process to see if I could see anything there but all I saw was a bunch of timer calls. chadgentoo Desktop # emerge --info Portage 2.1.4_rc11 (default-linux/amd64/2006.1/desktop, gcc-4.2.2, glibc-2.7-r1, 2.6.23-gentoo-r3 x86_64) ================================================================= System uname: 2.6.23-gentoo-r3 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ Timestamp of tree: Mon, 24 Dec 2007 09:00:01 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.1.3 dev-lang/python: 2.4.4-r4, 2.5.1-r4 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 dev-util/confcache: 0.4.2-r1 sys-apps/baselayout: 1.12.10-r5 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.23-r2 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -msse3 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/NX/etc /usr/NX/home /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /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/splash /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=k8 -msse3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans user-sandbox userfetch userpriv" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/sunrise /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d a52 aac aalib acct acl acpi aio alsa amd64 amr apache2 apm asf athena bash-completion berkdb bitmap-fonts blas bzip2 cairo ccache cddb cdr cgi cli commercial cracklib crypt css cups curl cvs daap dbus divx dnd dri dts dvd dvdnav dvdr dvdread eds emboss emerald encode escreen esd exif extensions fam fame fat ffmpeg fftw firefox flac fortran gd gdbm gif glitz glx gmail gmailtimestamps gnome gnutls gpm gstreamer gtk gtk2 hal hddtemp hpn httpd iconv ieee1394 imagemagick ipod ipv6 isdnlog joystick jpeg kde kdeenablefinal kdehiddenvisibility kdenablefinal lcms ldap libcaca lm_sensors lzo mad midi mikmod mjpeg mmap mp2 mp3 mp4 mpeg mpi mplayer mplayer-bin mpm-worker mudflap mysql ncurses network network-cron nls nptl nptlonly nsplugin nvidia nxclient ocaml offensive ogg openal opengl openmp oss pam pcre pdf perl php pic plugins png ppds pppd python qt3 qt4 quicktime readline realmedia reflection reiserfs rtc rtsp sdl session sftplogging shout smp snmp spell spl sqlite3 ssl ssse3 stream subversion svg tcpd theora threads truetype truetype-fonts type1-fonts unicode upnp usb vorbis wmp x264 xcomposite xml xml2 xorg xscreensaver xv xvid xvmc yv12 zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci 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 rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev mouse keyboard joystick" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I used Timothy's, which is in the tree. (Quoted from its changelog...) Yours had quite some other problems I needed to fix. Can send the corrected one later. (If you don't have it by newyear, remind me again. ;) )
(In reply to comment #69) > Strange issue mumble with the latest ebuild seems to build the client correctly > with no errors. Mumble even appears to work properly and doesn't throw any > errors. My problem is that the second I alt-tab to another desktop the mumble > window disappears and the process itself is still running and connected to the > murmur server I called. Anyone having a similar problem? I'm on amd64.Tried > running it through gdb but since there is no crash I can't get a bt. I also > tried to strace the process to see if I could see anything there but all I saw > was a bunch of timer calls. Here on KDE mumble reduces itself to a little icon in the taskbar, if you click the window's minimize button. maybe the same happens if you switch desktops? i'm not that proficient with all the kinds of WMs out there, but if you use one which doesn't support tray icons, that's where mumble might get lost for you :P
(In reply to comment #71) > (In reply to comment #69) > > Strange issue mumble with the latest ebuild seems to build the client correctly > > with no errors. Mumble even appears to work properly and doesn't throw any > > errors. My problem is that the second I alt-tab to another desktop the mumble > > window disappears and the process itself is still running and connected to the > > murmur server I called. Anyone having a similar problem? I'm on amd64.Tried > > running it through gdb but since there is no crash I can't get a bt. I also > > tried to strace the process to see if I could see anything there but all I saw > > was a bunch of timer calls. > > > Here on KDE mumble reduces itself to a little icon in the taskbar, if you click > the window's minimize button. maybe the same happens if you switch desktops? > i'm not that proficient with all the kinds of WMs out there, but if you use one > which doesn't support tray icons, that's where mumble might get lost for you :P > Sorry I don't know how I missed that. Is there anyway to have mumble stay full screen on one desktop when you alt-tab to another desktop? I can't seem to figure out how to disable the auto hide to tray icon.
Compilation failed. emerge outpout: http://pastebin.ca/837300 emerge --info: http://pastebin.ca/837434
the above 1.1.1 ebuild worked fine , however i've merged the version that is in portage now and it segfaults when there is audio playback ( someone says something and you segfault ) , i've compared the two ebuilds and they differ slightly , most noticeable is the lack of mumble-1.1.1-disablePulsaudioBuild.patch in the ebuild from the portage tree , could this be the cause of the segfaults ??
not really. all the patch does is what the sed line does in the portage ebuild I am still surpriesed that you can build this using the portage 1.1.1 ebuild this is probably due to the speex.a in /usr/lib64 is actually from mumble-1.1.1 (you emerged before collision prevention occured) thus you are using a speex.a from mumble and not from speex package moo
Seems the issue is with the version of speex in the tree (speex-1.2beta3) and what mumble-1.1.1 needs (they are working from a frozen csv build that they packagage) so I'm gonna try to get a speex-csv ebuild up and running. when speex-1.2 is released it should all be fine
sorted \o/ got the in-portage ebuild building, after an extra line added mumble ships with a copy of speex within it and it is speex-1.2beta3 HOWEVER it builds the libspeex.a with alot of the object files, while speex-1.2beta3 actually makes an extra lib (libspeexdsp.so) so 1) dependancy chance to speex-1.2beta3 2) sed -i -e "s:\(-lspeex\):\1 -lspeexdsp:" "${S}"/src/mumble/mumble.pro inserted NOTE: the speex ebuild really should be updated as well to install the libspeex headers
Created attachment 139746 [details] /media-sound/mumble-1.1.1.ebuild update
Hi there... These ebuilds work quite fine here on my amd64 box and my amd64 server. I am talking on it right now...
Created attachment 139993 [details] media-sound/mumble update with qt USE dependancies
(In reply to comment #77) > NOTE: the speex ebuild really should be updated as well to install the libspeex > headers > huh? what do you call these then.. /usr/include/speex/speex_echo.h /usr/include/speex/speex_types.h /usr/include/speex/speex_resampler.h /usr/include/speex/speex_buffer.h /usr/include/speex/speex_bits.h /usr/include/speex/speex_callbacks.h /usr/include/speex/speex_jitter.h /usr/include/speex/speex.h /usr/include/speex/speex_config_types.h /usr/include/speex/speex_header.h /usr/include/speex/speex_stereo.h /usr/include/speex/speex_preprocess.h installed by speex-1.2_beta3 (also now going stable) unless you mean some internal headers, that shouldn't be used.
*mumble-1.1.1 (23 Dec 2007) 23 Dec 2007; Timothy Redaelli <drizzt@gentoo.org> +files/mumble-1.1.1-path.patch, +mumble-1.1.1.ebuild: Add new media-sound/mumble for testing wrt bug #183781. InCVS. Anything else -> a NEW bug. Closing this mess.
