From: "Mykola S. Grechukh" <gns@altlinux.org> To: ALT Linux Sisyphus discussions <sisyphus@lists.altlinux.org> Subject: [sisyphus] kernel build hasher Date: Mon, 3 Aug 2009 17:56:13 +0300 Message-ID: <a4ab440f0908030756v1b9f1576vaab765b9cd5d0000@mail.gmail.com> (raw) Здравствуйте, дорогие учёные. У меня на трёх разных хостах происходит вот такой подземный стук при попытке сбилдить kernel-image-std-def в хэшере на текущем сизифе: LD init/built-in.o LD .tmp_vmlinux1 *** glibc detected *** ld: free(): invalid next size (normal): 0x08134338 *** ======= Backtrace: ========= /lib/libc.so.6[0x4015e6ea] /lib/libc.so.6[0x4015fbc8] /lib/libc.so.6(cfree+0x6d)[0x401625ad] /usr/lib/libbfd-2.19.51.0.2.so(_bfd_elf_link_read_relocs+0x15a)[0x40082eba] /usr/lib/libbfd-2.19.51.0.2.so(bfd_elf_link_add_symbols+0x3718)[0x4008c678] ld[0x8055e87] ld[0x8056e3f] ld[0x8056edf] ld[0x8059f29] ld[0x805f826] /lib/libc.so.6(__libc_start_main+0xe6)[0x4010bb26] ld[0x804ac41] ======= Memory map: ======== /bin/sh: line 1: 20099 Aborted ld -m elf_i386 --build-id -X -o .tmp_vmlinux1 -T arch/x86/kernel/vmlinux.lds arch/x86/kernel/head_32.o arch/x86/kernel/head32.o arch/x86/kernel/head.o arch/x86/kernel/init_task.o init/built-in.o --start-group usr/built-in.o arch/x86/kernel/built-in.o arch/x86/mm/built-in.o arch/x86/crypto/built-in.o arch/x86/vdso/built-in.o kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o block/built-in.o lib/lib.a arch/x86/lib/lib.a lib/built-in.o arch/x86/lib/built-in.o drivers/built-in.o sound/built-in.o firmware/built-in.o arch/x86/pci/built-in.o arch/x86/power/built-in.o arch/x86/video/built-in.o net/built-in.o --end-group make: Leaving directory `/usr/src/RPM/BUILD/kernel-image-std-def-2.6.30-alt7.toi1/kernel-source-2.6.30' make: *** [.tmp_vmlinux1] Error 134 error: Bad exit status from /usr/src/tmp/rpm-tmp.15561 (%build) Объясните пожалуйста, как он происходит.
reply other threads:[~2009-08-03 14:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=a4ab440f0908030756v1b9f1576vaab765b9cd5d0000@mail.gmail.com \ --to=gns@altlinux.org \ --cc=sisyphus@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \ sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru public-inbox-index sisyphus Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.sisyphus AGPL code for this site: git clone https://public-inbox.org/public-inbox.git