At the prompt, I typed: # emerge Xfree After about 40 minutes, it stopped with the following message: !!! Error: x11-base/xfree-4.3.0-r2 failed !!! Function src_compile, Line 477, Exitcode 2 !!! (no error message) I used ccache and distcc (with 4 hosts) with Portage USE="-alsa -gnome -gtk" Reproducible: Always Steps to Reproduce: 1. emerge xfree 2. 3. Actual Results: I got this error message: !!! Error: x11-base/xfree-4.3.0-r2 failed !!! Function src_compile, Line 477, Exitcode 2 !!! (no error message) Expected Results: Xfree should have been emerged Mosix6 root # emerge info Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20-openmosix-r6 i686 Celeron (Mendocino) GENTOO_MIRRORS="http://mirror.gentoo.gr.jp" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config" 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="x86 oss 3dnow apm arts avi crypt cups encode gif gpm imlib java jpeg kde libg++ libwww mikmod mmx motif mpeg ncurses nls oggvorbis opengl pdflib png qt quicktime sdl spell svga truetype X xml2 xmms xv zlib gdbm berkdb slang readline tcpd pam ssl perl python -gtk -gnome -alsa" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=pentium2 -O3 -pipe -fomit-frame-pointer -mmmx" CXXFLAGS="-mcpu=pentium2 -O3 -pipe -fomit-frame-pointer -mmmx" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j12" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox distcc ccache"
I am having the same problem. Also using the OpenMosix kernel. More of the error message: perl ../../../fonts/util/ucs2any.pl 6x13.bdf ../../../fonts/util/map-ISO8859-4 ISO8859-4 make[4]: *** [6x13-ISO8859-4.bdf] Segmentation fault I tried lowering my compile flags but doesn't help.
Created attachment 13195 [details] The last lines printed before the emerge of Xfree stopped I sent to a file everything I could copy from what "emerge xfree" output to tty before stopping. I hope it will help.
please check you have enough space, that your perl build is working good and that you don't have the pc suffering overheat.
Luca, I checked the temperature of the PC and it doesn't overheat. Regarding disk space, DF tells me: Mosix6 root # df -h Filesystem Size Used Avail Use% Mounted on /dev/hda3 3.6G 1.4G 2.0G 41% / tmpfs 2.0M 128K 1.9M 7% /mnt/.init.d oMFS 96G 0 9.6G 0% /mfs tmpfs 62M 0 62M 0% /dev/shm How can I make sure that perl is complete, properly installed and working well? Any test i can run? Thanks! Charles
just enter the xfree buildir and try performing one of the lines that seems segfaulting on you. then try to run frozen-bubble and/or reemerge perl again. if the df is after the xfree crash you should have plenty of space.
Luca, I tried running the line that made it crashed (perl ../../../fonts/util/bdftruncate.pl 0x3200 < 8x13.bdf > 8x13t.bdf) from where make was when it crashed (/var/tmp/portage/xfree-4.3.0-r2/work/xc/fonts/bdf/misc) and it worked. What does it mean? To reemerge perl again should I just do "emerge perl"? Thanks! Charles
seemant do you have any hint about that? I'm running out of ideas
tames@timmay tames $ df -h Filesystem Size Used Avail Use% Mounted on /dev/hdc3 57G 1.3G 55G 3% / tempfs 2.0M 132K 1.9M 7% /mnt/.init.d /dev/hda1 75G 23G 53G 30% /mnt/windows tmpfs 252M 0 252M 0% /dev/shm It also didn't give me an error when I ran it manually.
I switched to the Gentoo kernel sources and it went right past that part. It's compiling fine now.
could you give some information about the kernel you use? passing it to the x86-kernel team
I used the linux-2.4.20-openmosix-r6 kernel sources. What other info would help?
Luca, Here is the info about my kernel: Mosix6 root # uname -a Linux Mosix6 2.4.20-openmosix-r6 #1 Fri Jun 13 23:50:46 JST 2003 i686 Celeron (Mendocino) GenuineIntel GNU/Linux Mosix6 root # I'll download and compile the "vanilla" kernel (http://www.gentoo.org/dyn/pkgs/sys-kernel/vanilla-sources.xml) today and try to emerge xfree. I'll keep you posted. I have another machine on which I have this kernel: Mosix5 root # uname -a Linux Mosix5 2.4.20-openmosix-r4 #2 Fri May 23 15:12:58 JST 2003 i586 Pentium MMX GenuineIntel GNU/Linux Mosix5 root # and I emerged xfree without any problem (although it took 3.5 days.). Many thanks! Charles
Luca, I downloaded the source code for the vanilla version of kernel 2.4.21, compiled and installed it. I am trying again to emerge xfree. I am now well passed the point where I had my error message previously. I should be able to confirm Tames report (http://bugs.gentoo.org/show_bug.cgi?id=22736#c9) early tomorrow morning (when the emerge process will be fully done). I already brought this problem to attention of the OpenMosix mailing list (http://sourceforge.net/mailarchive/forum.php?thread_id=2598551&forum_id=7897). Thanks! Charles
Luca, Just a quick note to confirm that I successfully emerged xfree under the version 2.4.21 of the kernel. I am now trying to emerge kde under the OpenMosix kernel version 2.4.20-3. Thanks! Charles
I switched back to the OpenMosix kernel after getting Xfree emerged and it ran fine. I then tried to emerge gnome and it failed with the OpenMosix kernel but completed with the Gentoo sources kernel. Might be related.
i'm sending this to tantive since he does openmosix-sources. Jay
It looks like some packages can't be emerged while running openMosix. This depends on the hardware you have on your cluster: e.g if you have a pentium 4, an amd athlon xp and some older hardware and you emerge something on the pentium 4, then portage will optimize it according to your settings to that architecture. When openMosix kicks in and balances the load on your machines by migrating proccesses away, then it can happen, that code, that is optimized for e.g. a pentium 4 is run on some of your older hardware. Due to flags and extension (like sse, mmx etc...) this code can break. In this case emerge breaks. Hope this clarifies the problems you encountered.
see http://bugs.gentoo.org/show_bug.cgi?id=27615 for the same problem and more information. *** This bug has been marked as a duplicate of 27615 ***
