On Fri, Apr 26, 2024 at 07:04:22AM +0200, Sebastien Marie wrote:
> Dima Pasechnik writes:
>
> Only one thing isn't properly addressed: the SONAME of the library is
> still `libsbcl.so`. This information is used by the linker at compile
> time when the library is used.
>
> $ readelf -d
Dima Pasechnik writes:
> On Fri, Apr 26, 2024 at 12:11:31AM +0200, Kirill A. Korinsky wrote:
>> On Thu, 25 Apr 2024 23:28:27 +0200,
>> Dima Pasechnik wrote:
>> >
>> > +SHARED_LIBS += sbcl 0.0
>>
>> I suggest to match library version with sbcl version to avoid
On Fri, Apr 26, 2024 at 12:11:31AM +0200, Kirill A. Korinsky wrote:
> On Thu, 25 Apr 2024 23:28:27 +0200,
> Dima Pasechnik wrote:
> >
> > +SHARED_LIBS += sbcl 0.0
>
> I suggest to match library version with sbcl version to avoid nightmare, as
> far as I recall
On Thu, 25 Apr 2024 23:28:27 +0200,
Dima Pasechnik wrote:
>
> +SHARED_LIBS += sbcl 0.0
I suggest to match library version with sbcl version to avoid nightmare, as
far as I recall upstream doesn't care about ABI stability between releases,
and, for example, .fasl
On Thu, Apr 25, 2024 at 12:49:07PM +0100, Stuart Henderson wrote:
> On 2024/04/25 10:24, Dima Pasechnik wrote:
> >
> > 1) Is there a standard way to set up .so's major.minor version
> > in the port, and propagate it to the build?
> > (hardcoding major.minor in several patched places is a pain,
On Thu, 25 Apr 2024 15:22:27 +0200,
Sebastien Marie wrote:
>
> Kirill A. Korinsky writes:
> >
> > Which requires at least this patch
>
> yes. I already have sent to upstream the full support for
> --with-sb-linkable-runtime.
>
And you was in 20 seconds early than me with backporting to
Kirill A. Korinsky writes:
> On Thu, 25 Apr 2024 14:11:32 +0200,
> Sebastien Marie wrote:
>>
>> The static-library is simple to add (with --with-sb-linkable-runtime
>> support).
>>
>
> Which requires at least this patch
yes. I already have sent to upstream the full support for
On Thu, Apr 25, 2024 at 02:11:32PM +0200, Sebastien Marie wrote:
> Dima Pasechnik writes:
> > sbcl can be packaged into a dynamic library, something one needs for
> > e.g. calling Lisp from C or Python,
> > via sbcl-librarian https://github.com/quil-lang/sbcl-librarian
> >
>
> A question about
On Thu, 25 Apr 2024 14:11:32 +0200,
Sebastien Marie wrote:
>
> The static-library is simple to add (with --with-sb-linkable-runtime
> support).
>
Which requires at least this patch
diff --git src/cold/shared.lisp src/cold/shared.lisp
index 773d36115..a7c55ea6c 100644
--- src/cold/shared.lisp
Dima Pasechnik writes:
> Dear all,
> sbcl can be packaged into a dynamic library, something one needs for
> e.g. calling Lisp from C or Python,
> via sbcl-librarian https://github.com/quil-lang/sbcl-librarian
>
A question about your use-case: would a static library (libsbcl.a) be
enough for
On 2024/04/25 10:24, Dima Pasechnik wrote:
>
> 1) Is there a standard way to set up .so's major.minor version
> in the port, and propagate it to the build?
> (hardcoding major.minor in several patched places is a pain, obviously)
>
> In port's makefile I now have a line
>
> SHARED_LIBS += sbcl
On Thu, 25 Apr 2024 11:28:49 +0200,
Dima Pasechnik wrote:
>
> [1 ]
> On Wed, Apr 24, 2024 at 08:17:19PM +0200, Kirill A. Korinsky wrote:
> > On Wed, 24 Apr 2024 15:20:46 +0200,
> > Dima Pasechnik wrote:
> > >
> > > Could someone tell me what's missing?
> >
> > You must install it by hand from
On Wed, Apr 24, 2024 at 08:17:19PM +0200, Kirill A. Korinsky wrote:
> On Wed, 24 Apr 2024 15:20:46 +0200,
> Dima Pasechnik wrote:
> >
> > Could someone tell me what's missing?
>
> You must install it by hand from src/runtime/libsbcl.so
Well, that's just a quirk in sbcl-librarian, for the lack of
On Thu, Apr 25, 2024 at 01:25:30AM +0200, Theo Buehler wrote:
> On Thu, Apr 25, 2024 at 01:16:46AM +0200, Dima Pasechnik wrote:
> > On Wed, Apr 24, 2024 at 03:31:32PM -0400, George Koehler wrote:
> > [...]
> > >
> > > Try running "make update-plist" to add new files like libsbcl.so.0.0
> >
> > I
On Thu, 25 Apr 2024 01:16:46 +0200,
Dima Pasechnik wrote:
>
> On Wed, Apr 24, 2024 at 03:31:32PM -0400, George Koehler wrote:
> [...]
> >
> > Try running "make update-plist" to add new files like libsbcl.so.0.0
>
> I am trying this now. Is there a quick way to try an updated
> pkg/PLIST ?
> Or
On Thu, Apr 25, 2024 at 01:16:46AM +0200, Dima Pasechnik wrote:
> On Wed, Apr 24, 2024 at 03:31:32PM -0400, George Koehler wrote:
> [...]
> >
> > Try running "make update-plist" to add new files like libsbcl.so.0.0
>
> I am trying this now. Is there a quick way to try an updated
> pkg/PLIST ?
>
On Wed, Apr 24, 2024 at 03:31:32PM -0400, George Koehler wrote:
[...]
>
> Try running "make update-plist" to add new files like libsbcl.so.0.0
I am trying this now. Is there a quick way to try an updated
pkg/PLIST ?
Or one has to clean up and rebuilt the port in order to see the effect
of the
Cc semarie, who is MAINTAINER for lang/sbcl.
On Wed, 24 Apr 2024 14:20:46 +0100
Dima Pasechnik wrote:
> Dear all,
> sbcl can be packaged into a dynamic library, something one needs for
> e.g. calling Lisp from C or Python,
> via sbcl-librarian https://github.com/quil-lang/sbcl-librarian
>
>
On Wed, 24 Apr 2024 15:20:46 +0200,
Dima Pasechnik wrote:
>
> Could someone tell me what's missing?
You must install it by hand from src/runtime/libsbcl.so
--
wbr, Kirill
Dear all,
sbcl can be packaged into a dynamic library, something one needs for
e.g. calling Lisp from C or Python,
via sbcl-librarian https://github.com/quil-lang/sbcl-librarian
Currently sbcl port does not build and install it, while it's quite easy
at least in theory. Here is my incomplete
20 matches
Mail list logo
