From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel@gnu.org
Subject: Re: Glibc/Hurd building log
Date: Sat, 05 Apr 2014 15:37:34 +0200 [thread overview]
Message-ID: <871txb3nj5.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzMu+hDU9_7Pcx2RvT=sK4QDWRH1dGT4dEtEqYsubiMzmg@mail.gmail.com> (Manolis Ragkousis's message of "Fri, 4 Apr 2014 20:04:49 +0000")
Manolis Ragkousis <manolis837@gmail.com> skribis:
> I have attached the build.log file, as you told me, along with
> config.log so you can have a better look. There something strange
> going on with the linker.
>
> ;;; note: source file /home/manolis/git_repos/guix/guix/utils.scm
> ;;; newer than compiled /home/manolis/git_repos/guix/guix/utils.go
> ;;; found fresh local cache at /home/manolis/.cache/guile/ccache/2.0-LE-8-2.0/home/manolis/git_repos/guix/guix/utils.scm.go
It seems that you captured the stderr or ‘guix build’, but note that you
can use ‘guix build --log-file’ instead (see the manual.)
> i686-pc-gnu-gcc -shared -static-libgcc -Wl,-O1 -Wl,-z,defs -Wl,-dynamic-linker=/gnu/store/wb4c154q9ch76wl5giy1h832sxhpsm46-glibc-hurd-cross-i686-pc-gnu-2.18/lib/ld.so.1 -B/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/csu/ -Wl,--version-script=/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc.map -Wl,-soname=libc.so.0.3 -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -nostdlib -nostartfiles -e __libc_main -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/math -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/dlfcn -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/nss -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/nis -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/rt -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/resolv -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/crypt -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libpthread -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/mach -L/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/hurd -Wl,-rpath-link=/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/math:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/dlfcn:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/nss:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/nis:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/rt:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/resolv:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/crypt:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libpthread:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/mach:/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/hurd -o /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc.so -T /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/shlib.lds /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/csu/abi-note.o /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf/soinit.os /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc_pic.os /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf/sofini.os /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf/interp.os /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/elf/ld.so /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/mach/libmachuser-link.so /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/hurd/libhurduser-link.so -lgcc
> /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc_pic.os: In function `__fork':
> /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/source/posix/../sysdeps/mach/hurd/fork.c:71: undefined reference to `__start__hurd_atfork_prepare_hook'
> /gnu/store/hl1rsbjzq5pwph850al9y52xrjqjg4f5-gcc-cross-sans-libc-i686-pc-gnu-4.8.2/libexec/gcc/i686-pc-gnu/ld: /tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc_pic.os: relocation R_386_GOTOFF against undefined hidden symbol `__start__hurd_atfork_prepare_hook' can not be used when making a shared object
> /gnu/store/hl1rsbjzq5pwph850al9y52xrjqjg4f5-gcc-cross-sans-libc-i686-pc-gnu-4.8.2/libexec/gcc/i686-pc-gnu/ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status
> ../Makerules:614: recipe for target '/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-7/build/libc.so' failed
I suspect something wrong with the glibc makefile; see the other thread
on bug-hurd.
Ludo’.
next parent reply other threads:[~2014-04-05 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFtzXzMu+hDU9_7Pcx2RvT=sK4QDWRH1dGT4dEtEqYsubiMzmg@mail.gmail.com>
2014-04-05 13:37 ` Ludovic Courtès [this message]
2014-04-04 21:15 Glibc/Hurd building log Manolis Ragkousis
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871txb3nj5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=manolis837@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).