Re: Bug#792921: [sparc64] linking against libx264 crashes runtime linker
On Tue, Jul 21, 2015 at 2:49 PM, Andreas Cadhalpun wrote: > On 20.07.2015 17:18, Carlos O'Donell wrote: >> On Mon, Jul 20, 2015 at 3:35 AM, Andreas Cadhalpun >> wrote: >>> Program received signal SIGBUS, Bus error. >>> 0xf801cda4 in elf_dynamic_do_Rela (skip_ifunc=, >>> lazy=0, nrelative=, relsize=, >>> reladdr=, map=0xf80100023570) at do-rel.h:111 >> >> Usually a corrupted library. Check md5sums. > > I don't think this problem is caused by a corrupted libx264. > > First, it's also happening on the sparc64 buildds, see e.g. [1]. > Second, I rebuilt the current x264 locally and it shows the same problem. Does the problem always reproduce or just sometimes? If it's just sometimes then it's much much harder to figure out what's wrong. You'll need a dedicated person to track down exactly what is the concurrency issue and why it's failing. Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAE2sS1hiWgvUJb-RZX5O3=MCWZ=zbyojs_urnogodtzfkuv...@mail.gmail.com
Re: Current and upcoming toolchain changes for jessie
On Tue, Jun 18, 2013 at 8:02 PM, John David Anglin wrote: > Hi Aurelien, > > > On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote: > >> This is true that they have recently contacted me through another email >> address, but I haven't found time to work on that. Just stay tuned. > > > That's great news. > > Helge and I have been working away as best we can to maintain the port. I > know everybody is busy and this is a significant effort. ... and I'm incredibly busy with upstream glibc, but I'm trying my best to ensure hppa keeps building upstream glibc. Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAE2sS1g+63BWgBfwV8pHzRAQrpzv2V_AhZ9AmPsm4Y-h8=g...@mail.gmail.com
Re: GCC-4.5 as the default for (at least some) architectures
On Tue, Mar 1, 2011 at 8:34 PM, Matthias Klose wrote: > I'll make gcc-4.5 the default for (at least some) architectures within the > next > two weeks before more transitions start. GCC-4.5 is already used as the > default > compiler for almost any other distribution, so there shouldn't be many > surprises > on at least the common architectures. About 50% of the build failures exposed > by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > (although optimized for a different processor) and powerpc (some object files > linked into shared libs had to be built as pic). > > As the maintainer file for the ports in GCC is a bit outdated, I'd like to ask > which architectures should do the switch together with the four architectures > mentioned above, and which not, and which ones should be better delayed, or > dropped. Dave, What's your opinion on switching to GCC 4.5 for HPPA? Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinznkgbhpaqc7hd6peyppr8da+1iponh1im6...@mail.gmail.com
Re: Glibc upload this weekend
> > The arm bug isn't fixed in CVS - It's a toolchain problem that I'll work > around with a local hack to disable combreloc. HPPA hasn't submitted > yet. Last I heard ia64's patch wasn't in CVS yet, and I have no idea > what's up with Sparc. So it doesn't seem like post of the arch bugs are > in CVS right now. I hope we can change that, though. > > Let's see how necessary it is. We can always do a CVS pull after this > upload. > HPPA glibc 2.3.1 is completed, and I just finished writing the last of the 6 changelogs for the upstream patches. I began working on the debian package install and found a few issues in my chroot (as you will notice by my recent post to debian-glibc). My own personal testing was rather lax, and I've set myself the firm goal of doing a better job for the next glibc release. As such I'm doing an install on three chroots unstable/testing/stable and finally a live system test. Patches get the usual treatment of testing with the glibc testsuite, and HPPA hasn't gotten any prettier, any worse. I'm also taking care not to break x86 and Alpha with these patches (if you have a fast PowerPC box you would like to send me for testing purposes... there is still space on my rack for it :). I hope to have testing started and completed between Friday->Saturday. With upstream patches posted tommorow. c.
Re: a small C program to test xdm's /dev/mem reading on your architecture
Branden, > The long story, for those interested: > http://lists.debian.org/debian-x/2002/debian-x-200208/msg00091.html > (and read the whole thread) > The short story: > I need people with root on machines of your given architecture to > compile and run the attached C program. It consists of code borrowed > from xdm's genauth.c program. > Done. I've submitted the output for HPPA boxes running 32 and 64-bit kernels. Looks like they pass without any problem. I'll pass on the test results for an older 715/50 box (the other boxes were an A500 and C3K). Secondly, I will open a big can a whoopass on anyone else I see complaining about /dev/mem reading without providng a patch >:) Branden is merely asking you to _test_ something. c.
