Re: Bit from the Release Team: Status of hppa
On 2010-09-23, Thibaut VARÈNE vare...@debian.org wrote: I think it's been sufficiently documented on this m-l that hppa is/was in a releasable state (d-i works, upgrade works, etc) so this is mostly moot, and the cause of my personal disinterest for Debian given the way things were handled. as long as we need to have a usleep(1000) in the threading code in Qt for happa because of lowlevel bugs in order to just have things working a bit, I don't think hppa is in a releasable state. I haven't heard of any progress on that issue for very long. /Sune -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrni9ng2b.rvp.nos...@sshway.ssh.pusling.com
Re: FTBFS [hppa]: Assertion `y.isApprox(m*x)' failed.
severity 579424 serious thanks On Tuesday 29 June 2010 01:48:15 Matthias Klose wrote: severity 579424 important tag 579424 + moreinfo thanks the bug report mentions a workaround, lowering severity. Hi I don't see it as a workaround, unless the default gcc on hppa is changed to 4.3. The bug is when compiling c++ template header files shipped by the -dev package. Alternatively, please advice on how to ensure that all users of libeigen2-dev (a c++ template header only library) uses g++4.3 ? As I don't consider the workaround viable, I'm raising the severity again. And I hope that the hppa people can provide tests with g++4.5 and snapshots. It is not currently available on the porter boxes. /Sune -- How to debug the e-mail from the control drawer inside LinuxPPC 2000? From DOS and from Windows XP you must turn off a analogic DirectX connection for sending to the Ultra-wide minitower. -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201006290229.53992.s...@debian.org
Re: kde4libs vs qt4
On Wednesday 11 June 2008, Helge Deller wrote: Hello Sune, Sune Vuorela wrote: I now hacked a bit and got stuff working on one of those cluster machines. http://svn.debian.org/wsvn/pkg-kde/trunk/packages/qt4- x11/debian/patches/72_generic_arch_atomic_header_fix.diff?op=filerev=0s c=0 This isn't the real solution though. Qt4 has arch specific code for most archs (and a generic arch mostly used for bootstrapping of Qt), but no arch for linux/hppa, so we use the generic arch here. The real solution involves some hppa assembler (which is way out of my league). There is a patch in the package by lamont about patching the hpux code, but I couldn't get taht to work with my quick tests. Attached are the basic pieces which should get it working with the qt4-x11_4.4.0-3 source package. My machine is still compiling, but it seems OK so far... Okay. This piece makes configure detect hppa as a parisc-architecture: diff -up ./debian/patches/07_trust_dpkg-arch_over_uname-m.diff.org ./debian/patches/07_trust_dpkg-arch_over_uname-m.diff --- ./debian/patches/07_trust_dpkg-arch_over_uname-m.diff.org 2008-06-11 23:34:12.0 +0200 +++ ./debian/patches/07_trust_dpkg-arch_over_uname-m.diff 2008-06-11 23:34:23.0 +0200 @@ -22,7 +22,7 @@ Reported to trolltech as N180631 - and t + UNAME_MACHINE=armv5tel + ;; + hppa) -+UNAME_MACHINE=parisc64 ++UNAME_MACHINE=parisc + ;; + hurd-i386) + UNAME_MACHINE=i686-AT386 This part is definately wrong, as this gets hardcoded into the binaries and changes here will make all modules refuse to load. I think doing something around line 2333 of configure might work. Full patch attached as well, just in case my mailer breaks the lines. Could you test it ? Do you need more ? There is some tests here: http://chaos.troll.no/~bhughes/qatomicint/ http://chaos.troll.no/~bhughes/qatomicpointer/ and trying to build kde4libs (experimental) against it might also show something. I would like if some of you hppa people could test it a bit. I don't feel like throwing it at the debian buildds before that, as it takes a couple of days on some archs to build. /Sune -- I'm not able to reset the GPU, how does it work? The point is that you neither have to insert a TCP/IP provider on a head of a bus of the Ultra-wide GUI, nor can ever digit from the 4-bit IDE prompt, so that from Photoshop or from the tools within Outlook 93 you should ping the front-side bus for saving on a clock to a controller over the command prompt. signature.asc Description: This is a digitally signed message part.
Re: kde4libs vs qt4
On Friday 06 June 2008, Thibaut VARENE wrote: On Fri, Jun 6, 2008 at 12:53 PM, Sune Vuorela [EMAIL PROTECTED] wrote: Paer.debian.org is currently locked down, so there is not much I can do about it myself. Just for the records, your access to the ESIEE cluster is just a matter of sending me a non-compromised ssh key ;) HTH I now hacked a bit and got stuff working on one of those cluster machines. http://svn.debian.org/wsvn/pkg-kde/trunk/packages/qt4- x11/debian/patches/72_generic_arch_atomic_header_fix.diff?op=filerev=0sc=0 This isn't the real solution though. Qt4 has arch specific code for most archs (and a generic arch mostly used for bootstrapping of Qt), but no arch for linux/hppa, so we use the generic arch here. The real solution involves some hppa assembler (which is way out of my league). There is a patch in the package by lamont about patching the hpux code, but I couldn't get taht to work with my quick tests. To be inspired on what is needed, looking at other archs could be a inspiration: qt4-x11-4.4.0$ find . | grep s390 ./src/corelib/arch/s390 ./src/corelib/arch/s390/arch.pri ./src/corelib/arch/qatomic_s390.h ./include/QtCore/qatomic_s390.h ./include/Qt/qatomic_s390.h qt4-x11-4.4.0$ find . | grep parisc ./src/corelib/arch/parisc ./src/corelib/arch/parisc/q_ldcw.s ./src/corelib/arch/parisc/qatomic_parisc.cpp ./src/corelib/arch/parisc/arch.pri ./src/corelib/arch/qatomic_parisc.h ./include/QtCore/qatomic_parisc.h ./include/Qt/qatomic_parisc.h And please use arch hppa as a name, as parisc here means hpux. Qt upstream (trolltech) describes linux/hppa as community suppported, which means that they aren't really interested, but might accept patches. /Sune -- Genius, I cannot ping a cable, how does it work? First you can never click a kernel in order to overclock the software. signature.asc Description: This is a digitally signed message part.
kde4libs vs qt4
Hi! I have been trying to poke a couple of times on #parisc about kde4libs/experimental vs qt4.4 build failures. Bug report here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475767 and full build log here: http://buildd.ayous.org/fetch.php?pkg=kde4libsarch=hppaver=4%3A4.0.80-1stamp=1211907775file=logas=raw I would like to ask again. Could someone with hppa access try to take a look at it? And yes, there is lots of arch specific codepaths in Qt, especially in that area of the Qt headers. Paer.debian.org is currently locked down, so there is not much I can do about it myself. Some people on #parisc suggested the following: in fact i'd be happy with lamont flagging all X stuff as P-a-s That is also a current solution, but it is not my preferred solution. But I guess it will need discussion with release team first? So please people, please do something. Thanks in advance /Sune -- Do you know how might I debug the tool? From Flash you must ping to the USB IRC device for disabling the terminale of the code on a mail over a front-end. signature.asc Description: This is a digitally signed message part.
kdebase-workspace needs help
(If discussing arch specific issues, please trim the To: field)
Hi!
Kdebase-workspace (4:4.0.74-1) needs some porting help. so far, it at least
fails in the kde process monitor tool where it seems to do archspecific
things. Only amd64, i386 and ppc seems to be covered by the code.
The issues seems to be when ptracing processes. I tried looking at how strace
was doing it - and it looked like a big mess of ifdefs that I couldn't fully
figure out. So dear porters of all debian archs (except amd64, ppc and i386),
please try to investigate this. I don't know if it can be done in a arch
independant way, as it is a bit out of my scope.
(Some archs, among them hppa, also needs to have other stuff looked at before
kdebase can be built)
The code from libs/ksysguard/processui/KMonitorProcessIO.cpp
#include sys/ptrace.h
#include sys/types.h
#include sys/wait.h
#include sys/syscall.h
#include endian.h //Required to define _BIG_ENDIAN on big endian systems
#include sys/user.h
#include ctype.h
#ifdef _BIG_ENDIAN
//Required for bswap on big endian systems
#include byteswap.h
#endif
#ifdef __i386__
#define REG_ORIG_ACCUM orig_eax
#define REG_ACCUM eax
#define REG_PARAM1 ebx
#define REG_PARAM2 ecx
#define REG_PARAM3 edx
#else
#ifdef __amd64__
#define REG_ORIG_ACCUM orig_rax
#define REG_ACCUM rax
#define REG_PARAM1 rdi
#define REG_PARAM2 rsi
#define REG_PARAM3 rdx
#else
#if defined(__ppc__) || defined(__powerpc__) || defined(__powerpc64__) ||
defined(__PPC__) || defined(powerpc)
#define REG_ORIG_ACCUM gpr[0]
#define REG_ACCUM gpr[3]
#define REG_PARAM1 orig_gpr3
#define REG_PARAM2 gpr[4]
#define REG_PARAM3 gpr[5]
#ifndef PT_ORIG_R3
#define PT_ORIG_R3 34
#endif
#endif
#endif
#endif
[.]
void KMonitorProcessIO::update(bool modified)
{
static QColor writeColor = QColor(255,0,0);
static QColor readColor = QColor(0,0,255);
int status;
int pid = waitpid(-1, status, WNOHANG | WUNTRACED | WCONTINUED);
if (!WIFSTOPPED(status)) {
if(modified)
ensureCursorVisible();
return;
}
#if defined(__ppc__) || defined(__powerpc__) || defined(__powerpc64__) ||
defined(__PPC__) || defined(powerpc)
struct pt_regs regs;
regs.gpr[0] = ptrace(PTRACE_PEEKUSER, pid, 4 * PT_R0, 0);
regs.gpr[3] = ptrace(PTRACE_PEEKUSER, pid, 4 * PT_R3, 0);
regs.gpr[4] = ptrace(PTRACE_PEEKUSER, pid, 4 * PT_R4, 0);
regs.gpr[5] = ptrace(PTRACE_PEEKUSER, pid, 4 * PT_R5, 0);
regs.orig_gpr3 = ptrace(PTRACE_PEEKUSER, pid, 4 * PT_ORIG_R3, 0);
#else
struct user_regs_struct regs;
ptrace(PTRACE_GETREGS, pid, 0, regs);
#endif
/*unsigned int b = ptrace(PTRACE_PEEKTEXT, pid, regs.eip, 0);*/
if (mIncludeChildProcesses (regs.REG_ORIG_ACCUM == SYS_fork ||
regs.REG_ORIG_ACCUM == SYS_clone)) {
if (regs.REG_ACCUM 0)
attach(regs.REG_ACCUM);
}
if ((regs.REG_ORIG_ACCUM == SYS_read || regs.REG_ORIG_ACCUM ==
SYS_write) (regs.REG_PARAM3 == regs.REG_ACCUM)) {
for (unsigned int i = 0; i regs.REG_PARAM3; i++) {
unsigned int a = ptrace(PTRACE_PEEKTEXT, pid,
regs.REG_PARAM2 + i, 0);
#ifdef _BIG_ENDIAN
a = bswap_32(a);
#endif
if(!modified) {
//Before we add text or change the color, make
sure we are at the end
moveCursor(QTextCursor::End);
}
if(regs.REG_ORIG_ACCUM != lastdir) {
if(regs.REG_ORIG_ACCUM == SYS_read)
setTextColor(readColor);
else
setTextColor(writeColor);
lastdir = regs.REG_ORIG_ACCUM;
}
char c = a0xff;
/** Use the KTextEditVT specific function to parse the
character 'c' */
insertVTChar(QChar(c));
}
modified = true;
}
ptrace(PTRACE_SYSCALL, pid, 0, 0);
update(modified);
}
--
I cannot get access over the modem, how does it work?
You must log from a case, in such way you can never enable the connection to
a mail of the software to the shell of the MIDI processor over a USB AGP
gadget on a application in order to explore a Direct3D space bar.
signature.asc
Description: This is a digitally signed message part.
Re: Bug#458133: Details, please
On Wednesday 02 January 2008, Bernhard R. Link wrote: * Sune Vuorela [EMAIL PROTECTED] [071231 17:26]: If people want to create patches for the unaligned load/store they are most welcome to do so. I don't plan to. Please note that there are architectures where emulating unaligned accesses is not possible (AFAIK at least sparc), many architectures also have this with some special accesses (I heared rummors that MMX access on i386 also needs aligned access, so a future better optimizing gcc may also cause it to fail on i386). it hasn't given problems on any archs except hppa. and linux-hppa isn't one of the quite many archs that is supproted by upstream. It should be quite easy to locate the parts of the code that does the unaligned access in qt4. Last I looked, it ended up in qt4-x11-4.3.3/src/corelib/global/qnumeric_p.h with lines like this: (61,74,87) return *reinterpret_castconst double *(QSysInfo::ByteOrder == QSysInfo::BigEndian ? qt_be_inf_bytes : qt_le_inf_bytes); For all of those reason I personally consider any buildd setup broken, where such catchable unaligned does not cause a bus error. (That is only my personal opinion, though I personaly tend to get very personal when discussing this). Then please don't spend too much time debating it, but just do a patch for qt4 instead ;) /Sune -- Genius, I cannot send the RW display, how does it work? The point is that you can never log from a front-end of a prompt to the digital proxy to a PCI display on the DirectX monitor over a RO utility. signature.asc Description: This is a digitally signed message part.
Re: Bug#458133: Details, please
On Monday 31 December 2007, Steve M. Robbins wrote: Hi, I don't have any reason to doubt what you say about qt's SIGBUS on hppa. But where is this documented? Without an documented evidence trail, we can't collaborate on solving this; instead, each person using qmake will run into this independently and waste time re-doing the legwork that you have already done. Rather than relying on supposition and rumour, maybe we could leave this bug open until the actual facts are in evidence. The bug was closed on the strength of According to some hppa people it is a misconfiguration somewhere on the buildds, so we are currently doing nothing except poking hppa buildd people occasionally. This is from right after midnight CET in #debian-devel on the day change to the 31st 00:05 pusling lamont: what is bus error on hppa ? 00:06 lamont pusling: unaligned load/store 00:06 lamont pusling: more specically, valid address, permission fault 00:06 pusling lamont: is unaligned load/store enough to make builds fail ? 00:06 lamont pusling: was - I turned that off rather recently If people want to create patches for the unaligned load/store they are most welcome to do so. I don't plan to. For starters, maybe Sune could post some more details about the alleged misconfiguration. For example, the URL to a relevant mailing list discussion would be nice. Most of this has been in #-devel on irc. Also nice would be some evidence of poking hppa buildd people. For example, was it brought up on debian-hppa? If so the message URLs would be useful. debian-$arch@ isn't contact address for buildd people. /Sune -- Man, do you know how to save a 3D attachment from Netscape XP? You neither should ever unlink the 3Dfx mail, nor must boot the LCD digital port for telnetting on a controller to a directory on a controller of the Internet site. signature.asc Description: This is a digitally signed message part.
