rm -f lib.a ar rcs lib.a checksum.o old-checksum.o delay.o usercopy.o getuser.o memcpy.o strstr.o make[2]: Leaving directory `/usr/src/linux-2.4.19-openmosix-r5/arch/i386/lib' make[1]: Leaving directory `/usr/src/linux-2.4.19-openmosix-r5/arch/i386/lib' ld -m elf_i386 -T /usr/src/linux-2.4.19-openmosix-r5/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o init/do_mounts.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o /usr/src/linux-2.4.19-openmosix-r5/hpc/hpc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/net/pcmcia/pcmcia_net.o drivers/net/wireless/wireless_net.o drivers/video/video.o \ net/network.o \ /usr/src/linux-2.4.19-openmosix-r5/arch/i386/lib/lib.a /usr/src/linux-2.4.19-openmosix-r5/lib/lib.a /usr/src/linux-2.4.19-openmosix-r5/arch/i386/lib/lib.a \ --end-group \ -o vmlinux arch/i386/kernel/kernel.o: In function `sys_rt_sigsuspend': arch/i386/kernel/kernel.o(.text+0x1386): undefined reference to `cause_link_error_by_routine_that_does_not_exist' arch/i386/kernel/kernel.o: In function `sys_sigaction': arch/i386/kernel/kernel.o(.text+0x18c6): undefined reference to `cause_link_error_by_routine_that_does_not_exist' arch/i386/kernel/kernel.o(.text+0x1920): undefined reference to `cause_link_error_by_routine_that_does_not_exist' arch/i386/kernel/kernel.o(.text+0x1980): undefined reference to `cause_link_error_by_routine_that_does_not_exist' arch/i386/kernel/kernel.o(.text+0x19e4): undefined reference to `cause_link_error_by_routine_that_does_not_exist' arch/i386/kernel/kernel.o(.text+0x22b3): more undefined references to `cause_link_error_by_routine_that_does_not_exist' follow make: *** [vmlinux] Error 1
Created attachment 4046 [details] my .config Same .config from my working gentoo-r9 kernel, with a 'make oldconfig' and 'make menuconfig' to include the openmosix stuff
It is failing on purpose cuz something is wrong... you can turn those places into panic()s because they shouldn't be reachable... that is how to fix it... let me get carpaski in on this...
tantive make the ebuild. He's good at it
If you are using gcc3.2 then you just encountered some nasty things in opemosix... I added a patch to avvoid these, but catched only one. I'll try to fix that.
I can verify this issue. I currently have two gentoo1.4 systems (one p4, one p3) that have failed in the exact same way while emerging openmosix-sources. On another note, downloading the stock kernel.org 2.4.19 kernel and applying the stock openmosix patch from openmosix.sf.net's download section produced the exact same result. As well, on openMosix's FAQ page (http://openmosix.leonora.org/FAQ.php?openMosixFAQ) they state "There are many kernel-related issues with gcc-3.x compilers. Inlining, optimization and page alignment do strange things to operating systems kernels. The standard Linux kernel is only guaranteed to compile and work properly with versions of gcc prior to 3.x." Of course, I my previous kernel (latest gentoo-sources) has worked fine with my gcc3.2-only systems, which leads me to believe this is an issue dealing specifically with the openmosix patches. If anyone figures any of this out, that would be great :) Hopefully I may have helped to lead someone in the right direction here, if not, sorry - this is my first (ever) bugzilla report... ;-) Marcus
There is a patch for this error (which is only a link error) included in the gentoo-2.4.19-r5.ebuild. Due to a nasty typo the patch was not applied when using gcc3. I fixed that one. In other words: Please update portage (sync/rsync) and try again. Post your results here...
The patch fails for me. Even attempting to use my own diff it failed when patching (?!) Changing the big openmosix patch it worked fine, and built fine.
ok, at least i found another error... The patch-file itself, it won't apply because the openmosix-devs changed the comment in the line before that one that is patched, so patch couldn't find the right line to patch... I corrected this and uploaded a new -gcc3.patch.bz2 to ibiblio (the old one had 322 bytes, the new one has 338 bytes). Also generated a new digest... Hope this will fix this bug!
After an emerge rsync (and checking in distfiles to make sure i have the 338 byte version of the patch) I get the following when I emerge openmosix-sources: ----------snip------------- patching file drivers/evms/evms.c patching file drivers/md/lvm.c patching file fs/buffer.c Hunk #1 succeeded at 366 (offset 4 lines). patching file fs/reiserfs/super.c patching file fs/super.c Hunk #1 succeeded at 38 (offset 1 line). Hunk #3 succeeded at 495 (offset 1 line). Hunk #4 succeeded at 766 (offset 19 lines). Hunk #5 succeeded at 760 (offset 1 line). Hunk #6 succeeded at 786 (offset 19 lines). Hunk #7 succeeded at 883 (offset 1 line). patching file include/linux/fs.h Hunk #1 succeeded at 1291 (offset 71 lines). patching file kernel/ksyms.c can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -naur a/uaccess.h b/uaccess.h |--- a/uaccess.h Mon Sep 23 18:42:30 2002 |+++ b/uaccess.h Mon Sep 23 18:45:10 2002 -------------------------- File to patch: ----------snip------------- At this point, it lets me type in a file to patch, but I'm not really sure what it wants. If I type something in, heres what happens: (my input is in carats <>) ----------snip------------- File to patch: <uaccess.h> uaccess.h: No such file or directory Skip this patch? [y] <y> Skipping patch. 1 out of 1 hunk ignored !!! ERROR: The ebuild did not complete successfully. !!! Function src_unpack, Line -86, Exitcode 1 !!! (no error message) ----------snip------------- Hope this aids with the debugging process...
I forgot to include the correct path in the patch. Fixed that, new .patch.bz2 is 362 bytes. Digest is updated.
Success. It has so far worked perfectly on two of my machines, and thus openmosix-user is working now as well. Thanks for the quick responces to our queries to solve this issue! :) (If this wasn't my first bugzilla experience, I'd prolly "close" or "Resolve" this bug now, but in case there is a specific protocol, I'm gonna leave it as it is. If not, feel free to close the bug.)
I'll close this bug now. Thanks for your help in making openmosix-support better. Keep in mind to install gentoo-stats so your new machines will show up in the stats :-)
