Summary: | compile error when emerging qemacs 1.3.1 on ppc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin <monsorno> |
Component: | New packages | Assignee: | PPC Porters <ppc> |
Status: | VERIFIED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Fixes ppc segfault with qemacs |
Description
Martin
2005-03-02 02:35:10 UTC
Just a little fix, done in CVS. Successfully installed qemacs 1.3.1 now on my machine. Thanks for the fix. Sadly, now when trying to start it, I get a "Segmentation fault". Any ideas what could be broken? Should I mark this bug as VERIFIED now? No, we'll reopen the bug. From looking at the code, it's segfaulting when it's trying to open plugins. By switching the method it uses to another, it seems to work fine. Can you test this patch? Created attachment 53302 [details, diff]
Fixes ppc segfault with qemacs
I applied this patch by running the following commands, I hope this was correct:
igent:/usr/portage/app-editors/qemacs # ebuild qemacs-0.3.1.ebuild unpack
...
cd /var/tmp/portage/qemacs-0.3.1/work/qemacs-0.3.1
igent:/var/tmp/portage/qemacs-0.3.1/work/qemacs-0.3.1 # patch -p0 </tmp/qemacs-ppc-segfault.patch
patching file qe.c
igent:/usr/portage/app-editors/qemacs # ebuild qemacs-0.3.1.ebuild compile test install qmerge
>>> md5 src_uri ;-) qemacs-0.3.1.tar.gz
>>> Checking qemacs-0.3.1.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
./configure --prefix=/usr --host=powerpc-unknown-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-x11 --enable-png
...
These commands run successfully, as does qemacs afterwards. So I think this is fixed. Well done, thank you very much.
Added to cvs. Just notized that this bug is not closed by now, so I tried to install this again by running: emerge qemacs and it worked well. So I set this to verified. I don't know who is responsible for closing this bug. Closed. :) |