List for cgit developers and users
 help / color / mirror / Atom feed
Subject: Linking cgit with Lua using -Wl,-E
Date: Fri, 21 Oct 2016 09:54:23 +0200	[thread overview]
Message-ID: <564914cc-2ae6-ad15-f40c-4f033788999c@aegee.org> (raw)
In-Reply-To: <20161016115547.GG22407@john.keeping.me.uk>

Hello John,

liblua is linked statically. This is what you get, when you compile Lua from source (no liblua.so).

Greetings
?????

On 10/16/2016 01:55 PM, John Keeping wrote:
> On Sun, Oct 16, 2016 at 07:30:08AM +0200, ????? ???????? wrote:
>> on my system I wanted to link cgit with lua, so that lua can load the
>> (lua)crypto.so module.  For this to work the symbol lua_gettop has to
>> be exported by cgit.  I managed this by passing "-Wl,-E" to the
>> linker, when compiling cgit.
>
> How are you linking to liblua?  I thought we normally linked that
> dynamically so the symbol should be exported from the shared library
> even if the cgit binary does not export symbols.
>


  reply	other threads:[~2016-10-21  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16  5:30 
2016-10-16 11:55 ` john
2016-10-21  7:54   `  [this message]
2016-10-23 15:55     ` john
2016-11-06 10:13       ` 

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=564914cc-2ae6-ad15-f40c-4f033788999c@aegee.org \
    --to=cgit@lists.zx2c4.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.
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 NNTP newsgroup(s).