From: Dan Nicolaescu <dann@ics.uci.edu>
To: Peter Dyballa <Peter_Dyballa@freenet.de>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; How to make some libraries link statically via pkg-config files?
Date: Mon, 18 Feb 2008 16:10:31 -0800 [thread overview]
Message-ID: <200802190010.m1J0AVpZ018954@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <C1611188-DE2F-4C2F-9CB6-82609E5DCA3D@freenet.de> (Peter Dyballa's message of "Tue, 19 Feb 2008 00:51:47 +0100")
Peter Dyballa <Peter_Dyballa@freenet.de> writes:
> Am 18.02.2008 um 20:32 schrieb Dan Nicolaescu:
>
> > Your problem lies in linking 2 versions of the same library. You
> > should
> > only ever do that if you know exactly what you are doing, and know
> > details about the libraries and their users.
> >
> > So, IMO, there's nothing that emacs should do about this.
>
> Yes. And therefore I want to delegate this to ld to link those
> libraries that exist twice statically when I have control which
> library gets used.
Again, if you are trying to link the 2 versions of the same library
twice you are asking for trouble. It can be made work if you know what
your are doing, but it's not a good idea. If you do such a thing, and
report bugs here, please explicitly say this in each bug report.
IMHO it's better to figure out a way to avoid linking 2 versions of the
same library than to play any tricks with the config files, linker, etc.
next prev parent reply other threads:[~2008-02-19 0:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 18:52 23.0.60; How to make some libraries link statically via pkg-config files? Peter Dyballa
2008-02-18 19:32 ` Dan Nicolaescu
2008-02-18 23:51 ` Peter Dyballa
2008-02-19 0:10 ` Dan Nicolaescu [this message]
2008-02-19 9:47 ` Peter Dyballa
2008-02-19 9:59 ` Dan Nicolaescu
2008-02-19 10:31 ` Peter Dyballa
2008-02-19 12:03 ` Andreas Schwab
2008-02-19 20:31 ` Stephen J. Turnbull
2008-02-19 21:25 ` Peter Dyballa
2008-02-20 0:32 ` Stephen J. Turnbull
2008-02-20 0:49 ` Peter Dyballa
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=200802190010.m1J0AVpZ018954@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=Peter_Dyballa@freenet.de \
--cc=emacs-pretest-bug@gnu.org \
/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).