I am not a Debian s390x porter, per se, and I don't know much about
Debian package maintaining. But if you want to create your own virtual
s390x machine for testing purposes, perhaps the following web page
will be helpful to you:
http://users.wowway.com/~zlinuxman/hercules.htm
--
.''`.
Control: tag -1 confirmed
On Tue, Feb 25, 2014 at 08:14:12AM -0500, Reinhard Tartler wrote:
Nevertheless, dear s390x porters, please help with fixing this issue.
Some digging shows that relocations are broken in the version running
via yorck:
| Dump of assembler code for function
Processing control commands:
tag -1 confirmed
Bug #726733 [libavformat-dev] av_register_all() segfaults on s390x in some cases
Added tag(s) confirmed.
--
726733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
tags 726733 help
stop
On Tue, Jan 14, 2014 at 11:09 PM, Reinhard Tartler siret...@gmail.com wrote:
Mostly for my own reference, I noticed this from the buildlog
https://buildd.debian.org/status/fetch.php?pkg=libavarch=s390xver=6%3A9.10-2stamp=1388850961:
env
On Thu, Nov 14, 2013 at 5:26 PM, Florian Schlichting f...@debian.org wrote:
Hi,
mpd also FTBFS since I enabled the build tests in 0.18 (no regression
here either).
Reinhard asked for a backtrace, this is what I get in the
sid_s390x-dchroot on zelenka:
fsfs@zelenka ~/mpd-0.18.3 % gdb
Mostly for my own reference, I noticed this from the buildlog
https://buildd.debian.org/status/fetch.php?pkg=libavarch=s390xver=6%3A9.10-2stamp=1388850961:
env
Processing control commands:
retitle -1 av_register_all() segfaults on s390x in some cases
Bug #726733 [libavformat-dev] av_register_all() segfaults on s390x in some
cases (regression, causes FTBFS)
Changed Bug title to 'av_register_all() segfaults on s390x in some cases' from
Control: retitle -1 av_register_all() segfaults on s390x in some cases
Control: severity -1 normal
Control: thanks
Hi,
Downgrading the severity as it's actually not a regression: the package
always failed building on s390x with the same error message. I thought I
did my homework and checked
Dear Reinhard,
Le 03/11/2013 02:11, Reinhard Tartler a écrit :
Hi Thibaut,
can you perhaps also provide a backtrace? It seems that there are no
public s390x porter machines where I could get that myself.
Unfortunately, I can't: gdb seems to be broken on s390x. Reporting bug
as we speak:
On Sat, 2013-11-02 at 21:11 -0400, Reinhard Tartler wrote:
can you perhaps also provide a backtrace? It seems that there are no
public s390x porter machines where I could get that myself.
adsb@zelenka:~$ schroot --list | grep s390x
chroot:experimental_s390x-dchroot
chroot:jessie_s390x-dchroot
Hi Thibaut,
can you perhaps also provide a backtrace? It seems that there are no
public s390x porter machines where I could get that myself.
Also, I wonder why s390x would require -DPIC -fPIC in compilation
flags, but s390 would not.
___
Here comes the minimal example. See file README.
buggy.tgz
Description: application/compressed-tar
signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
On Fri, Oct 18, 2013 at 01:51:41PM +, Thibaut Paumard wrote:
Package: libavformat-dev
Version: 6:9.10-1
Severity: serious
File: /usr/include/libavformat/avformat.h
Hi,
My package yorick-av fails to build on s390x:
https://buildd.debian.org/status/package.php?p=yorick-av
It used
Package: libavformat-dev
Version: 6:9.10-1
Severity: serious
File: /usr/include/libavformat/avformat.h
Hi,
My package yorick-av fails to build on s390x:
https://buildd.debian.org/status/package.php?p=yorick-av
It used to build fine previously.
After investigation, I can build a minimal example
14 matches
Mail list logo
