First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 14458
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Jonathan Nall <nall@themountaingoats.net>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: ta_hanson@yahoo.com
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 14458 depends on: Show dependency tree
Show dependency graph
Bug 14458 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-01-23 16:30 0000
I'm attempting to 'emerge xemacs', which fails with this:
Loading /var/tmp/portage/xemacs-
21.4.9/work/xemacs-21.4.9/lisp/auto-show.elc...
Loading /var/tmp/portage/xemacs-
21.4.9/work/xemacs-21.4.9/lisp/loadhist.elc...
Loading /var/tmp/portage/xemacs-
21.4.9/work/xemacs-21.4.9/lisp/loaddefs.elc...
Loading site-load...
Finding pointers 
to doc strings...
Finding pointers to doc strings...done
Dumping under the name 
xemacs
Testing for Lisp shadows ...
Wrong type argument: vectorp, #<INTERNAL OBJECT 
(XEmacs bug?) (symbol-value-forward type 0) 0x30027008>
xemacs exiting
.
make[1]: *** 
[xemacs] Error 255
make[1]: Leaving directory `/var/tmp/portage/xemacs-
21.4.9/work/xemacs-21.4.9/src'
make: *** [src] Error 2

!!! ERROR: app-editors/xemacs-
21.4.9 failed.
!!! Function src_compile, Line 83, Exitcode 2
!!! (no error message)

---------------------


I think that this is related to the protable dumper (--pdump in configure) but I'm not sure what 
it is or does or how to fix.
I'm doing this on a PPC beige G3 box using Gentoo Linux 1.4rc3 (starting 
with stage1).
Here's some more emerge info:

# emerge info
Portage 2.0.46-r9 (default-ppc-
1.4, gcc-3.2.1, glibc-2.3.1-
r2)
=================================================================
System 
uname: 2.4.19-r6 ppc 

GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc 
/var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config 
/usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf 
/etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="oss 
dvd xv jpeg nls mitshm gif imlib sdl oggvorbis gnome gtk kde mozilla png truetype ppc gdbm berkdb 
slang readline mysql X gpm tcpd pam libwww ssl perl python esd qt motif 
opengl"
COMPILER="gcc3"
CHOST="powerpc-unknown-linux-gnu"
CFLAGS="-O2 -pipe -mcpu=750 -
mpowerpc-gfxopt -fsigned-char"
CXXFLAGS="-O2 -pipe -mcpu=750 -mpowerpc-gfxopt -fsigned-
char"
ACCEPT_KEYWORDS="ppc"
MAKEOPTS="-
j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-
portage"
FEATURES="ccache"

# emerge -p xemacs

These are the packages that I would 
merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] app-editors/xemacs-
21.4.9

------- Comment #1 From Mark Guertin 2003-01-24 10:02:53 0000 -------
Is there a good reason why the xemacs-21.4.8-r3.ebuild was deleted?  Afaik this
was the last one that was truly and successfully tested on ppc.  The otehr
builds had all been bumped by non ppc developers along with stable keywords
(grumble grumble)


ta_hanson: can you try ACCEPT_KEYWORDS="~ppc" emerge xemacs (to test the latest
testing version) and see if it works?

------- Comment #2 From ta_hanson@yahoo.com 2003-01-24 16:02:34 0000 -------
Mark, I tried what you suggested and got the same result.
In case you're wondering, I set the 
ACCEPT_KEYWORDS="~ppc" in make.conf.
Also, I noticed that the same version of xemacs was used 
(21.4.9)...which wasn't what I expected.

------- Comment #3 From Jonathan Nall 2003-01-26 20:44:47 0000 -------
taking this one...

------- Comment #4 From Jonathan Nall 2003-01-26 21:47:55 0000 -------
can you post your glibc version? i've reproduced this on my machine and have
patched it properly. however, i'm curious if the patch is applicable to
glibc-2.2.x as well.

thanks.

------- Comment #5 From ta_hanson@yahoo.com 2003-01-26 21:58:57 0000 -------
my glibc is 2.3.1-rc2...sorry.

------- Comment #6 From Jonathan Nall 2003-01-26 22:58:31 0000 -------
yep, it seems only glibc-2.3.x systems break. i've committed a fix w/ ebuild
checking for glibc >= 2.3.1


First Last Prev Next    No search results available      Search page      Enter new bug