unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jca+emacs@wxcvbn.org (Jérémie Courrèges-Anglas)
Cc: aurelien.aptel+emacs@gmail.com, monnier@iro.umontreal.ca,
	emacs-devel@gnu.org
Subject: Re: Google Summer of Code - some ideas
Date: Mon, 22 Apr 2013 23:30:13 +0300	[thread overview]
Message-ID: <83a9oqxq96.fsf@gnu.org> (raw)
In-Reply-To: <87bo961fu6.fsf@moo.wxcvbn.org>

> From: jca+emacs@wxcvbn.org (Jérémie Courrèges-Anglas)
> Cc: Aurélien Aptel <aurelien.aptel+emacs@gmail.com>,
>         monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 22 Apr 2013 22:16:17 +0200
> 
> I'm probably not knowledgeable enough about this subject, but... is it
> really easier to get this (raw dlopening) right?  If my Emacs build
> dlopens gnutls with a major 39, and a few days later my system gets
> a 40th gnutls major version because of ABI change, then I will run into
> problems.  And I can't count on my package tools dependancy system to
> notice the ABI change, unless I artificially encode the dependancy on
> gnutls or take care to bump my Emacs package to force a rebuild.
> 
> Perhaps are there workarounds or methods to implement this safely in
> Emacs, but I fear that it would make life harder for some users and
> packagers.

Emacs already has a solution for all this, in the MS-Windows build
(which already loads these libraries dynamically).  So what's needed
is to use the same arrangement on other platforms, which currently
link statically against these libraries.

In  nutshell, the version against which Emacs was compiled is recorded
at build time, and then tested against the library at load time.




  reply	other threads:[~2013-04-22 20:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 16:46 Google Summer of Code - some ideas Aurélien Aptel
2013-04-21 17:16 ` Aurélien Aptel
2013-04-21 17:25   ` Bastien
2013-04-21 17:53     ` Aurélien Aptel
2013-04-21 23:05       ` Bastien
2013-04-21 18:34 ` joakim
2013-04-22 14:34 ` Stefan Monnier
2013-04-22 16:48   ` Eli Zaretskii
2013-04-23  3:23     ` Stefan Monnier
2013-04-22 17:51   ` Aurélien Aptel
2013-04-22 18:26     ` Eli Zaretskii
2013-04-22 20:16       ` Jérémie Courrèges-Anglas
2013-04-22 20:30         ` Eli Zaretskii [this message]
2013-04-22 20:39           ` Jérémie Courrèges-Anglas
2013-04-23  2:38             ` Eli Zaretskii
2013-04-23 16:21               ` Eli Zaretskii
2013-04-22 15:52 ` Lennart Borgman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a9oqxq96.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jca+emacs@wxcvbn.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).