From: lemonnierk@ulrar.net
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: gnu: Have lua-5.1 compile a .so
Date: Thu, 11 Sep 2014 12:12:21 +0200 [thread overview]
Message-ID: <20140911101221.GI31169@luwin.ulrar.net> (raw)
In-Reply-To: <87vbouv5iu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Didn't think of that, indeed. I know I'm not using the .a, don't know about others though.
On Thu, Sep 11, 2014 at 12:02:49PM +0200, Ludovic Courtès wrote:
> lemonnierk@ulrar.net skribis:
>
> > According to someone on stackoverflow, "The lua team does not include support for
> > shared libraries by default because doing so in a portable manner is not simple."
> > http://stackoverflow.com/questions/20848275/compiling-lua-create-so-files
>
> Heh, Libtool to the rescue! ;-)
>
> > From 81f659884cf02d0d63846b45be5f93d794a9e092 Mon Sep 17 00:00:00 2001
> > From: Kevin Lemonnier <lemonnierk@ulrar.net>
> > Date: Thu, 11 Sep 2014 03:12:39 +0200
> > Subject: [PATCH] gnu: Have lua-5.1 compile a .so
> >
> > * gnu/packages/patches/lua51-liblua-so.patch: New file
> > * gnu/packages/lua.scm: Use of lua51-liblua-so.patch in lua-5.1
>
> I’ve applied it, but I realized that liblua.a is now populated with
> -fPIC object files, which doesn’t make much sense.
>
> Perhaps we could remove lib/liblua.a altogether?
>
> Thanks,
> Ludo’.
--
Kevin Lemonnier
PGP Fingerprint : C123 47CA 9E64 FCF0 3907
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-11 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 22:31 gnu: Have lua-5.1 compile a .so lemonnierk
2014-09-10 22:42 ` Cyril Roelandt
2014-09-10 23:09 ` Eric Bavier
2014-09-11 8:02 ` Ludovic Courtès
2014-09-11 8:12 ` lemonnierk
2014-09-11 10:02 ` Ludovic Courtès
2014-09-11 10:12 ` lemonnierk [this message]
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=20140911101221.GI31169@luwin.ulrar.net \
--to=lemonnierk@ulrar.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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
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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.