unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tomas Cech <sleep_walker@suse.cz>
Cc: guix-devel@gnu.org, enlightenment-devel@lists.sourceforge.net
Subject: Re: [PATCH] gnu: luajit: Add -fPIC into CFLAGS.
Date: Wed, 07 Jan 2015 21:14:46 +0100	[thread overview]
Message-ID: <87ppaqz6tl.fsf@gnu.org> (raw)
In-Reply-To: <87oaqpwazx.wl%sleep_walker@suse.cz> (Tomas Cech's message of "Sat, 27 Dec 2014 13:08:50 +0100")

Tomas Cech <sleep_walker@suse.cz> skribis:

> /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.3/../../../../x86_64-pc-linux-gnu/bin/ld: /gnu/store/ij22m0lalbagkm4fflnxc9691ax4bpvk-luajit-2.0.3/lib/libluajit-5.1.a(lj_err.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
> /gnu/store/ij22m0lalbagkm4fflnxc9691ax4bpvk-luajit-2.0.3/lib/libluajit-5.1.a: error adding symbols: Bad value
> collect2: error: ld returned 1 exit status

It took me a while to notice it, but it seems you’re using the linker of
your host distro here and not that of Guix.

This problem cannot occur in builds run by the guix-daemon because it
sets up a chroot.  So I’m guessing this is in your own environment,
right?

In that case, please make sure to run:

  guix package -i gcc-toolchain

to get the “right” compiler, linker, etc.

HTH,
Ludo’.

  reply	other threads:[~2015-01-07 20:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 22:52 [PATCH] gnu: luajit: Add -fPIC into CFLAGS Tomáš Čech
2014-12-16 17:08 ` Ludovic Courtès
2014-12-16 19:28   ` Tomas Cech
2014-12-16 21:08     ` Ludovic Courtès
2014-12-16 21:42       ` Tomas Cech
2014-12-16 22:15         ` Ludovic Courtès
2014-12-27 12:08           ` Tomas Cech
2015-01-07 20:14             ` Ludovic Courtès [this message]
2015-01-28 20:31               ` Tomas Cech
2015-02-01 14:43                 ` [PATCH] gnu: luajit: don't require ldconfig Tomáš Čech
2015-02-01 19:07                   ` Ludovic Courtès

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=87ppaqz6tl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=enlightenment-devel@lists.sourceforge.net \
    --cc=guix-devel@gnu.org \
    --cc=sleep_walker@suse.cz \
    /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).