hello
lili_ed...@yahoo.com It is my great pleasure establishing a contact with you when i saw your Email hoping we can be friends contact me with this (lili_ed...@yahoo.com) looking forward to hearing from you Lili___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
On Tue, Feb 26, 2013 at 10:45 PM, Roland Stigge sti...@antcom.de wrote: On 26/02/13 19:32, Reinhard Tartler wrote: TBH, I do not feel comfortable with maintaining this patch outside of libav, escp. since upstream already does take care about unusual environments. The libav packaging is already complicated enough. Therefore, I would like to ask you to reconsider your decision to implement this with configure switches instead of implementing the logic in the configuration script. I'm not quite sure what you mean by this since the only patch I proposed is to the Debian files which currently already disable altivec on powerpc - and the patch adds the same for powerpcspe. Well, the difference is who has to maintain that change. I am not willing to maintain handling powerpcspe in debian/rules because this is something that they upstream configure script is in a much better position to handle. -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
On Tue, Feb 26, 2013 at 10:32 PM, Roland Stigge sti...@antcom.de wrote: OTOH, I wonder why the gcc and the toolchain on this port do not set the proper default flags by themselves. Since http://wiki.debian.org/PowerPCSPEPort does not clarify this either, can you perhaps jump in here? ...however, -maltivec is still present but doesn't make sense to enable at the same time with e500, hence compile errors. I don't understand this. Why does gcc on powerpcspe enable altivec by default? If powerpcspe ships a gcc that has broken default settings, then this should be fixed first. I have noticed that you have filed a similar bug against mplayer, and suspect that you have filed many more bugs. Is it possible that with fixed gcc default settings, no changes would be necessary in mplayer, libav and possibly many other packages? -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
Hi Reinhard,
On 02/27/2013 02:57 PM, Reinhard Tartler wrote:
I don't understand this. Why does gcc on powerpcspe enable altivec by
default? If powerpcspe ships a gcc that has broken default settings,
then this should be fixed first.
I had a second look at this, and it turned out that it's actually a bug
in upstream's configure. Consider the attached patch: Some lines before,
configure decides, contrary to the default on generic powerpc, that
altivec is not available (disable altivec, e.g. on powerpcspe).
However, in this case it still aborts and complains about some AltiVec
detail that should be ignored in case AltiVec is correctly detected as
disabled.
So using this new patch instead would be good.
An additional:
ifeq ($(DEB_HOST_ARCH),powerpcspe)
confflags += --enable-pic -cpu=e500v2
endif
... in debian/confflags would be nice, though (similar to arch powerpc).
I have noticed that you have filed a similar bug against mplayer, and
suspect that you have filed many more bugs. Is it possible that with
fixed gcc default settings, no changes would be necessary in mplayer,
libav and possibly many other packages?
Right, I filed quite some bugs as you guessed. :-) Feel free to have a
look at
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=powerpcspe;users=debian-powerpc...@breakpoint.cc
Fortunately, libav's and mplayer2's configure are not very
representative. ;-) The majority of the other bugs are fixes in other
places or plain activation of powerpcspe.
Will file a similar upstream fix to the mplayer2 package/bug.
Roland
--- libav-0.8.5/configure.orig 2013-02-27 15:52:13.013650621 +0100
+++ libav-0.8.5/configure 2013-02-27 17:19:08.898946263 +0100
@@ -2730,10 +2730,12 @@
EOF
# check if our compiler supports braces for vector declarations
-check_cc EOF || die You need a compiler that supports {} in AltiVec vector declarations.
+if enabled altivec ; then
+check_cc EOF || die You need a compiler that supports {} in AltiVec vector declarations.
$inc_altivec_h
int main (void) { (vector int) {1}; return 0; }
EOF
+fi
fi
elif enabled sparc; then
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge sti...@antcom.de wrote: Hi Reinhard, On 02/27/2013 02:57 PM, Reinhard Tartler wrote: I don't understand this. Why does gcc on powerpcspe enable altivec by default? If powerpcspe ships a gcc that has broken default settings, then this should be fixed first. I had a second look at this, and it turned out that it's actually a bug in upstream's configure. Please propose a patch to fix that instead of changing debian/rules then. ... in debian/confflags would be nice, though (similar to arch powerpc). I have noticed that you have filed a similar bug against mplayer, and suspect that you have filed many more bugs. Is it possible that with fixed gcc default settings, no changes would be necessary in mplayer, libav and possibly many other packages? Right, I filed quite some bugs as you guessed. :-) Feel free to have a look at http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=powerpcspe;users=debian-powerpc...@breakpoint.cc Fortunately, libav's and mplayer2's configure are not very representative. ;-) The majority of the other bugs are fixes in other places or plain activation of powerpcspe. Will file a similar upstream fix to the mplayer2 package/bug. You did not answer my question/suggestion at all. Can you please comment on my suggestion to fix the gcc package? -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
Hi Reinhard, On 02/27/2013 05:47 PM, Reinhard Tartler wrote: On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge sti...@antcom.de wrote: Hi Reinhard, On 02/27/2013 02:57 PM, Reinhard Tartler wrote: I don't understand this. Why does gcc on powerpcspe enable altivec by default? If powerpcspe ships a gcc that has broken default settings, then this should be fixed first. I had a second look at this, and it turned out that it's actually a bug in upstream's configure. Please propose a patch to fix that instead of changing debian/rules then. In the last mail (that you cite) there is a new patch attached. This patch alone fixes the issue completely (an upstream bug), without changes to debian/* at all. Will file a similar upstream fix to the mplayer2 package/bug. You did not answer my question/suggestion at all. Can you please comment on my suggestion to fix the gcc package? I don't consider this a gcc bug. It's working fine in the powerpcspe scene for many years now. You should just refrain from explicitly activating -maltivec and everything is fine. Thanks, Roland ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701595: mplayer2: FTBFS on powerpcspe
Hi,
Reinhard Tartler pointed me to a similar issue in libav, and it turned
out to be an upstream bug in configure.
I'm attaching a new patch that fixes the issue in upstream's configure
alone: After detecting that altivec is missing, we can also ignore the
detail about the AltiVec {} syntax instead of aborting.
Thanks,
Roland
Index: mplayer2-2.0-554-gf63dbad/configure
===
--- mplayer2-2.0-554-gf63dbad.orig/configure 2013-02-27 15:58:44.0 +
+++ mplayer2-2.0-554-gf63dbad/configure 2013-02-27 16:41:41.027281546 +
@@ -2498,6 +2498,8 @@
_altivec_gcc_flags=none, AltiVec disabled
fi
fi
+else
+ _altivec=no
fi
echores $_altivec_gcc_flags
@@ -2506,7 +2508,9 @@
$inc_altivec_h
int main(void) { (vector int) {1}; return 0; }
EOF
-cc_check $_altivec_gcc_flags || die You need a compiler that supports {} in AltiVec vector declarations.
+if [ $_altivec = yes ] ; then
+ cc_check $_altivec_gcc_flags || die You need a compiler that supports {} in AltiVec vector declarations.
+fi
# Disable runtime cpudetection if we cannot generate AltiVec code or
# AltiVec is disabled by the user.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701710: libav: FTBFS on powerpcspe
On Wed, Feb 27, 2013 at 5:53 PM, Roland Stigge sti...@antcom.de wrote: Hi Reinhard, On 02/27/2013 05:47 PM, Reinhard Tartler wrote: On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge sti...@antcom.de wrote: Hi Reinhard, On 02/27/2013 02:57 PM, Reinhard Tartler wrote: I don't understand this. Why does gcc on powerpcspe enable altivec by default? If powerpcspe ships a gcc that has broken default settings, then this should be fixed first. I had a second look at this, and it turned out that it's actually a bug in upstream's configure. Please propose a patch to fix that instead of changing debian/rules then. In the last mail (that you cite) there is a new patch attached. This patch alone fixes the issue completely (an upstream bug), without changes to debian/* at all. Oh, I'm sorry. No I've seen it. Sorry for the confusion, I will forward it to upstream shortly. Will file a similar upstream fix to the mplayer2 package/bug. You did not answer my question/suggestion at all. Can you please comment on my suggestion to fix the gcc package? I don't consider this a gcc bug. It's working fine in the powerpcspe scene for many years now. You should just refrain from explicitly activating -maltivec and everything is fine. Ah, so you say that libav's configure need to check if the compiler actually supports altivec before forcefully enabling it. That sounds like a very valid feature enhancement. Again, sorry for the confusion and thanks for your patch! -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701830: vlc: FTBFS on powerpcspe (illegal insns due to -mtune=G4)
Source: vlc
Version: 2.0.5-1
Severity: wishlist
Tags: patch sid
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe
Hi,
vlc FTBFS on powerpcspe[1] like this:
[...]
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..
-DMODULE_STRING=\libvlc\ -I../include -I../include -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security
-Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast
-Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var
-Werror-implicit-function-declaration -pipe -fvisibility=hidden -ffast-math
-funroll-loops -fomit-frame-pointer -mtune=G4 -MT error.lo -MD -MP -MF
.deps/error.Tpo -c error.c -fPIC -DPIC -o .libs/error.o
{standard input}: Assembler messages:
{standard input}:434: Error: Unrecognized opcode: `stfd'
{standard input}:435: Error: Unrecognized opcode: `stfd'
{standard input}:436: Error: Unrecognized opcode: `stfd'
{standard input}:437: Error: Unrecognized opcode: `stfd'
{standard input}:438: Error: Unrecognized opcode: `stfd'
{standard input}:439: Error: Unrecognized opcode: `stfd'
{standard input}:440: Error: Unrecognized opcode: `stfd'
{standard input}:441: Error: Unrecognized opcode: `stfd'
make[2]: *** [error.lo] Error 1
make[1]: *** [override_dh_auto_configure] Error 2
make[2]: Leaving directory `/«PKGBUILDDIR»/lib'
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
As you can see above, -mtune=G4 is used by default, leading to the above
illegal instructions. The attached patch fixes this by enabling altivec only on
powerpc _except_ powerpcspe, and doing confflags += --with-tuning=8548 which
is propagated to gcc as -mtune=8548 on powerpcspe.
Thanks,
Roland
[1] http://wiki.debian.org/PowerPCSPEPort
-- System Information:
Debian Release: 7.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)
Kernel: Linux 3.8.0 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
--- vlc-2.0.5/debian/rules.backup 2013-02-27 11:42:44.417931459 +0100
+++ vlc-2.0.5/debian/rules 2013-02-27 12:58:16.251057655 +0100
@@ -194,13 +194,18 @@
endif
# PowerPC specific optimizations
-ifneq ($(filter $(DEB_HOST_ARCH_CPU),powerpc),)
+ifeq ($(filter powerpc,$(DEB_HOST_ARCH_CPU))-$(filter powerpcspe,$(DEB_HOST_ARCH)),powerpc-)
confflags += --enable-altivec
else
confflags += --disable-altivec
removeplugins += altivec
endif
+# PowerPCSPE specific optimizations
+ifeq ($(DEB_HOST_ARCH),powerpcspe)
+confflags += --with-tuning=8548
+endif
+
%:
dh $@ --parallel --with autoreconf
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#665732: reopen: vlc: GUI latency/unresponsiveness to clicks on control options
Rémi Denis-Courmont wrote: tags 665732 = moreinfo help unreproducible thanks Hello, Le mardi 26 février 2013 17:33:21, Johann Klammer a écrit : Adding a usleep(1) after the last aout_unlock() in aout_DecPlay() in src/audio_output/dec.c solves the problem for me. Unfortunately that does not really help pinpoint the problem. It is likely a race, but it could be anywhere. Without a stack trace of the freeze or a way to reproduce the problem, there is nothing I, as a VLC developer, can do about this bug report. Could only find those two points where the audio output lock was taken... Changing volume (with ALSA) exhibits a noticeable delay of a few tenth of a second, due to buffering in the ALSA driver. That is neither new and nor fixable. Several seconds of delay is abnormal. it's more than just seconds(perhaps because it's single core box)... Lockup can be broken by doing stuff to shake up the scheduling... switching console-xorg, disk activity etc.. While a kernel bug cannot be completely ruled out, a bug in libpthread seems more probable. With that in mind, it would be good to know if the bug reproduces with *unoptimized* libpthread builds (on i386, this can be achieved by removing the libc6-i686 package). I am using the i386 versions of everything... Starting the gdb while it's locked up shows that it blocks in ___lll_lock_wait in eglibc's lowlevellock.S... the i486 variant...(there's no i386 because of xchg insn) ...also it's the same for i686(which just includes the 486 version)... And there's a __GI_poll done somewhere inside libasound. ...it sleeps there... Yes, the sched_yield() does the trick, too. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#665732: reopen: vlc: GUI latency/unresponsiveness to clicks on control options
tags 665732 + fixed-upstream thanks Fixed in VLC 2.1.0 (1.3.0-git-5708-gf788153). -- Rémi Denis-Courmont http://www.remlab.net/ ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: Bug#665732: reopen: vlc: GUI latency/unresponsiveness to clicks on control options
Processing commands for cont...@bugs.debian.org: tags 665732 + fixed-upstream Bug #665732 [vlc] vlc: GUI latency/unresponsiveness to clicks on control options Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 665732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701841: mp3fs: version 0.32 was released last year
Package: mp3fs Version: 0.31-28-g7b30a54-1 Severity: wishlist Dear Maintainer, version 0.32 was released 2012-06-18: Important changes in 0.32 (2012-06-18) This release has a lot of bug fixes and some code cleanup. Changes in this release: * The file size calculation should always be correct. * A crash affecting programs like scp that might try to access past the end of the file has been fixed. * Too many other little fixes were made to list here. See the ChangeLog for full details. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#701841: marked as done (mp3fs: version 0.32 was released last year)
Your message dated Wed, 27 Feb 2013 20:37:49 + with message-id camhuwoyz6lt7arlkj6pozyyzebbs00wycveug+gapxxz+fh...@mail.gmail.com and subject line Re: Bug#701841: mp3fs: version 0.32 was released last year has caused the Debian Bug report #701841, regarding mp3fs: version 0.32 was released last year to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mp3fs Version: 0.31-28-g7b30a54-1 Severity: wishlist Dear Maintainer, version 0.32 was released 2012-06-18: Important changes in 0.32 (2012-06-18) This release has a lot of bug fixes and some code cleanup. Changes in this release: * The file size calculation should always be correct. * A crash affecting programs like scp that might try to access past the end of the file has been fixed. * Too many other little fixes were made to list here. See the ChangeLog for full details. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 0.31-28-g7b30a54-1 On Wed, Feb 27, 2013 at 8:27 PM, Nemo Inis nemoi...@hotmail.com wrote: This release has a lot of bug fixes and some code cleanup. Changes in this release: * The file size calculation should always be correct. * A crash affecting programs like scp that might try to access past the end of the file has been fixed. * Too many other little fixes were made to list here. See the ChangeLog for full details. As you can see here [1] the version available in testing already provides the latest fixes, it is the 0.32 de facto. Regards, [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/mp3fs.git;a=commitdiff;h=0f745171b9 -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A---End Message--- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
