epsilon-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [JITTER] PIC code in sub-package mode


From: Luca Saiu
Subject: Re: [JITTER] PIC code in sub-package mode
Date: Mon, 18 May 2020 23:44:32 +0200
User-agent: Gnus (Gnus v5.13), GNU Emacs 27.0.50, x86_64-pc-linux-gnu

On 2020-05-17 at 20:04 +0200, Jose E. Marchesi wrote:

> Libtool convenience libraries can be incorporated in both applications
> and shared objects (using LDADD and LIBADD respectively), so I guess the
> libfoo.la contains pointers to both PIC and non-PIC code.

Let me restate in public, for the record, what we discussed yesterday.

Libtool convenience libraries *are* in fact guaranteed to always contain
PIC code, or at least PIC code, for the simple fact that they may be
used to generate part of a *shared* library.  The fact that convenience
libraries are static is entirely irrelevant: convenience libraries are
just a collection of object files.
Therefore José was right from the beginning and what I incorrectly
believed to be just a coincidence is in fact the guaranteed behavior.  I
had to reread the manual to remember, and to believe.

I am implementing JITTER_LIBADD in a temporary feature branch.
Sub-package mode seems to work well and I have restructured the
Structured example build system to show how it works.

What I still need to implement is a way to *install* a Libtool
convenience library, for Jitter in non-sub-package mode.  But it should
not be difficult.

-- 
Luca Saiu
* My personal web site:  http://ageinghacker.net
* GNU epsilon:           http://www.gnu.org/software/epsilon
* Jitter:                http://ageinghacker.net/projects/jitter

I support everyone's freedom of mocking any opinion or belief, no
matter how deeply held, with open disrespect and the same unrelented
enthusiasm of a toddler who has just learned the word "poo".

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]