emerge =emacs-22.1-r1 fails with the following messages: loading tooltip... ((58203 . 8578) (11755 . 0) (620 . 65) 80110 166533 (71 . 7) (18 . 12) (5651 . 1846)) Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under names emacs and emacs-22.1.1 1110195 pure bytes used ./emacs -q -batch -f list-load-path-shadows Fatal error (11)gmake[1]: *** [emacs] Segmentation fault: 11 (core dumped) gmake[1]: Leaving directory `/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/src' (export PARALLEL; PARALLEL=0; cd leim; gmake all \ CC='i686-gentoo-freebsd6.2-gcc' CFLAGS='-O2 -march=pentium4 -pipe' CPPFLAGS='-I/usr/X11R6/include -I/usr/local/include -L/usr/local/lib ' \ LDFLAGS='-Wl,-znocombreloc ' MAKE='gmake') gmake[1]: Entering directory `/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim' EMACSLOADPATH=/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim/../lisp LC_ALL=C ../src/emacs -batch --no-init-file --no-site-file --multibyte -l /var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim/../lisp/international/titdic-cnv \ -f batch-titdic-convert -dir quail /var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim/CXTERM-DIC; \ echo "changed" > changed.tit Fatal error (11)EMACSLOADPATH=/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim/../lisp LC_ALL=C ../src/emacs -batch --no-init-file --no-site-file --multibyte -f batch-byte-compile quail/CCDOSPY.el >>Error occurred processing quail/CCDOSPY.el: File error (("Opening input file" "no such file or directory" "/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim/quail/CCDOSPY.el")) gmake[1]: *** [quail/CCDOSPY.elc] Error 1 gmake[1]: Leaving directory `/var/tmp/portage/app-editors/emacs-22.1-r1/work/emacs-22.1/leim' gmake: *** [leim] Error 2 * * ERROR: app-editors/emacs-22.1-r1 failed. * Call stack: * ebuild.sh, line 1684: Called dyn_compile * ebuild.sh, line 1020: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * emacs-22.1-r1.ebuild, line 140: Called die * The specific snippet of code: * emake CC="$(tc-getCC)" || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-editors/emacs-22.1-r1/temp/build.log'. * Reproducible: Always Steps to Reproduce: 1. Use a Gentoo/FreeBSD system 2. emerge emacs 3. Actual Results: emerge fails Expected Results: Sucessfull compilation of emacs emerge --info gives: zion ~ # emerge --info Portage 2.1.3.11 (default-bsd/fbsd/6.2/x86, gcc-4.1.2, freebsd-lib-6.2-r1, 6.2-RELEASE i386) ================================================================= System uname: 6.2-RELEASE i386 i386 Timestamp of tree: Mon, 01 Oct 2007 17:30:01 +0000 app-shells/bash: 3.2_p15-r1 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 2.0.0_alpha1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 6.2-r1 ACCEPT_KEYWORDS="x86-fbsd ~x86-fbsd" CBUILD="i686-gentoo-freebsd6.2" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-gentoo-freebsd6.2" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.gentoo.no/ " PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/kde" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi aiglx berkdb bzip2 cairo cli cracklib crypt cups dbus dri drm gdbm gif glitz hal iconv java java5 jce jpeg kde kdehiddenvisibility midi mono mp3 ncurses nls nsplugin ogg openexr opengl oss pam pcre perl png ppds python qt qt3 qt3support qt4 readline reflection session spl sqlite ssl svg tcpd tiff truetype unicode vorbis win32codecs x86-fbsd xcomposite xine xml xorg zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="FreeBSD" INPUT_DEVICES="mouse keyboard" KERNEL="FreeBSD" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="BSD" VIDEO_CARDS="i810" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Hi - this worked fine for me (I just re-merged it to make sure). I wonder if it is your use flags - I know you included your whole set, but could you do an "emerge -1av emacs" and let me know what it says? Here is mine: app-editors/emacs-22.1-r1 USE="X gif gtk jpeg png spell tiff toolkit-scroll-bars xpm -Xaw3d (-alsa) -gzip-el -hesiod -motif -sound -source"
(In reply to comment #1) Sorry for the delay... Here is the output: [ebuild N ] app-editors/emacs-22.1-r1 USE="X gif jpeg png tiff xpm -Xaw3d (-alsa) -gtk -gzip-el -hesiod -motif -sound -source -spell -toolkit-scroll-bars"
Thanks Joe for reproducing the bug and for reporting it upstream: <http://lists.gnu.org/archive/html/bug-gnu-emacs/2007-11/msg00022.html> To summarise what we (Joe doing all the work ;) have found out in our IRC debugging session yesterday: a) emacs-cvs-22.1.50-r1 (i.e. Emacs 22 CVS base branch) is also affected. b) Under different USE flags it behaves as follows: -X: o.k. X gtk: o.k. X -gtk Xaw3d segfaults X -gtk -Xaw3d -motif: segfaults Increasing severity by one point, since the bug is reproducible and affects more than one configuration.
Any news on this issue?
Not from me... The gentoo/freebsd was a bit more work than i needed so that install is gone :( But i could alwas give it a new try. (In reply to comment #4) > Any news on this issue? >
Is this still an issue in app-editors/emacs-cvs-22.2.91? We are approaching the last pretests for 22.3 so this might be the last chance to fix the bug for Emacs 22.
I don't really know. Bit i do have virtualbox installed so i can test it without to much hassle if it is interesting. If it is, do you want me to test gfbsd6.* or gfbsd-7.0? /addeman (In reply to comment #6) > Is this still an issue in app-editors/emacs-cvs-22.2.91? > > We are approaching the last pretests for 22.3 so this might be the last chance > to fix the bug for Emacs 22. >
(In reply to comment #7) > I don't really know. Bit i do have virtualbox installed so i can test it > without to much hassle if it is interesting. If it is, do you want me to test > gfbsd6.* or gfbsd-7.0? Both would be the best case.
(In reply to comment #8) > Both would be the best case. > Turns out that Virtualbox didn't want to cooperate as much as I would have liked it to. But I noticed that 22.3 already hit the tree, so i guess it's a moot point anyway. I did test 22.3 in gfbsd 6.2 with the following use flags: X -gtk Xaw3d, which earlier was reported to segfault. It worked just fine now. If you want me to test any other combination of useflags please let me know. I'll see if i can manage to get 7.0 to work in virtualbox too, and do the same test.
(In reply to comment #9) > (In reply to comment #8) > > Both would be the best case. > > > > Turns out that Virtualbox didn't want to cooperate as much as I would have > liked it to. But I noticed that 22.3 already hit the tree, so i guess it's a > moot point anyway. It isn't. We can patch it in Gentoo and report it upstream, a release does not mean bug-freeness. > I did test 22.3 in gfbsd 6.2 with the following use flags: X -gtk Xaw3d, which > earlier was reported to segfault. It worked just fine now. If you want me to > test any other combination of useflags please let me know. Perfect would be an iteration through all combinations...you can script that, but that depends on you if you want to do it or not. If the original issue is fixed we can close this bug. > I'll see if i can manage to get 7.0 to work in virtualbox too, and do the same > test. We appreciate that.
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > Both would be the best case. > > > > > > > Turns out that Virtualbox didn't want to cooperate as much as I would have > > liked it to. But I noticed that 22.3 already hit the tree, so i guess it's a > > moot point anyway. > > It isn't. We can patch it in Gentoo and report it upstream, a release does > not mean bug-freeness. I guess not, i meant more in respect of 'in time for release'... But bugs should get squashed, even if they made the release. > > > I did test 22.3 in gfbsd 6.2 with the following use flags: X -gtk Xaw3d, which > > earlier was reported to segfault. It worked just fine now. If you want me to > > test any other combination of useflags please let me know. > > Perfect would be an iteration through all combinations...you can script that, > but that depends on you if you want to do it or not. If the original issue is > fixed we can close this bug. Well, there are a lot of use flags for emacs, so testing all combinations would take a while. But i'm thinking of a little script that starts building with no use flags and adds one per iteration. That would finish in acceptable time i think. I'm currently building all deps for this test. Could for f in useflags ; do echo "app-editors/emacs $f" >> /etc/portage/package.use ; emerge app-editors/emacs >> emacs${f}.log ; done with /etc/portage/package.use originally containing app-editors/emacs -* and useflags replaced with the actual use flags available for emacs do the trick? On gfbsd6 i seem to remember that libpng failed, but thats another bug, but prevents testing of that useflag. > > > I'll see if i can manage to get 7.0 to work in virtualbox too, and do the same > > test. > Well, upgrading to vbox-1.6.6 seems to have done the trick. gfbsd7.0 now boots, so results will be available in the near future. > We appreciate that. >
No update since more than a year. Please reopen if this is still an issue.
