On Mon, 25 Mar 2019 04:23:08 +
"Robin H. Johnson" wrote:
> On Sat, Mar 23, 2019 at 04:23:27PM -0500, William Hubbs wrote:
> > Hi all,
> >
> > Soon I will be working on fixing up the state of dev-lang/lua, and
> > there are a couple of things I want to mention.
> >
> > The first thing is lib
On Mon, 2019-03-25 at 04:23 +, Robin H. Johnson wrote:
> > Are there more packages in the tree that are locked to a specific version
> > of lua?
> Yes, several, and more on that in a second.
>
> I think packages will need one of two variables:
> LUA_SINGLE_TARGET
> LUA_TARGETS
>
> LUA_TARGET
On Sat, Mar 23, 2019 at 04:23:27PM -0500, William Hubbs wrote:
> Hi all,
>
> Soon I will be working on fixing up the state of dev-lang/lua, and there
> are a couple of things I want to mention.
>
> The first thing is liblua as a shared library. If you are using lua
> internally in a program, upst
On Sun, 2019-03-24 at 12:44 -0500, William Hubbs wrote:
> On Sun, Mar 24, 2019 at 02:26:35PM +0100, Andreas K. Huettel wrote:
> > Am Samstag, 23. März 2019, 22:23:27 CET schrieb William Hubbs:
> > > Hi all,
> > >
> > > Soon I will be working on fixing up the state of dev-lang/lua, and there
> > >
On Sun, Mar 24, 2019 at 12:24:26PM +0100, cont...@hacktivis.me wrote:
> [2019-03-23 16:23:27] William Hubbs:
> > The first thing is liblua as a shared library. If you are using lua
> > internally in a program, upstream strongly recommends not linking it
> > this way; it is supposed to be statically
On Sun, Mar 24, 2019 at 02:26:35PM +0100, Andreas K. Huettel wrote:
> Am Samstag, 23. März 2019, 22:23:27 CET schrieb William Hubbs:
> > Hi all,
> >
> > Soon I will be working on fixing up the state of dev-lang/lua, and there
> > are a couple of things I want to mention.
> >
> > The first thing i
Am Samstag, 23. März 2019, 22:23:27 CET schrieb William Hubbs:
> Hi all,
>
> Soon I will be working on fixing up the state of dev-lang/lua, and there
> are a couple of things I want to mention.
>
> The first thing is liblua as a shared library. If you are using lua
> internally in a program, upst
[2019-03-23 16:23:27] William Hubbs:
> The first thing is liblua as a shared library. If you are using lua
> internally in a program, upstream strongly recommends not linking it
> this way; it is supposed to be statically linked into the executable.
> Because of this, and because of the amount of c
On Sat, 2019-03-23 at 16:23 -0500, William Hubbs wrote:
> Hi all,
>
> Soon I will be working on fixing up the state of dev-lang/lua, and there
> are a couple of things I want to mention.
>
> The first thing is liblua as a shared library. If you are using lua
> internally in a program, upstream st
Hi all,
Soon I will be working on fixing up the state of dev-lang/lua, and there
are a couple of things I want to mention.
The first thing is liblua as a shared library. If you are using lua
internally in a program, upstream strongly recommends not linking it
this way; it is supposed to be static
10 matches
Mail list logo